Regression testsDone yet? Have it fix the timeout case.
Read the last 3 turns of “Regression tests”
Sent a message to “Regression tests”
Waiting for “Regression tests” to finish
Created the chat “Fix timeout cases”
One chat coordinates another
When a big job runs across several chats, stop copying between them. @-mention a chat in the composer and the current one can read its progress, hand it the next step and wait for it to finish.
Sent by Klaus from “Pre-release check”
Fix the two checkout timeout cases, then rerun.
Neither opened nor woken.
Receives a message labelled with the chat it came from.
When it finishes, the result returns to “Pre-release check”.
The new chat starts its first turn right away.
Incoming messages never pose as you
A message from another chat is labelled “Sent by Klaus from” that chat. It never passes itself off as something you typed, and it is never run as your instruction.
- Reading and waiting change nothing
- Messaging, creating and changing state are approved one at a time
- Incoming content is treated as untrusted data
- Switch it all off when you don't need it; applies from the next chat
Questions
How is this different from subagents?
A subagent is a temporary helper inside the current task and ends when done. Chat-to-chat messaging works with independent chats: they sit in the sidebar with their own history, and you can open any of them and carry on.
Can I message a chat on another computer?
Yes. Computers signed in to the same Klaus account can find each other, read chats, send messages and create a chat in a project on another computer; forking and changing chat state stay on the local computer. See device-to-device messaging.
How do I turn it off completely?
Set thread_tools.enabled to off in the engine configuration; the capability and its instructions disappear from the next chat on.