At a glance
- Claude Code stores chat/session history locally on the machine, primarily as .jsonl files under ~/.claude/projects/, organized into project-specific folders; it is distinct from Claude.ai's cloud conversation history.
- On macOS/Linux, inspect ~/.claude/projects/.
- On Windows, check the equivalent user-profile path, commonly %USERPROFILE%.claudeprojects.
- Use Claude Code's session controls such as /resume, claude –continue, or claude –resume to access prior sessions.
- Claude Code history is stored locally.
Claude Code stores chat and session history locally on the machine, primarily as .jsonl files under ~/.claude/projects/, organized into project-specific folders, separate from Claude.ai’s cloud conversation history.
Where to Find Claude Code History
On macOS and Linux, inspect this directory:
~/.claude/projects/The .claude directory is hidden because its name begins with a dot. Enable hidden files in your file manager if the directory does not appear.
On Windows, the commonly used equivalent is:
%USERPROFILE%.claudeprojectsPlatform or version differences may affect the exact location, so verify the Windows path for your installation if it is not present.
How the Session Files Are Organized
Claude Code sessions are grouped by project or working directory. The folders under ~/.claude/projects/ associate saved conversations with the codebase or location where they were created.
Sessions are stored as .jsonl files, generally with one file representing one conversation. Folder names and filename patterns can vary, while the sessions remain organized by project.
| Item | What it means |
|---|---|
| Storage | Local files on your computer |
| Primary directory | ~/.claude/projects/ on macOS and Linux |
| Format | .jsonl session files |
| Organization | Project-specific folders |
Claude Code History vs. Claude.ai History
| System | Storage model | History type |
|---|---|---|
| Claude Code | Local files on the device | Project-based sessions in .jsonl format |
| Claude.ai | Cloud-based account history | Web conversations and account export |
These are separate history systems. A session saved by Claude Code in the local .claude directory should not be treated as part of the Claude.ai sidebar history or account export. Claude Code sessions and Claude.ai history are not automatically synchronized.
How to Resume an Earlier Session
You do not need to open a raw .jsonl file to return to an earlier conversation. Use Claude Code’s session controls:
/resumelets you select a saved session from within Claude Code.claude --continuecontinues a previous session.claude --resumeresumes a selected previous session.
Resuming a saved session retrieves that session; it is not the same as Claude Code automatically remembering every earlier conversation across new sessions.
Handling Local Session Files
Local Claude Code history files may contain sensitive prompts, source code, or credentials included in a conversation. Handle them carefully when inspecting, copying, or sharing them, and do not expose them in logs or public repositories.
If you are looking for a conversation in the Claude.ai sidebar, check the web account history instead. A Claude.ai export is separate from the live local session files under ~/.claude/projects/.
