Plan view in Claude Desktop (Code mode) shows images from a different session

Resolved 💬 1 comment Opened May 19, 2026 by lnO4X Closed Jun 18, 2026

Description

When running multiple Claude Code sessions in parallel in Claude Desktop, opening the Plan view of session A after viewing the Plan of session B causes session A's Plan to render images belonging to session B. The text/plan content appears correct, but the inline images are leaked from the previously viewed session's Plan. Closing the Plan and reopening it restores the correct images for session A.

This looks like a state/cache isolation issue in the Plan view component — image assets seem to be reused from the previously rendered Plan rather than being re-scoped to the current session.

Steps to reproduce (100% reliable)

  1. Open Claude Desktop in Code mode.
  2. Start two parallel sessions, A and B, each with a Plan that contains images.
  3. Open session B's Plan view (so it renders fully with its images).
  4. Switch to session A and open its Plan view.
  5. Observe that session A's Plan now shows images from session B.
  6. Close and reopen session A's Plan view → correct images for A are restored.

Expected behavior

Each session's Plan view should display only its own images, regardless of which other session's Plan was viewed before.

Actual behavior

Images from the previously opened Plan (session B) leak into the newly opened Plan (session A) until the Plan view is closed and reopened.

Workaround

Close and reopen the Plan view after switching sessions.

Suspected cause (guess)

The Plan view component appears to be keyed by something stable across sessions (or not keyed at all), so the UI reuses the previous image elements/resources instead of remounting per session.

Environment

  • Product: Claude Desktop, Code mode (bundle id `com.anthropic.claudefordesktop`)
  • Claude Desktop version: 1.7196.3
  • OS: macOS 26.4.1 (Build 25E253), arm64 / Apple Silicon
  • Reproducibility: 100%

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗