Silent retention cleanup deletes session transcripts with no warning, opt-in, or recovery
## Summary A user actively working in Claude Code (Cursor extension, `anthropic.claude-code-2.1.141-darwin-arm64`) lost the ability to resume, view, or recover **all Claude Code conversation transcripts** in a given workspace older than the current session, including a session from the previous day, because a built-in cleanup process silently deleted those transcripts from disk. The user received no prompt, no warning, and no Trash-style soft-delete. The retention setting (`cleanupPeriodDays`) was never surfaced, never set explicitly, and **the observed retention behavior is inconsistent with the documented 30-day default** — sessions newer than 30 days are still missing. When the user discovered the loss, the Cursor resume picker presented an empty workspace history, leaving the user with no in-product hint that data had ever existed there. ## Specific concerns 1. **No consent prompt.** Cleanup runs out of the box with no install-time disclosure or first-run dialog. Users who treat their conversation history as durable working knowledge are silently mistaken about the persistence model. 2. **No UI surface for retention.** `cleanupPeriodDays` is documentation-only. There is no UI in Cursor's Claude Code extension or the CLI to view current retention, see when next cleanup will run, see what will be deleted, or cancel a pending cleanup. 3. **Hard delete, no Trash.** Deleted transcripts go straight to `unlink()`. No soft-delete folder, no grace period, no `--restore` comma
Posted by FTSBrand on May 14, 2026, 10:51 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
New> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Silent retention cleanup deletes session transcripts with no warning, opt-in, or recovery
## Summary A user actively working in Claude Code (Cursor extension, `anthropic.claude-code-2.1.141-darwin-arm64`) lost the ability to resume, view, or recover **all Claude Code conversation transcripts** in a given workspace older than the current session, including a session from the previous day, because a built-in cleanup process silently deleted those transcripts from disk. The user received no prompt, no warning, and no Trash-style soft-delete. The retention setting (`cleanupPeriodDays`) was never surfaced, never set explicitly, and **the observed retention behavior is inconsistent with the documented 30-day default** — sessions newer than 30 days are still missing. When the user discovered the loss, the Cursor resume picker presented an empty workspace history, leaving the user with no in-product hint that data had ever existed there. ## Specific concerns 1. **No consent prompt.** Cleanup runs out of the box with no install-time disclosure or first-run dialog. Users who treat their conversation history as durable working knowledge are silently mistaken about the persistence model. 2. **No UI surface for retention.** `cleanupPeriodDays` is documentation-only. There is no UI in Cursor's Claude Code extension or the CLI to view current retention, see when next cleanup will run, see what will be deleted, or cancel a pending cleanup. 3. **Hard delete, no Trash.** Deleted transcripts go straight to `unlink()`. No soft-delete folder, no grace period, no `--restore` comma
Comments (0)
No comments yet. Start the discussion.