Skip to main content
Type while the agent is working. Your message queues up and injects into the next agent step — no abort, no restart.

​
How to use it

Just keep typing. The chat input stays active even while the agent is busy: 
> refactor the auth module
Agent: [reads files, starts edits...]
> actually, just do the middleware first, skip the handlers
At the next natural boundary, your message appears in the conversation and the agent adjusts.

​
Limits

  • Up to 5 messages queued — the 6th is rejected (not dropped).
  • Not after Ctrl+X — abort clears the queue and blocks new steers until the next prompt.
  • Visible as you queue — queued messages show below the chat with a “queued” label.

​
Why it matters

Watching the agent drift for 10 seconds and then aborting to restart is expensive. Steering redirects for the cost of one extra user message.