Independent verification will determine whether Claude Code automatically deletes inactive project session history after roughly 30 days, creating a material persistence limitation for coding-agent workflows.
state: expiredheat: lowuncertainty: highknownscott: highagent-memory coding-agents data-retention
What is this?
Claude Code stores project conversation transcripts as JSONL files under `~/.claude/projects/` and reportedly deletes them after 30 days by default through the configurable `cleanupPeriodDays` setting. A GitHub bug report claims a cutoff matching that default and warns that code remains while the agent’s reasoning and debugging trail disappears; third-party guides describe the same behavior and say retention can be extended in `~/.claude/settings.json`. The supplied snippets do not include direct confirmation from Anthropic’s documentation, so the exact default and deletion behavior still warrant independent verification.
Why it matters to Scott
The exact ~30-day deletion claim is already held in “Code What Transcript Why ebook,” not merely inferred from Scott’s broader memory frameworks. Independent verification is still highly relevant because it would validate or correct a published premise and a material risk addressed by his active Search Conversations archive.
ip:source.code-what-transcript-why-ebookip:concept.keep-the-bronzedev:project.search-conversationsradar:claude-code-plaintext-session-logsradar:concept.claude-coderadar:concept.agent-memory
queries asked of Scott's wikis
- coding-agent session persistence and durable memory
- agent transcripts as project artifacts
- filesystem memory versus conversation history
- coding-agent retention and archival policies
- CLAUDE.md changelogs and externalized agent memory
- lossy compaction and cross-session knowledge preservation
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (1) — ⭐ canonical anchor
Interpretation history
2026-08-19T14:34:50Z
The anecdote has produced no independent verification, first-party documentation, or counterevidence within its observation horizon, so it has not developed into an active episode. The underlying retention question remains relevant but should be reopened only on substantive new evidence.
2026-08-17T14:07:22Z
The re-observation adds no independent verification or counterevidence, so the case remains a single-user anecdote despite its high relevance to Scott’s published premise and archival tooling.
2026-08-17T13:55:30Z
grounded: known/high — The exact ~30-day deletion claim is already held in “Code What Transcript Why ebook,” not merely inferred from Scott’s broader memory frameworks. Independent ve
2026-08-17T13:48:34Z
case created — A single user report of session history loss; plausible but needs independent confirmation before warranting attention.
Decision trace
- 08-20 00:34expireThe anecdote has produced no independent verification, first-party documentation, or counterevidence within its observation horizon, so it has not developed into an active episode. The underlying rete
- 08-20 00:34alert_silentThe staleness trigger adds no factual delta, and repeated observation still leaves only the original user report; there is nothing Scott needs before a future briefing or a substantive reopening event
- 08-20 00:34alert_routeThe staleness trigger adds no factual delta, and repeated observation still leaves only the original user report; there is nothing Scott needs before a future briefing or a substantive reopening event
- 08-18 00:07repriceThe re-observation adds no independent verification or counterevidence, so the case remains a single-user anecdote despite its high relevance to Scott’s published premise and archival tooling.
- 08-18 00:07alert_silentNothing materially changed: engagement and evidence are unchanged, and the claimed 30-day deletion behavior still lacks first-party documentation or reproducible independent confirmation.
- 08-18 00:07alert_routeNothing materially changed: engagement and evidence are unchanged, and the claimed 30-day deletion behavior still lacks first-party documentation or reproducible independent confirmation.
- 08-18 00:03alert_silentA single low-engagement Reddit anecdote repeats the existing roughly 30-day deletion claim but does not independently establish Anthropic's retention policy, deletion mechanism, or scope. It adds
- 08-18 00:03alert_routeA single low-engagement Reddit anecdote repeats the existing roughly 30-day deletion claim but does not independently establish Anthropic's retention policy, deletion mechanism, or scope. It adds
- 08-17 23:55groundThe exact ~30-day deletion claim is already held in “Code What Transcript Why ebook,” not merely inferred from Scott’s broader memory frameworks. Independent verification is still highly relevant beca
- 08-17 23:48createA single user report of session history loss; plausible but needs independent confirmation before warranting attention.