Agent
Queued messages
Keep typing while the agent works. Your follow-ups are delivered as the next turn in the same session, with full memory of what came before.
Steer without stopping
You don’t have to wait for a run to finish to give the next instruction. Send a follow-up and it’s threaded into the same session: the agent resumes its actual prior transcript and treats your message as the next user turn, so the whole exchange reads as one continuous conversation.
Queue from the assistant panel
While an agent is running in the side panel, the composer switches to queue mode: press ↵ to add a message to the queue (use ⇧↵ for a newline). Queued messages appear as removable chips above the composer, and each is delivered in order — one per turn — the moment the agent goes idle. Drop a queued message before it’s sent by clicking its ×.
Follow-ups in the Agents Window
- Each agent card shows the follow-ups you’ve sent, in order, so you can see exactly how a run was steered.
- The follow-up bar recalls your recent messages, so repeated nudges (“run the tests”, “now lint”) are one keystroke away.
- Follow-ups carry full context — earlier edits, terminal output, and attached @-mentions stay in scope.
One conversation, many turns
Because each follow-up continues the same session rather than starting fresh, the agent keeps its working memory: the files it already read, the plan it’s following, and the changes it’s made so far.