[BUG] Desktop app Code tab: CLI-created sessions not visible, "Session not found on disk" + "Import CLI sessions" fails even in trusted folder

Status Open
Reported on v2.1.260
Maintainer reply None cached
Activity 0 comments · opened Sep 4, 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?

An existing Code tab session became inaccessible from the desktop app sidebar, showing "Session not found on disk" with the error "No conversation found with session ID: e76e6fb8-c104-4edc-9ade-384b846aba0c". This session ID does not correspond to any file on disk at all.

The actual conversation transcript was intact on disk at:
C:\Users\support\.claude\projects\C--Users-support-Claude\3470e4ee-4a52-48c0-9f10-0a688c49a3f6.jsonl
(~100 MB, last modified 9/3/2026)

The "Import CLI sessions" feature also failed, reporting "No CLI sessions to import" — even after explicitly trusting the project folder (via the trust prompt shown when running the CLI in that directory).

The only way to recover the conversation was to manually locate claude.exe under:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude-code\2.1.260\claude.exe
and run claude --resume 3470e4ee-4a52-48c0-9f10-0a688c49a3f6 from a terminal — which worked and loaded the full session, confirming the data was never lost, only the desktop app's session index lost track of it.

Even after this recovery, the session still does not appear in the desktop app's sidebar, and "Import CLI sessions" still cannot detect it, despite the folder now being trusted.

What Should Happen?

The desktop app should either keep its session index in sync with on-disk .jsonl transcripts under ~/.claude/projects/, or "Import CLI sessions" should successfully detect and import any valid, trusted, on-disk transcript — so end users don't need to manually locate the CLI binary and run raw --resume commands from a terminal to recover their own conversation history.

Error Messages/Logs

No conversation found with session ID: e76e6fb8-c104-4edc-9ade-384b846aba0c

Steps to Reproduce

  1. Use a Code tab session in the desktop app over a long period (large .jsonl, ~100 MB in this case)
  2. At some point, reopening the session shows "Session not found on disk" with a session ID that doesn't match any file in ~/.claude/projects/<project>/
  3. Click "Import CLI sessions" — result: "No CLI sessions to import," even though a valid .jsonl exists in the same (trusted) project folder
  4. From a terminal, run: claude --resume <correct-session-id-found-on-disk>
  5. The CLI successfully loads the full session — confirming the transcript was intact and only the desktop app's index was broken

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Unknown

Claude Code Version

2.1.260

Platform

Claude account with subscription /

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Desktop app version: [uygulamanın About/Hakkında kısmından bulup buraya ekleyin]
Screenshots attached showing: "Session not found on disk" error, "No CLI sessions to import" dialog, and the successful CLI --resume recovery.

<img width="1878" height="932" alt="Image" src="https://github.com/user-attachments/assets/0f5e00c1-56f9-4f29-8a62-99468071d00e" />

<img width="1878" height="932" alt="Image" src="https://github.com/user-attachments/assets/b9c8e05b-cd3b-43a5-b7ce-89b74f426fd3" />

View original on GitHub ↗