Steer a running turn
You do not have to wait for a turn to finish before correcting it. A second message becomes guidance for the work in progress.
Send guidance
While a turn is running, send another message in web chat or the CLI. Chetty queues it for the active run and picks it up after its current tool round; it does not start a parallel turn in the same conversation.
The agent is told that your message arrived while it was working, and it must address it before it finishes. If the run ends before the message is picked up, the message is used on the next turn instead.
Keep guidance short and specific: a correction, a constraint, or a fact it could not know. A change of plan is better than a full second brief.
While a child is on screen
Delegated child views in the CLI and web keep the message field in its usual place and size, locked with a read-only hint. The task list stays visible above it, and its rows are display-only.
Send guidance in the parent conversation; Chetty can continue or steer the child from there without gaining extra access. The parent's draft and queued messages stay in the parent view.
Commands and model controls never act on the hidden parent while a child is on screen.
Keys in the CLI
- Ctrl+O switches between running children.
- Esc returns to the parent.
- Ctrl+B moves foreground work to the background without cancelling it.
You can change these shortcuts in /keybinds.
Stop or background work
In the CLI, press Ctrl+X, then k, to stop the child you are viewing or the newest running one. In the web app, use Stop on a busy child opened from the activity rail.
To stop a running turn in the parent conversation, press Esc twice within the interrupt window. If a foreground command keeps the turn from settling, another Esc kills that command.
Ask for a background run instead of stopping the work when you only need your hands back. Read Check or continue a sub-agent for what a stopped child keeps.