exit_plan_mode returns false rejection in YOLO mode

[tanzhenxin]

What happened?

The exit_plan_mode tool does not work correctly in YOLO mode. When the model calls exit_plan_mode to present a plan and exit plan mode, it returns:

Plan execution was not approved. Remaining in plan mode.

The agent loop continues, but the model believes the user rejected its plan. This causes the model to behave incorrectly — it may try to revise the plan, ask clarifying questions, or otherwise stall instead of proceeding with implementation.

What did you expect to happen?

In YOLO mode, exit_plan_mode should auto-accept the plan and transition out of plan mode, allowing the agent to proceed with coding without user confirmation.

Additional context

• The behavior of exit_plan_mode in non-interactive CLI mode and ACP mode has not been verified and may have similar issues — these modes should also be checked.

[nsalvacao]

Root cause confirmed.

coreToolScheduler.ts has a YOLO fast-path that sets ProceedAlways outcome and marks the tool as scheduled — but skips getConfirmationDetails() and onConfirm() entirely. Since wasApproved is only set inside onConfirm, it stays false. When execute() runs, it sees wasApproved=false and returns the rejection message regardless of the approval mode.

The fix lives in exitPlanMode.ts rather than the scheduler, to keep the change minimal and avoid any risk of affecting other tools. execute() now checks config.getApprovalMode() === YOLO as a fallback before evaluating wasApproved. When YOLO is active, the tool exits plan mode correctly and does not downgrade the approval mode to AUTO_EDIT — the user's --yolo intent is preserved for the rest of the session.

The non-interactive headless auto-deny path (shouldAutoDeny) is intentionally left unchanged — that behavior is correct.

Opened PR #2586 with a single focused commit and 2 new unit tests covering both behaviors.

---

🤖 Generated by Nuno Salvação nuno.salvacao@gmail.com & Co-Authored with Nexo nexo.modeling@gmail.com