[BUG] Cowork: ALL session chat histories truncated - only last user message visible across ~1967 sessions
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?
In the Claude Desktop app (Cowork mode, Windows Microsoft Store version), ALL session chat histories have been truncated. Approximately 1967 sessions are affected.
Symptoms:
- Only the last user message remains visible in every Cowork session
- All prior conversation history (both user and assistant messages) before that final message has disappeared from the UI
- This affects ALL sessions simultaneously, not just specific ones
Investigation findings:
- Session transcripts are still accessible via the backend API (
read_transcriptreturns full data) - IndexedDB LevelDB files in
AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\IndexedDBstill contain data (verified withstringsandplyvel) - The data is NOT physically deleted - only the UI fails to render it
- Cache clearing, app restart, and computer restart do NOT resolve the issue
Related issues: #27752, #33130, #29793, #29684, #27349
This appears to be the same IndexedDB rendering/corruption issue reported in #33130, but specifically affecting Cowork mode on Windows.
What Should Happen?
All Cowork session chat histories should display their full conversation history (all user and assistant messages) when opened in the UI, matching the data available via the backend API.
Error Messages/Logs
No specific error messages in the UI. Sessions simply show truncated history.
IndexedDB investigation confirms data exists:
- LevelDB files contain session data (verified via strings command and plyvel)
- Backend API read_transcript returns full conversation transcripts
- Custom comparator idb_cmp1 in use
Path: AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\IndexedDB\https_claude.ai_0.indexeddb.leveldbSteps to Reproduce
- Open Claude Desktop app (Windows, Microsoft Store version)
- Navigate to Cowork mode
- Open any existing session from the sidebar
- Observe: only the last user message is visible; all prior conversation (user + assistant messages) is missing
- Repeat with any other session - same result across all ~1967 sessions
- Use
read_transcriptAPI - full conversation data is returned (proving backend data is intact) - Inspect IndexedDB files in AppData - data exists in LevelDB binary files
- Clear app cache, restart app, restart computer - issue persists
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Desktop (Windows Microsoft Store) - Cowork mode - Claude_pzs8sxrjxfjjc
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
Critical issue affecting ~1967 Cowork sessions with important AI VTuber project context.
Related issues: #27752, #33130, #29793, #29684, #27349
Root cause likely IndexedDB corruption/rendering failure (same as #33130).
Environment: Windows 11, Claude Desktop Microsoft Store (Claude_pzs8sxrjxfjjc)
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is NOT a duplicate. Please do not auto-close this issue.
The suggested duplicates (#37273, #24304, #38055) describe different symptoms or are already closed without resolution. This issue specifically reports:
This is a critical data accessibility bug affecting the entire Cowork session database. The scale (1967 sessions) and the specific platform (Windows Store Claude Desktop) make this a unique report that requires engineering investigation.
Please remove the "invalid" label and assign this to the appropriate team.
same issue
Same, and I would add on, is there a need to truncate locally run chat history. Github Copilot and any other that i know of keeps the history of the entire chat and compacts in the background using that compaction as the point to send chat data to the cloud. Yet, the user still will be able to see the entire chat (and. information that was paid for through our token usage for reference at any point we desire to look atit )
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
Seeing a related but distinct symptom, and filed it separately since it doesn't match the exact description here: #75426
In my case it's not that ALL history collapses to only the last user message - specific individual turns go missing from the rendered chat log while turns before and after them display fine. I asked Claude inside the session to check the raw session data via the backend read_transcript tool, and the missing message's full text was present there, confirming the data is intact and this is a UI rendering issue, not data loss. Likely the same underlying root cause as this issue (UI failing to render stored history) but a different manifestation, partial vs. total.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.