Claude Code deletes context history stored on user devices after 30 days. The policy appears in Anthropic's official documentation and surfaced in a recent Hacker News thread with 13 points.
The change affects local context files created during coding sessions. No user action is required for deletion.
Data Retention Policy
Anthropic states that context history on the device is automatically removed after 30 days. The rule applies only to local storage, not to data processed through Anthropic servers.
The documentation does not specify whether users can extend or shorten this window.
How Context History Works
Claude Code saves conversation state and file context locally to support multi-turn coding tasks. These files enable the model to reference prior edits without re-uploading entire projects.
After the 30-day period, the files are purged from the device. Server-side logs follow separate retention rules outlined elsewhere in Anthropic's privacy policy.
Privacy and Security Considerations
Automatic deletion reduces long-term exposure of code snippets on developer machines. Teams handling sensitive repositories may view the 30-day limit as a built-in safeguard.
The policy provides no option for immediate manual deletion through the documented interface. Users concerned about specific sessions must remove files through their operating system.
Comparison with Other AI Coding Tools
Several competing tools offer different local retention defaults.
| Tool | Local Retention | User Control | License Type |
|---|---|---|---|
| Claude Code | 30 days | None documented | Proprietary |
| Continue.dev | User-defined | Config file | Open source |
| Cursor | Session-based | Manual clear option | Proprietary |
| GitHub Copilot | Not stored | N/A | Proprietary |
Open-source options like Continue.dev let users set retention to zero or archive indefinitely through configuration files.
Who Should Use This
Developers working on short-cycle projects gain automatic cleanup without extra scripts. Teams with strict compliance windows under 30 days should evaluate local alternatives instead.
Users who need persistent project memory across months will find the fixed limit restrictive and may prefer self-hosted setups.
Practical Recommendations
Check the current policy at the official page before relying on long-running sessions. For extended local history, configure Continue.dev or similar tools that store context only where the user directs.
Test deletion behavior on a non-critical project first to confirm file locations on your operating system.
Bottom line: The 30-day device deletion rule adds a predictable privacy boundary but removes user flexibility compared with configurable open-source alternatives.
Anthropic's approach prioritizes automatic cleanup over customization. Developers who value control will likely shift toward local or self-hosted options that keep retention decisions in their hands.
Top comments (0)