diff --git a/docs/features/message-queueing.md b/docs/features/message-queueing.md index d7b381cb..55cce694 100644 --- a/docs/features/message-queueing.md +++ b/docs/features/message-queueing.md @@ -22,7 +22,7 @@ No more waiting. Type your follow-up thoughts, corrections, or additional reques ## Overview -Message queueing lets you type and send messages while Zoo is still working. Just type your message and hit Enter - it gets queued and will be processed as soon as Zoo is ready for your next input. When a queued message is processed, Zoo implicitly approves whatever would normally require your confirmation (tool calls, file writes, running commands)—even if auto-approval is disabled. This is useful for quick corrections or additions when you want to keep work moving without manual prompts. +Message queueing lets you type and send messages while Zoo is still working. Just type your message and hit Enter - it gets queued and will be processed as soon as Zoo is ready for your next input. Queued messages remain user instructions. They interrupt pending subtask lifecycle and task completion prompts so Zoo can process your feedback before moving on. --- @@ -33,7 +33,7 @@ While Zoo is working: 1. **Type your message** as normal 2. **Press Enter** or click Send 3. **Message gets queued** and appears with "Queued Messages:" label -4. **Zoo processes the queued message** as soon as it's ready for your next input and implicitly approves the next pending action (e.g., a tool call, file write, or command)—even if auto-approval is disabled +4. **Zoo processes the queued message** as soon as it's ready for your next input. If Zoo is about to start or finish a subtask, or accept a completion result, the message is treated as feedback before that lifecycle action continues. Message queueing interface showing active processing and three queued messages @@ -45,10 +45,8 @@ While Zoo is working: The input field stays active so you can type anytime - just hit Enter to queue your message. -:::warning Queued Messages Implicitly Approve -Queued messages act as approval for the next action. When a queued message is processed, Zoo proceeds with whatever would normally require confirmation (tool calls, file writes, running commands)—even if auto-approval is disabled. -Editing or deleting a queued message requires clicking it before it's processed. In fast workflows this window can be extremely short; if you need a manual review step, avoid queueing until you're ready to approve. -Note: This behavior is distinct from [Auto-Approving Actions](/features/auto-approving-actions) and is not controlled by its settings. +:::info Queued Messages and Approval Controls +Queued messages interrupt subtask start, subtask finish, and task completion prompts so Zoo receives your latest instruction before changing task state. For ordinary tool and command prompts, queued input can still accompany the next action as approval feedback. Use the visible approval controls when you need to review an ordinary action before it runs, or configure [Auto-Approving Actions](/features/auto-approving-actions). ::: @@ -63,10 +61,10 @@ A: There is no hard limit on the number of messages you can queue. The queue siz A: No, messages are always processed in the order they were sent (FIFO). **Q: Do queued messages require approval?** -A: No. When processed, a queued message implicitly approves the next pending action (tool calls, file writes, running commands), even if auto-approval is disabled. If you need a manual review step, do not queue the message; wait for the approval prompt and confirm manually. +A: Queued messages are instructions, not standalone actions. They interrupt subtask lifecycle and completion prompts, but can accompany ordinary tool or command approvals as feedback. If you need to review an ordinary action first, wait for its approval prompt instead of queueing the message. -**Q: Why are my queued messages triggering auto-approval?** -A: This isn’t the Auto-Approving Actions setting. Queueing a message tells Zoo to proceed without pausing for confirmations, so the queued message implicitly approves the next action. To avoid this, don’t queue when you need a manual review—wait for the approval prompt and confirm manually. See [Auto-Approving Actions](/features/auto-approving-actions) for settings-based approvals. +**Q: What happens if a subtask finishes before my queued message is processed?** +A: Zoo treats the queued message as feedback and keeps control in the subtask. The subtask processes your instruction before it can finish and return control to its parent. **Q: What happens if Zoo encounters an error?** A: Queued messages remain in the queue. You can choose to cancel them or let processing continue.