Skip to the content
GuidesSign inAdd to your AI

Does Claude Code remember between sessions?

Short answer

Claude Code carries some information between sessions through persistent instructions and auto memory. A new session starts with fresh conversation context; --continue or --resume reopens a saved local conversation instead. Keep exact task status in a reviewed handoff file, such as one saved to 1folder, and ask the next session to read it.

Checked on November 11, 2026 against 3 sources.

Add to your AIFree to start. No card.
Claude Code’s own instructions, auto memory and saved conversations serve different purposes from a checked release handoff.

Choose what should survive the session

  1. Use persistent instructions for lasting rules

    Claude Code documents project instructions in CLAUDE.md and support for reading a repository’s AGENTS.md instead. Keep stable conventions and check commands there, following the repository’s existing instruction-file rules.

  2. Review auto memory separately

    Claude Code can save learnings automatically, including corrections and preferences. Its memory guide explains how this differs from instructions you write. Do not assume it is a complete, reviewed record of the task.

  3. Resume when you want the existing conversation

    Run claude --continue to reopen the most recent session in the current directory, or claude --resume to choose one. Starting a genuinely new session gives you fresh conversation context rather than all previous conversations.

  4. Save a precise working handoff

    For exact state, write a note with the code revision, changed files, actual check results and next action. Keep it locally, or ask connected Claude Code to save it in 1folder for another session or AI app to read.

What persists, and how to use it

WhatWhat it keepsBest use
CLAUDE.md or AGENTS.mdWritten instructions loaded as persistent project contextBuild commands and stable coding conventions
Auto memoryLearnings Claude saves as you workRecurring corrections and preferences
Saved local conversationConversation history that can be resumedReturn to a previous sitting
An explicit handoffThe current state and evidence you choose to saveTransfer a task deliberately and verify it

Checked on November 11, 2026. Native behavior comes from Claude Code’s memory, architecture and common workflows docs; the handoff is a suggested workflow.

How to save Claude Code context between sessions

Decide whether you need the conversation or the state of the project. Reopening a saved conversation is convenient for continuing the same investigation. A handoff is more useful when another app will continue, when the code has changed since the last session or when a reviewer needs a short statement of what was actually verified.

For a release candidate, the note might say that the export test passed, Windows packaging was not checked and the next step is to inspect the installer. Include the branch and commit it describes. The next session should confirm those details against the checkout before acting on them.

Where does Claude Code save files?

In a local session, Claude Code works with the project directory and paths you give it. Its architecture guide says it can access that directory and its subdirectories, plus other files with permission. Ask for the absolute path of a generated report before assuming it is in your downloads.

Claude Code also saves local conversation records under ~/.claude/projects/ so sessions can be resumed. These records are different from the source code and deliverables it edits. A file written locally does not appear in 1folder unless you upload it or ask a connected app to save it there.

End with evidence, start by reading it

  • In Claude Code

    “Write a release handoff with the current project path, branch and commit, changed files, exact checks run and results, unverified Windows packaging and the next step. Save it as Release handoff in my Releases folder in 1folder and return its private link.”

  • In Codex

    “Read Release handoff in 1folder, then inspect this checkout. Confirm the revision and report any mismatch. Continue with the unverified packaging step and update the same handoff with the checks you actually ran.”

A shared file is not shared model memory

1folder can keep the brief, decisions and report that several connected apps need. Connect each app with https://1folderapp.com/mcp, sign in and allow the relevant folder. Ask the next app to read the saved file; nothing imports the prior chat automatically.

Updates to the same file become versions showing who changed it. Compare or undo a mistaken edit while keeping the same link. Keep Git history and code review in the repository workflow: a shared handoff does not transfer uncommitted code or replace a source backup.

Questions

Does Claude Code remember all context between sessions?
No. Its docs say a new session starts with a fresh context window. Persistent instructions and auto memory carry selected information; resuming a saved conversation is a different action.
Is auto memory the same as a task handoff?
No. Auto memory stores learnings Claude chooses to save. A handoff explicitly records the task’s state and evidence so you and the next session can review it.
Can I keep context without a 1folder account?
Yes. Use Claude Code’s persistent instructions, auto memory and resume options, or keep a handoff file in your project. 1folder helps when you want a shared file link and versions across apps.
Does 1folder read the local conversation records?
No. It stores only the files you upload or ask the connected app to save. It does not inspect local session records or move chat history.

Sources

Checked on November 11, 2026.

Read next

All resources

Give Claude Code and Codex one place to keep their work.

Set it up once. Everything they save is kept with every version, easy to find and ready to share.

Add to your AI

Free to start. No card needed.