Desktop app: active session auto-archives repeatedly right after context compaction/continuation (3+ times in one day, no opt-out)
Environment
- Claude Code desktop app (macOS, Darwin 25.5.0)
- Date observed: 2026-08-10
- Long-running session in a Google Drive-synced workspace
Symptom
An actively-used session was automatically archived at least 3 times in a single day while the user was mid-conversation. The input field was replaced by the "conversation has been archived" notice with an "Unarchive" button. No user action and no assistant/tool action triggered it (verified: the agent never called any archive tool during the session).
Clicking Unarchive restores the session with no data loss, but on a long working session this repeatedly interrupts flow and makes it look like the session was lost.
Correlation observed (possibly useful for root-causing)
The session in question had gone through context-limit continuation (compaction/handoff) twice the same day. Each auto-archive occurred during the post-compaction phase of the session's life. Other, shorter sessions in the same workspace and same app instance were never auto-archived — list_sessions(include_archived: true) consistently showed 0 archived sessions among ~15 recent ones, while this one long/compacted session kept flipping to archived in the UI.
This matches the hypothesis in #60043 that session-state tracking around compaction/continuation is involved, and adds a desktop-app (macOS) data point with a fairly clean correlation: only the compacted long session is affected, repeatedly.
Related issues
- #60043 (long sessions auto-archive mid-conversation; no opt-out)
- #59449, #59451, #68972
Expected behavior
- An actively-used session should never be auto-archived mid-conversation, regardless of how many compactions it has been through.
- If auto-archiving must exist, provide an opt-out or a "pin" per session (as requested in #60043).
🤖 Filed with Claude Code on behalf of the user.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗