# Claude Code handoff: pass work to a new session

> A Claude Code handoff is a checked note of the goal, code revision, changes, tests actually run and next step. Save it as HANDOFF.md in your project or as a shared page in 1folder. For the same local conversation, Claude Code’s --continue and --resume may be enough; /compact instead shortens the current conversation.

*Picture: Checkout handoff, a page saved by Claude Code: Goal: preserve cart after sign-in; Branch: cart-restore at 4f2a9c1; Changed: cart restore and its test; Checked: focused test passed; full suite not run; Next: review the empty-cart case.* A checkout handoff: the goal, the branch and commit, what was checked and the next step, for the next session to read and verify.

## Write a handoff the next session can use

1. **Choose resume, compact or a separate handoff.** For a local conversation you want to reopen, claude --continue resumes the most recent session in the current directory and claude --resume offers a picker. Use /compact to summarize the conversation you are still in. Write a handoff for a deliberate new starting point, or to pass work between [Claude Code and Codex](https://1folderapp.com/integrations/claude-code-and-codex-together.md) or another AI app.
2. **Record the code state and evidence.** Ask Claude Code for the project path, branch, commit, uncommitted changes, relevant files, decisions, commands actually run and their results. Keep recommended checks separate from completed checks.

   *Picture: In Claude Code, you type: “Write HANDOFF.md with our goal, branch, commit, uncommitted paths, decisions, actual check results, blockers and next step. Mark unverified claims.”*
3. **Save a shared copy if another app needs it.** [Connect Claude Code](https://1folderapp.com/integrations/claude-code-mcp.md) to 1folder using https://1folderapp.com/mcp, allow the project folder and ask it to save the note as a page. This is an explicit save, not repository sync.

   *Picture: In Claude Code, you type: “Save the reviewed HANDOFF.md as Checkout handoff in my Shop project folder in 1folder. Return its private link.” Claude Code saves Checkout handoff (a page saved by Claude Code) to 1folder.*
4. **Verify before the next edit.** Have the new session read the handoff and inspect the current checkout. Ask it to report mismatches before changing code. After the next task, update the same shared handoff with the results it actually obtained.

   *Picture: The versions of Checkout handoff: Verified empty-cart case (Codex, today); Recorded cart restore fix (Claude Code, yesterday).*

## Claude Code handoff vs compact vs resume

| | What it does | When it fits |
|---|---|---|
| claude --continue or --resume | Reopens an existing local conversation | Continue the same work with its saved conversation |
| /compact | Summarizes the current conversation to free context | Keep working in the same session |
| A handoff note | States the evidence and next action in a file you review | Start a new session deliberately or work with another app |

Checked on November 11, 2026. Built-in command behavior comes from Claude Code’s commands, common workflows and architecture docs; the handoff is a suggested writing workflow.

## A useful handoff is smaller than a transcript

For the checkout example, the next session needs to know the intended cart behavior, the code revision the note describes and why the chosen change was made. It needs the names of the touched files and a reproducible description of the focused test. It does not need every terminal line or abandoned attempt.

Write results narrowly: “focused cart-restore test passed” is better evidence than “everything works.” If the full suite was not run, say that. If a browser check remains, keep it under Next checks. A handoff can be accurate about yesterday’s checkout and still need verification today.

## Copy a Claude Code handoff prompt

- In Claude Code: “Prepare HANDOFF.md for a new session. Include goal and acceptance criteria, absolute project path, branch and commit, uncommitted files, completed edits, decisions with reasons, exact checks actually run and outcomes, failures, unverified assumptions and one next step. Do not include secrets or claim an unrun check passed. Save the reviewed note as Checkout handoff in 1folder.”
- In Codex: “Read Checkout handoff in 1folder. Inspect this checkout and compare its revision and changes with the note. Report mismatches before editing. Continue with the documented next step, run the relevant checks and update the same handoff with actual results.”

## Keep lasting rules separate from changing status

Claude Code documents persistent instructions in CLAUDE.md and support for reading a repository’s AGENTS.md instead. It also has [auto memory](https://1folderapp.com/how-to/does-claude-code-remember-between-sessions.md) for accumulated learnings. Those features are useful for lasting project rules; a handoff records the specific work in progress.

1folder keeps a shared file and its versions. It does not transfer a running session, hidden model state or Git changes to another app. The next agent still needs access to the right repository. Use Git for source history and the saved handoff for the explanation and next action.

## Questions

### Is a Claude Code handoff .md file built in?

HANDOFF.md is a suggested Markdown filename in this workflow, not a special command or automatically loaded file. Explicitly ask the next session to read it.

### Does /compact start a new Claude Code session?

No. It summarizes the current conversation to free context. Claude Code’s command guide distinguishes that from /clear, which starts a new conversation with empty context.

### Can I hand off to a new session without 1folder?

Yes. Keep a reviewed HANDOFF.md with your project and ask the next session to read it. Use 1folder when a shared file link and versions across connected AI apps help.

### Does saving a handoff move the code too?

No. A handoff describes the checkout; it does not copy it, apply changes or create commits. Verify the code independently before relying on the note.

## Sources

- [Claude Code: Common workflows](https://code.claude.com/docs/en/common-workflows)
- [Claude Code: Built-in commands](https://code.claude.com/docs/en/commands)
- [Claude Code: How Claude Code works](https://code.claude.com/docs/en/how-claude-code-works)
- [Claude Code: How Claude remembers your project](https://code.claude.com/docs/en/memory)

Checked on November 11, 2026.

## Read next

- [Does Claude Code remember between sessions?](https://1folderapp.com/how-to/does-claude-code-remember-between-sessions.md): Claude Code loads its instructions and auto memory, and can resume local chats. See what a new session knows, and save handoffs to 1folder to carry the rest.
- [Claude Code HTML report: publish it with a link](https://1folderapp.com/how-to/claude-code-html-report.md): Ask Claude Code or Codex for one HTML report, save it to 1folder and turn on its public link. Keep one address for revisions, within the hosting limits.
- [Use Claude Code and Codex together on the same files, with Cursor too](https://1folderapp.com/integrations/claude-code-and-codex-together.md): Use Claude Code, Codex and Cursor together with a saved handoff, code revision and checks. Connect each app once and keep the next agent’s starting point clear.
- [An AI agent workspace: shared files for every agent you use](https://1folderapp.com/use-cases/ai-agent-workspace.md): 1folder gives Claude Code, Codex, Cursor and your chat apps one shared workspace of files. Each agent gets its own access; every change is a version.

[Add 1folder to your AI app, free](https://1folderapp.com/signin) · [All resources](https://1folderapp.com/resources.md)

Website: https://1folderapp.com/ · Contact: hello@1folderapp.com