[BUG] Dispatch list_sessions returns stale/incomplete view of Claude Code sessions. Stuck Looping

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?

After a combination of a usage-limit pause, a full C drive, and a cache-folder migration from C: to D:, Dispatch's list_sessions has been returning the same stale single-session view for multiple days. Current Claude Code sessions — including ones Dispatch itself started — do not appear, while one old, completed session is the only entry returned. The feed has not recovered on its own.
Impact

Dispatch cannot reach old sessions it previously spawned or new sessions spawned after the incident; no session_id to send_message into them.
list_sessions output no longer matches the Claude Code sidebar.
Archiving the stale session in Claude Code does not remove it from Dispatch's view.
Orchestrator keeps referencing a completed, irrelevant project because it's the only entry in its feed.

What Should Happen?

Expected behavior
list_sessions should reflect the current set of Claude Code sessions and recover automatically after usage-limit / disk-space incidents, rather than latching onto a stale snapshot indefinitely.
Environment

Dispatch (Cowork mode, research preview)
Claude Code on Windows
Cache folder was relocated from C: to D: drive
Observed persisting across multiple days leading up to 2026-04-17

Error Messages/Logs

Steps to Reproduce

Conditions observed before the breakage (not a clean repro — correlated signals)

Dispatch hit a usage limit during an active multi-session workflow.
Around the same time, the user's C drive ran out of space.
Dispatch was mid-way through moving a project cache folder from C: to D:.
Dispatch was left in a paused/hanging state until the usage limit reset and disk space was freed.
After recovery, list_sessions has been stuck ever since. Clearing Dispatch's context/memory and starting new conversations did not restore visibility. Archiving the stale session in Claude Code also did not update the feed.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

claude dispatch desktop app

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

Additional notes

No in-product feedback affordance (no thumbs-down) in Dispatch, so the report goes via GitHub.
If useful to the investigation: the stale entry points at a /sessions/<slug> cwd, suggesting the index may be pinned to a specific session path that no longer reflects current state.