[BUG] Archived Web session never reconnects — CCRClient Epoch mismatch (409, session_not_active)
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?
A Web (Remote Control) session gets archived, then unarchived from claude.ai, but can no longer be opened from the VS Code extension. Every attempt to reopen the tab fails with "No conversation found", generating a different new session ID each time — it never reconnects to the original conversation. This happens even after reloading VS Code, fully restarting VS Code, and confirming Remote Control is active.
What Should Happen?
The session should reconnect and load the full conversation history after being unarchived.
Error Messages/Logs
[ERROR] CCRClient: Epoch mismatch (409, reason=session_not_active), shutting down
[DEBUG] [bridge:repl] CCR v2: terminal request-path condition (session_not_active) — closing with 4090 for poll-loop recovery
[WARN] CCRClient: client events failed: terminal request-path condition
[ERROR] SSETransport: Stream read error: The operation was aborted.
[DEBUG] [remote-bridge] Torn down (archive=200)
...
Error: Claude Code returned an error result: No conversation found with session ID: b555c471-140c-4e59-9c5f-82bfcf38402c
Steps to Reproduce
- Start a session in VS Code Claude Code extension via Web/Remote Control.
- Let the session become archived (or archive it manually from claude.ai).
- Unarchive it from claude.ai.
- Reopen the same session tab in the VS Code extension.
- Extension mints a new random session ID and fails with "No conversation found".
- Reproduces even after reloading VS Code, restarting VS Code fully, and confirming Remote Control is active.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.241
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
The local session stub file created by the extension contains: {"type":"teleported-from","remoteSessionId":"...","messageCount":0}. Possibly related to #68972 (sessions auto-archiving too aggressively), but this issue is specifically about the reconnect-after-unarchive step failing.