fix(plan): exit_plan_mode silently rejected under YOLO#132
Merged
Conversation
Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
YOLO bypassed getConfirmationDetails for exit_plan_mode, so the tool's onConfirm never ran and wasApproved stayed false — execute() then reported "Plan execution was not approved" even when the user wanted the plan to proceed. Treat exit_plan_mode like ask_user_question and keep the confirmation dialog wired up in YOLO mode. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (13)
WalkthroughA version bump from 0.26.13 to 0.26.14 across multiple packages, combined with updates to i18n locale files and UI text replacing "Qwen" references with "proto", and adjustments to YOLO approval mode logic to exclude Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
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
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.
Summary
finalPermission==='allow'), the scheduler and ACP session bypassedgetConfirmationDetails()forexit_plan_mode, so the tool'sonConfirmnever ran.wasApprovedstayedfalseandexecute()returned "Plan execution was not approved" even though the user expected the plan to proceed.exit_plan_modefrom the YOLO bypass incoreToolScheduler.ts:936andSession.ts:900, mirroring the existingask_user_questionexemption. The plan dialog now always fires in YOLO, the closure flipswasApproved, andexecute()reports approval correctly.exit_plan_modetoallowwould still hit the same shape — easy follow-up if needed.Test plan
vitest run packages/core/src/tools/exitPlanMode.test.ts(16 pass)vitest run packages/core/src/core/coreToolScheduler.test.ts(54 pass)vitest run packages/cli/src/acp-integration/session/Session.test.ts(15 pass)🤖 Generated with Claude Code
Summary by CodeRabbit
Version Updates
Bug Fixes
Localization