[BUG] 7 days of Cowork chat history permanently lost when auto-renewal failed (Windows, self-updated build now in MSIX container)
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?
Bug Report: 7 days of Cowork chat history permanently lost at auto-renewal failure
Account: tcbkhiem@gmail.com
Date: 2026-07-21
Product: Claude Desktop — Cowork mode, Windows 11
Install method: downloaded directly from the browser (not Microsoft Store); the app self-updated afterwards
Severity: Permanent, unrecoverable user data loss. No warning, no error, no export path.
---
What happened
- I was using the app normally.
- Auto-renew triggered at 00:00 and failed.
- The last week of chat history vanished immediately.
- I resubscribed. The history did not come back.
Result: 7 days of work permanently lost. I have exhausted every recovery avenue (see Section 4). I am not asking for the data back — I am reporting the defect so it stops happening to other users.
---
1. Why this matters
Cowork chat history is stored only on the local disk. There is no server-side copy, no export function, and no indication anywhere in the UI that history is at risk. As a paying user I reasonably assumed my Cowork conversations were as durable as conversations on claude.ai. They are not, and nothing told me so.
The lost sessions contained multi-hour design and strategy work. A persistent memory file preserved the conclusions of one session, but the reasoning, the alternatives weighed, and the options rejected along the way — the part that actually cannot be reconstructed — are gone.
---
2. Storage layout (relevant to the suspected cause)
Actual on-disk location of session transcripts:
C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\
Roaming\Claude\local-agent-mode-sessions\
<orgId>\<userId>\local_<sessionId>\.claude\projects\<cwd>\<uuid>.jsonlTwo things stand out:
(a) I never installed from the Microsoft Store, yet the data lives inside an MSIX package container (AppData\Local\Packages\Claude_*). The self-update process therefore converted this installation to a packaged build and migrated the data store at some point.
(b) %APPDATA%\Claude no longer exists on this machine. That is where a non-packaged Electron build would keep its userData. The old location is gone — consistent with a migration that moved (or partially moved) data and then removed the source.
(c) The data lives under LocalCache. Windows treats LocalCache as discardable — it is cleared by app reset, reinstall, and various cleanup utilities. Durable user data belongs in LocalState. This alone makes the storage location unsafe by design.
---
3. Evidence
3.1 Inventory of what survives
- 49 session folders, 176
.jsonlfiles, 127 conversation transcripts (excludingaudit.jsonl). - All under a single org/user UUID pair — no orphaned second-account directory.
- The app's own session index reports 48 sessions, matching the folders on disk. The files are genuinely absent, not merely unindexed.
3.2 The gap, measured two independent ways
By message timestamps inside transcripts:
| Date | Sessions ending |
|---|---|
| 2026-07-12 | 9 |
| 2026-07-13 | 8 |
| 2026-07-14 | 6 |
| 2026-07-15 → 07-19 | 0 |
| 2026-07-20 | 2 (opened only while investigating this incident) |
By filesystem mtime (independent of file contents):
| Last write | .jsonl files |
|---|---|
| 2026-07-12 | 11 |
| 2026-07-13 | 2 |
| 2026-07-14 | 12 |
| 2026-07-15 → 07-20 | 0 |
| 2026-07-21 | 2 |
Two independent measures agree. The newest surviving transcript was written 2026-07-14 15:00. This is not a UI or indexing problem.
3.3 Age-based cleanup is ruled out
Any cleanupPeriodDays-style retention policy deletes the oldest files first. Here transcripts from 2026-06-15 survive intact while the newest week is gone. The deletion pattern is inverted relative to any age-based policy. Something removed or failed to migrate the most recent data specifically.
3.4 Volume Shadow Copy — establishes the timing
| Snapshot | Captured | .jsonl inside | Newest file inside |
|---|---|---|---|
| 1 | 2026-07-21 07:40 | 127 | 2026-07-21 03:20 |
| 2 | 2026-07-20 16:35 | 126 | 2026-07-14 15:00 |
Snapshot 2 is decisive: by the afternoon of 2026-07-20, the newest transcript at this path was already dated 2026-07-14.
Combined with my own observation that the history disappeared immediately after the 00:00 auto-renewal failure, this bounds the loss event to between 2026-07-14 15:00 and 2026-07-20 16:35, with the auto-renewal failure at 00:00 as the only notable event in that window.
3.5 The missing sessions definitely ran
A persistent memory file written by one of the lost sessions still exists and records its own session date within the missing window. Sessions executed and wrote memory, but their transcripts are absent from disk. The application ran to completion while failing to persist — or while persisting somewhere that was subsequently destroyed — and reported nothing.
---
4. Recovery avenues exhausted
| Attempt | Result |
|---|---|
| Full C:\ scan for other local-agent-mode-sessions directories | None found |
| Full scan for any .jsonl with mtime 2026-07-14 → 07-21 | Zero matches anywhere on the volume |
| Windows.old | Not present / no matches |
| $Recycle.Bin | No matches |
| All other AppData\Local\Packages\* containers | No matches |
| Both Volume Shadow Copy snapshots | Newest content already 2026-07-14 |
| App's own session index | Reports only the 48 surviving sessions |
The data is gone. I accept that.
---
5. Known related issues
This failure mode is already reported repeatedly:
- #64403 — history wiped after app update; no server backup, no export, no warning
- #45076 — Cowork session history and project metadata silently lost between sessions
- #57227 — sessions invisible after reinstall; data intact, index lost
- #51412 — Cowork history disappeared after desktop app upgrade
- #65695 — "Reset Application Data" dialog understates destructiveness
- #55084 — chat history deleted after uninstall/reinstall
- #59850 — archived Cowork conversations disappear permanently
---
6. What I am asking for
6.1 — Investigate the link between subscription state changes and local session storage. My history disappeared at the moment auto-renewal failed. Whatever code path runs on entitlement loss, downgrade, or re-authentication should be audited for anything that clears, resets, or re-migrates the local session store. If a failed renewal can destroy local data, that is a critical defect regardless of my individual case.
6.2 — Audit the self-update migration to the MSIX package container. This installation came from a direct download but now stores data inside AppData\Local\Packages\Claude_*, and the previous %APPDATA%\Claude location no longer exists. A migration that copies only part of the data and then removes the source would produce exactly the pattern observed here: everything up to a cutoff date preserved, everything after it lost.
6.3 — Ship these safeguards:
- Export function. There is currently no supported way to get transcripts out of the product. This is the single highest-value fix.
- Tell users history is local-only. One line in the UI would have caused me to back up.
- Automatic pre-update backup of session storage into a timestamped folder that survives the update.
- Move data out of
LocalCacheintoLocalState.LocalCacheis a directory Windows is entitled to discard. - Fail loudly. A session that runs normally while silently failing to persist is the worst possible failure mode.
6.4 — Confirm on the record whether any server-side copy of Cowork session content exists for this account for 2026-07-15 → 07-20. My analysis says no. An explicit answer lets me stop looking.
---
7. Current mitigation
I wrote my own PowerShell tool that exports every surviving session to raw .jsonl plus readable Markdown, and I now run it before every application update. It recovered 127/127 transcripts with 0 errors.
Users should not have to write their own backup tooling to keep their work.
What Should Happen?
Use normally
Error Messages/Logs
Just a normal failed renewal promptSteps to Reproduce
- I was using the app normally.
- Auto-renew triggered at 00:00 and failed.
- The last week of chat history vanished immediately.
- I resubscribed. The history did not come back.
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
lastest cowork version
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
I'm a non-tech guy, so I try to write this report with the help of Claude. I'm pretty upset as I spent a whole night trying to recover missed files