feat: sequential per-tool approval instead of batched all-or-nothing#937
Merged
feat: sequential per-tool approval instead of batched all-or-nothing#937
Conversation
…777) Replace the batched approval prompt (approve all or deny all) with sequential per-tool prompts so users can approve or deny each tool independently. This gives granular control without needing skip/only syntax or new data types. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Rename _format_approval_message to format_approval_message (public API) - Update module docstring to reflect sequential approval behavior Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Description
Replaces the batched approval prompt (approve all or deny all) with sequential per-tool prompts. Users can now approve or deny each tool independently when the agent requests multiple actions in a single round.
Before: "I need your approval for: Send text, Create calendar event, Upload file. Yes or no?" (all-or-nothing)
After: Three individual prompts, each with "I'd like to: X. Yes or no?" The user can approve sending the text, deny the calendar event, and approve the upload.
Key behaviors:
Closes #777
Type
Checklist
uv run pytest -v)ruff check backend/ && ruff format --check backend/)test_selective_approval)AI Usage