Queue and Steer Messages While Ziva Works
While Ziva is working, type in the message box labeled Add a follow-up. You can send it in two ways:
| Key | What happens |
|---|---|
| Enter | Queue. Wait until the current task finishes, then start a separate task. |
| Cmd+Enter (macOS) / Ctrl+Enter (Windows, Linux) | Steer. Adjust the current task after Ziva finishes its current step. |
For example, while Ziva adds player movement, steer with “Make the jump lower.” Queue “Add coins to collect” if you want that done afterward. Queued follow-ups run one at a time, in the order you added them.
What you’ll see
Waiting messages appear as rows just above the message box, marked after task (queued) or after current step (steering). Once Ziva reads a steering message, it appears in the conversation marked Steered.
Each waiting message has buttons:
- Steer (on a queued message): use it to adjust the running task instead.
- Send now (on a steering message): stop the current step and send your steering messages right away. Changes Ziva already made stay.
- Edit: move the message back into the message box to change it.
- ✕, labeled Remove from queue: remove the message before delivery.
In a narrow panel, long messages are cut short; hover a row to read all of it.
Things to know
- Steering waits for the current step. A long playtest or Subagent task can delay it. Use Send now if you need to stop that step.
- Stop brings them back. Pressing Stop, or a task ending in an error, puts every waiting message back in the message box so you can edit or resend it.
- Keep Ziva open. Unsent queued messages do not survive a restart.
- Undo and Retry remove steers too. Undoing or retrying a message removes its steers and puts their text back in the message box. You cannot undo a steered message on its own.
- Answer first. Messages already sent to steer wait while Ziva needs an approval or answer. Skipping a question keeps them too. A Clarifying Questions card replaces the message box until you answer or skip it.
Slash commands while Ziva works
Built-in slash commands run right away, even mid-task, except /compact, which waits until the task finishes. Model and mode changes apply to your next message. Skills and custom commands queue or steer like other messages.
Plans and privacy
Queueing and steering work with every model and plan. A steering message goes to the same model as the running task and counts as part of that task, not as a new message.
Queued text stays on your computer until its turn starts, then goes to the selected model. Attachments may upload before that turn begins.
Troubleshooting
- Cmd/Ctrl+Enter sends a normal message. Steering only applies while Ziva is working. When Ziva is idle, both keys send.
- A follow-up could not be queued. Your draft stays in the message box. Check the error, make sure a model is selected, and send it again.
Optional: grouped steers and delivery states
- Several steers go together. If you send two during one step, Ziva reads both at once.
- Changed settings apply to the next task. A running task keeps its starting model, mode, tools, project memories, and MCP servers. If you change these, Cmd/Ctrl+Enter queues the message instead; the message box tells you.
- My steer was queued instead. You changed the model, mode, or a tool setting after the task started. Switch back, or let it run as the next message.
- “Already delivered” when I tried to edit or remove a steer. Ziva has read it; it is in the chat now.