Code tab Recents loses on-disk sessions; Chat and Cowork tabs persist them correctly

Resolved 💬 5 comments Opened May 5, 2026 by pbawa27 Closed May 8, 2026

Environment

  • Claude Code desktop app v2.1.121
  • Windows 11 Pro
  • Account: signed-in personal

Summary
On the Code tab, the "Recents" rail in the left sidebar shows only the currently-running session. Sessions from earlier today (and prior days) that exist as JSONL transcripts on disk are not listed.

The Chat and Cowork tabs do NOT have this problem — their recent items persist across app restarts as expected. The bug is specific to Code.

Repro

  1. Open the desktop app, navigate to the Code tab in any local project.
  2. Start a new Code session, do some work, close it.
  3. Start a second Code session in the same project.
  4. Observe: the Recents rail shows only the second session. The first session is gone from the UI even though its .jsonl is intact at ~/.claude/projects/<slug>/<uuid>.jsonl.

In my case, 7 sessions exist on disk for today's project; only 1 is listed under Recents.

Expected
Recents should list recent sessions for the current project (matching the behavior of claude --resume from the terminal, and matching how Chat/Cowork tabs handle their recents).

Actual
Recents shows only the live session.

Data integrity
On-disk JSONLs are fine. claude --resume from a terminal correctly lists every session. Purely a desktop-app UI display gap — no data is actually lost, but the workflow loss for UI-only users is significant.

Workaround
claude --resume <uuid> from a terminal in the project directory.

Files I checked while investigating

  • ~/.claude/projects/<slug>/*.jsonl — all sessions present
  • ~/.claude/sessions/<pid>.json — only the live session
  • ~/.claude/session-env/<uuid>/ — folders for several recent sessions
  • AppData/Roaming/Claude/Local Storage/leveldb/ — appears to be where the desktop UI stores its Recents state (binary, not inspected)
  • AppData/Roaming/Claude/config.json, bridge-state.json — no Recents data here

View original on GitHub ↗

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