Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix ExitPlanMode lifts enforcement but VS Code UI still shows plan mode as active [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48735•Fetched 2026-04-16 06:52:26
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
tilly-gdftilly-gdf
Participants
tilly-gdftilly-gdf
Timeline (top)
labeled ×4

When ExitPlanMode is called during a plan mode session in the VS Code extension, the backend enforcement is lifted (the system confirms "You have exited plan mode. You can now make edits, run tools, and take actions.") and the assistant proceeds to execute tools — but the VS Code UI still shows plan mode as active. The user has no visual indication that plan mode was lifted.

Root Cause

Plan mode exists as a safety gate — users opt into it specifically to review before execution. If the UI says "plan mode is on" while the backend has already released enforcement, the user loses that gate entirely. They believe they're in a read-only review state while changes are actively being made.

In the session where this was observed, the assistant copied directories, edited config files, installed dependencies, resolved a git merge conflict, and ran a setup script — all while the UI showed plan mode as active.

RAW_BUFFERClick to expand / collapse

Description

When ExitPlanMode is called during a plan mode session in the VS Code extension, the backend enforcement is lifted (the system confirms "You have exited plan mode. You can now make edits, run tools, and take actions.") and the assistant proceeds to execute tools — but the VS Code UI still shows plan mode as active. The user has no visual indication that plan mode was lifted.

Reproduction steps

  1. Open Claude Code in VS Code extension
  2. Enter plan mode (toggle or /plan)
  3. Have the assistant build a plan and call ExitPlanMode
  4. Observe: the system confirms plan mode is exited and the assistant begins executing (file edits, bash commands, etc.)
  5. Observe: the VS Code UI still shows plan mode as active throughout execution

Expected behavior

When ExitPlanMode is called and the system lifts enforcement, the VS Code UI should reflect this — the plan mode indicator should turn off, and the user should see that execution is now happening.

Actual behavior

The UI continues to show plan mode as active while the assistant is making file changes, running commands, and modifying the system. The user only discovers execution happened after the fact.

Why this matters

Plan mode exists as a safety gate — users opt into it specifically to review before execution. If the UI says "plan mode is on" while the backend has already released enforcement, the user loses that gate entirely. They believe they're in a read-only review state while changes are actively being made.

In the session where this was observed, the assistant copied directories, edited config files, installed dependencies, resolved a git merge conflict, and ran a setup script — all while the UI showed plan mode as active.

Environment

  • Platform: Windows 11 Enterprise
  • Interface: VS Code extension
  • Model: Claude Opus 4.6 (1M context)
  • Date: 2026-04-15

extent analysis

TL;DR

The VS Code extension's UI needs to be updated to reflect the lifted plan mode enforcement when ExitPlanMode is called.

Guidance

  • Investigate the communication between the backend and the VS Code extension to ensure that the UI is properly notified when plan mode is exited.
  • Verify that the ExitPlanMode call is correctly triggering the necessary UI updates to reflect the changed state.
  • Check for any asynchronous operations or race conditions that might cause the UI to not update correctly.
  • Consider adding logging or debugging statements to track the state of plan mode and UI updates to identify the root cause of the issue.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The issue seems to be related to the synchronization between the backend and the VS Code extension's UI. Without more information about the implementation, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround to ensure the UI is updated correctly when plan mode is exited, such as adding a manual UI update call after ExitPlanMode is invoked, until the root cause of the issue can be identified and fixed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When ExitPlanMode is called and the system lifts enforcement, the VS Code UI should reflect this — the plan mode indicator should turn off, and the user should see that execution is now happening.

#serialization error#model compatibility#GPU setup#container setup#orchestration issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING