[Bug] Plan Mode exit confirmation message inconsistent with actual mode state

Bug Description
Claude Code made active edits while in Plan Mode. It ack'd the mistake. <excerpt>You're right, I apologize for the confusion. Looking at your screenshot, the UI clearly shows "plan
mode on" at the bottom.
From my side, when I called ExitPlanMode, I received a system message saying "User has approved your plan. You can now start coding." and "You have exited plan mode." — so I proceeded with edits believing plan mode had ended. But your UI shows otherwise.

I don't have a good explanation for the discrepancy. The edits, commits, and pushes all went through successfully (and QA verified), so the tools weren't actually blocked — but plan mode should have prevented that.

You can toggle it off with shift+tab as shown in the status bar. The work is done and verified either way.</excerpt>

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.1.91
• Feedback ID: 9a3a4a04-2154-403c-83e1-3e350e9e59e1

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/tony/.local/share/claude/versions/2.1.91 (expected in multi-process scenarios)\n    at Am_ (/$bunfs/root/src/entrypoints/cli.js:1899:2153)\n    at jl6 (/$bunfs/root/src/entrypoints/cli.js:1899:1233)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:12:45.589Z"},{"error":"MaxFileReadTokenExceededError: File content (30641 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at mO7 (/$bunfs/root/src/entrypoints/cli.js:4306:13161)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:18:05.618Z"},{"error":"MaxFileReadTokenExceededError: File content (16128 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at mO7 (/$bunfs/root/src/entrypoints/cli.js:4306:13161)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:18:05.727Z"},{"error":"McpToolCallError: ### Error\nError: Browser is already in use for /Users/tony/.codex/playwright-browsers/mcp-chrome-9055ea0, use --isolated to run multiple instances of the same browser\n    at nL9 (/$bunfs/root/src/entrypoints/cli.js:1581:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:50:12.340Z"},{"error":"McpToolCallError: Timed out after waiting 15000ms\nCause: Locator.waitHandle\n    at nL9 (/$bunfs/root/src/entrypoints/cli.js:1581:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:50:59.745Z"},{"error":"McpToolCallError: Timed out after waiting 60000ms\nCause: Locator.waitHandle\n    at nL9 (/$bunfs/root/src/entrypoints/cli.js:1581:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T05:53:59.503Z"},{"error":"McpToolCallError: Timed out after waiting 90000ms\nCause: Locator.waitHandle\n    at nL9 (/$bunfs/root/src/entrypoints/cli.js:1581:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-03T06:01:59.237Z"}]