[BUG] Plan mode indicator persists in UI after ExitPlanMode is called

Resolved 💬 2 comments Opened Apr 18, 2026 by Kaylo90 Closed Apr 18, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description:

The "Plan mode" label displayed in the bottom-left of the Claude Code UI appears to remain visible even after the model has successfully called ExitPlanMode and the user has approved the plan. The label does not reflect the actual state of the session.

What Should Happen?

Expected behavior:

The UI indicator should update to reflect the current session state. If the session has exited plan mode, the label should either disappear, change to show the active mode, or visually distinguish between "plan mode available" vs. "plan mode active."

Actual behavior:

The "Plan mode" label remains displayed even though the session has fully exited plan mode and is accepting edits normally.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

  1. Enter plan mode in a Claude Code session
  2. Have the model research, write a plan, and call ExitPlanMode
  3. Approve the plan when prompted
  4. Observe that the system/assistant receives confirmation: "You have exited plan mode. You can now make edits, run tools, and take actions."
  5. Continue the session — ask the model to make edits
  6. Observe that edits succeed (confirming the session is no longer in plan mode functionally)
  7. Note that the "Plan mode" label still appears in the bottom-left of the UI

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗