[Docs] Clarify queued-message approval behavior - #39
Draft
zoomote[bot] wants to merge 1 commit into
Draft
Conversation
This was referenced Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The Message Queueing guide now explains that queued messages remain user instructions, do not approve pending actions, and are delivered as feedback when Zoo is waiting for confirmation. The callout and FAQ were updated to distinguish queued input from explicit and configured auto-approval.
Why this change was made
The previous guide documented implicit approval behavior that is removed by the paired Zoo Code fix for #1308.
Impact
Users receive accurate guidance about steering active tasks without bypassing approval controls.
Related PRs
Screenshots