[BUG] Plan mode: second plan in the same session is not displayed — UI keeps showing the first plan (Claude Desktop)

Preflight

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report
• [x] I am using the latest Claude Desktop build installed at time of report

What's Wrong?

In Claude Code inside the Claude Desktop app, when plan mode is used twice in the same session, the plan UI stays pinned to the first plan.

After the second plan (call it plan B) is produced and auto-displayed, the plan shown on screen is still the first plan (plan A). Clicking the "View plan" button also shows plan A. Plan B is present in the session data — expanding the assistant's thinking block shows it in full — but the plan viewer never updates to it.

So the plan the user reviews and approves is not the plan that is about to be executed. Since Claude Code can enter plan mode on its own (e.g. driven by a CLAUDE.md instruction), the user may not even realize a newer plan exists.

This appears to be a view-binding issue, not data loss: the plan viewer seems bound to the first plan event of the session and is not refreshed by subsequent ExitPlanMode events. (That mechanism is my inference from the observed symptom — I have not inspected any code.)

What Should Happen?

The plan display area and the "View plan" button should show the most recent plan (plan B).

Steps to Reproduce

1. In the Claude Desktop app, start a session and let Claude enter plan mode. Receive plan A.
2. Approve plan A and let the work complete.
3. In the same session, give a follow-up instruction that causes plan mode again. In my case Claude Code entered plan mode on its own, following a CLAUDE.md instruction that requires plan mode for certain kinds of work — it was not a manual toggle.
4. Plan B is produced and auto-displayed, and a "View plan" button appears alongside it.
5. Look at the displayed plan, and click "View plan".

Observed at step 5:

| Where | Content shown |
| --- | --- |
| Auto-displayed plan area | plan A (wrong) |
| "View plan" button | plan A (wrong) |
| Expanded thinking block | plan B (correct) |

Impact

What is displayed for approval does not match what will be executed. The user makes an approval decision based on plan A while plan B is what actually runs, which defeats the purpose of plan mode's approval gate. It is more likely to go unnoticed in workflows where Claude Code re-enters plan mode automatically, because there is no user action that signals "the plan changed."

Workaround

Expand the thinking block to read the current plan, or start a new session.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Claude Code Version

Claude Desktop 1.24012.9 (03c61d), build 2026-07-24T04:59:17Z. (This is the desktop app version; the bug is in the desktop GUI, not the CLI TUI.)

Platform

Anthropic API

Operating System

macOS 26.6 (25G72)

Terminal/Shell

Other — Claude Desktop app (GUI, not a terminal)

Additional Information

The workspace in use is a multi-root VS Code workspace with CLAUDE.md instructions that mandate plan mode for implementation work, which is why plan mode is entered repeatedly within a single session. I have not tested whether the same happens in the CLI TUI.