Omniscio

OmniscioGuidesClaude Code resume session

Claude Code resume session: /resume, --resume and --continue

A session is a saved conversation tied to a project folder. Claude Code saves it as you work, so you can come back after you exit, crash or /clear.

Sources read November 8, 2026. By the Omniscio team. Updated .

The ways back in

claude --help names the pair you will use most: -c, --continue and -r, --resume [value].

What you haveWhat to run
Last conversation, just exitedclaude --continue, or claude -c
A list to choose fromclaude --resume
You named the sessionclaude --resume <name>
You have a session IDclaude --resume <session-id>
The transcript fileclaude --resume <absolute-path-to.jsonl>
You are inside another session/resume, whose alias is /continue
Only sessions linked to a pull requestclaude --from-pr <number>

claude --continue has limits. With no earlier session it prints No conversation found to continue and exits. It skips sessions created with claude -p or the Agent SDK, and sessions whose first prompt was /loop, though -p --continue includes them. It opens a finished background session, and opening a finished one requires Claude Code v2.1.257 or later.

A running one is refused with

Your most recent conversation is running in the background and the session's ID.

Inside a session, /resume is the command, and /continue is the same command under its alias. It takes a session ID or a name, and opens the picker when you give it nothing; what it does to the conversation you leave is in the still running section.

/restart restarts Claude Code, applies an installed update and resumes this session, and its alias is /update. It needs a Pro, Max or Ultra plan, a native install on macOS or Linux rather than WSL, and Claude Code v2.1.288 or later.

The session picker

Run claude --resume with no argument, or /resume inside a session, and the picker opens on the current worktree, including background sessions marked bg and sessions that added this directory with /add-dir. Ctrl+W widens it to every worktree of the repository and Ctrl+A to every project, and since v2.1.243 it loads more rows as you scroll.

Move with Up, Down, k or j; expand or collapse a group with Right and Left.

Resume with Enter, or 1 to 9 for a position, and preview with Space or Ctrl+V where that is not paste. Ctrl+R renames the row. / or any printable character other than Space, j, k or a digit searches, so a pull request URL finds the session that created it.

Ctrl+A, Ctrl+W and Ctrl+B widen to every project, every worktree or the current branch, each toggling back, and Esc leaves search or closes the picker.

Each row shows the name, otherwise its generated title, summary or first prompt, then time since activity, branch and file size; sessions created with /branch or --fork-session have their own IDs, and duplicate entries are grouped.

If it cannot load the session you select, claude --resume prints

Failed to resume the conversation with a retry command and exits with code 1. From the /resume picker inside a session, it reports the failure and your conversation continues.

Resume by ID or name, from any directory

Set a name at startup with claude -n auth-refactor, change it with /rename auth-refactor, or rename the highlighted row with Ctrl+R. A name you set is a resume handle, and so is the generated title; the default display name, your folder plus a suffix like my-app-3f, is not. --session-id gives a new conversation a specific UUID.

claude --resume <session-id> runs from any directory: Claude Code looks in the current project and its worktrees first, then every other project, a cross-project search that started in v2.1.223. It resolves only when exactly one other project holds a transcript for that ID, and a duplicate makes it report not-found rather than resume one.

When nothing resolves, it prints No conversation found with session ID: <session-id>.

A name resolves across the repository and its worktrees; the two commands differ when it is ambiguous: claude --resume <name> resumes an exact match and opens the picker with the name pre-filled when more than one matches,

By contrast, /resume <name> resumes an exact match and reports an error when the name is ambiguous, so run /resume with no argument for the picker.

If you do not know the ID, /status shows it.

What comes back

A resumed session restores the messages, tool calls and results, the active goal with counters reset, and unexpired scheduled tasks. It does not rerun a tool call still running when the previous process ended, and background Bash and monitor tasks are not restored.

A background subagent, command or workflow that ended with the old process appears as a note that it did not finish.

A compacted session opens at a Conversation compacted row and continues with that summary, the messages it left unsummarized, and every message since; the messages the last compaction summarized are not loaded again.

It continues on its model, except where Anthropic's model page says otherwise. A session started with an agent continues as that agent, keeping its tool restrictions and model; pass --agent to pick another. Claude Code looks in the original directory, if you trusted that workspace, then where you resume from; otherwise it uses the default tools and warns.

Not every launch flag is restored. Pass --mcp-config, --settings, --plugin-dir and --fallback-model again, and any directory added with --add-dir at launch; one added mid-session with /add-dir is not restored. Settings files are re-read at launch, so settings.json and settings.local.json need no flag.

On Pro, Max and Ultra plans, resuming a long conversation after a long break or on a different model can show a Resume this conversation? prompt, estimating the share of your five-hour limit the saved conversation alone would use. It arrives with your first message, not when you select the session.

Which permission mode you return in

Resuming from a terminal with claude --continue, claude --resume <session-id> or claude --resume <name> without -p restores the session's mode, for a name only when it matches one. Pass --permission-mode or --dangerously-skip-permissions to override it. The other routes differ:

  • The picker at launch starts the chosen session in the mode a new session would start in from that command line, except plan mode, which resumes in plan mode.
  • /resume inside a session continues the chosen conversation in your current session's mode. Plan mode is the exception again.
  • A session that ended in bypassPermissions is not resumed in that mode; enable it again at launch.
  • A session that ended in auto returns there only while your account still meets the auto mode requirements.

Plan mode under claude -p --resume is the most conditional case, and restoring it on the non-interactive and VS Code paths needs Claude Code v2.1.246 or later. The run must present the plan for approval: pass --permission-prompt-tool, and do not pass --permission-prompts none, --permission-mode, --dangerously-skip-permissions or --fork-session.

It also must not start through channels (messages from another app), and no deny rule may remove the ExitPlanMode tool.

A session that is still running

Background sessions are the exception: there is a live process to talk to. When the conversation you resume belongs to a running background session, Claude Code opens that session itself. Since v2.1.285 that is the behaviour; before, Claude Code refused and told you to claude attach <id> or stop it first.

A prompt on the command line, as in claude --resume <session> "check the tests too", becomes that session's next turn, and it prints Sent your prompt to the background session (<id>); opening it first.

From inside a session, /resume moves your current conversation to the background and attaches this terminal to the running one, printing Opening "<title>", running in the background (<id>). Press Left on an empty prompt for agent view, the list of background sessions that also lists the one you left.

When the conversation cannot move, because you are already attached to one or session persistence is off, /resume prints the claude attach command instead.

Do not resume one session in two terminals without forking: the messages interleave into one transcript. --fork-session continues in a copy with a new session ID instead.

In the Claude Desktop app

Desktop keeps its own session list and can pick up a CLI session. Close the session in the terminal, type /resume in the Desktop prompt box, search by title, folder or branch, preview where a session left off, and select it. Desktop continues the same session rather than a copy, so claude --resume in the terminal still finds it.

It works in local sessions, not in SSH, WSL or cloud sessions.

From a terminal, claude --desktop --resume <session-id> opens an existing CLI session in Desktop and exits. It requires Claude Code v2.1.285 or later, macOS or x64 Windows, and a signed-in Claude subscription, and it does not work with API key authentication, Bedrock, Google Cloud's Agent Platform or Microsoft Foundry.

It takes the ID that /status shows, and does not accept a session name in place of the ID. It will not move a session open in another terminal or still running in the background; when it works it prints Opening session <session-id> in Desktop.

A session you started in the desktop app resumes in the desktop app, so use the app's own list, which the sidebar guide covers.

When it will not resume

Four messages cover most failures and name the next step. No conversation found to continue means --continue found no earlier session here. No conversation found with session ID means no single stored session matches that ID, because nothing holds it or more than one project holds a copy.

Failed to resume the conversation means the picker found the session but could not load it, and prints a retry command.

Your most recent conversation is running in the background means the session is live: attach from claude agents, or run claude --resume to pick another.

Since v2.1.285, --resume opens it instead.

One report names a heavier Desktop failure. Issue 107157, filed on 2026-11-04 against Claude Code 2.1.309 on Windows 11, says the Desktop Code tab appended a copy of an already compacted segment and rebuilt the conversation through it on resume;

The reporter measured the first request after the resume growing from about 390,000 to 862,039 input tokens, context that had been compacted away the day before.

That is a report, not documented behaviour, and no release note we read changes it.

A second report is a request, not a fault. Issue 96189, open since 2026-09-22 on 2.1.280, asks for a /restart command that would be /exit plus a resume of the latest conversation. Anthropic now documents /restart, though only after an update installs.

Resume, branch or fork

Resume returns to a conversation.

To keep the original and work in a copy, use /branch, which copies the conversation and leaves the original on disk, or --fork-session with --resume or --continue, which starts a separate process on a new session ID.

/clear starts a new conversation and saves the previous one, which you can reopen with /resume or from the rewind menu's previous-session entry.

Where sessions are stored

A session is a saved conversation tied to a project directory, saved locally as you work, which is why you can return after exiting or /clear. The transcript is a JSONL file at ~/.claude/projects/<project>/<session-id>.jsonl, where <project> is your working directory path with non-alphanumeric characters replaced by hyphens.

Transcripts are kept 30 days by default; cleanupPeriodDays changes that.

Two tools sit beside it. /export copies the conversation to the clipboard or saves it as text, for when the transcript leaves Claude Code. claude rm <id> removes a background session from the list, while its transcript stays on disk and remains available through claude --resume.

Where Omniscio fits

Omniscio is the desktop app we make for running many Claude Code sessions at once. It keeps each session's Claude Code ID and starts it again with --resume <id>, so a paused or stopped session returns to the same conversation. The session lifecycle library page covers that, and the features page and download page cover the app.

Where this page stops

This page owns the resume entry points and what they restore. A session that will not load belongs to the failed to load a session guide, undoing changes to the checkpoints guide, and a resumed conversation's context to the context window guide. The rest is in the other guides.

Common questions

How do I resume a Claude Code session?

Run /resume inside a session to open the picker, or run claude --resume in a terminal. claude --continue reopens the most recent conversation in the current directory, and claude --resume with a session ID works from any directory on the machine.

Does a resumed Claude Code session keep the whole conversation?

It restores the messages, tool calls and results, the agent, and, for a direct terminal resume, the permission mode. The model is the exception: it continues as before except in the cases Anthropic's model page names. If the session was compacted it opens at the compaction row and continues from the last summary. Flags such as --mcp-config, --settings, --plugin-dir, --fallback-model and --add-dir are not restored, so pass them again.

Where does Claude Code store sessions?

By default in a JSONL file under ~/.claude/projects, in a folder named from your working directory path and a file named for the session ID. Transcripts are kept for 30 days by default, and the cleanupPeriodDays setting changes that.

Can I resume a Claude Code session from another directory?

Yes. Pass the session ID to claude --resume. Claude Code searches the current project directory and its git worktrees first, then every other project on the machine. A session name resolves only across the current repository and its worktrees.

Does the Claude Desktop app have /resume?

Yes, in local sessions. Type /resume in the Desktop prompt box, then search by title, folder or branch. It is not available in SSH, WSL or cloud sessions. Desktop continues the same session rather than a copy. From a terminal, claude --desktop --resume with a session ID opens the session in Desktop.

Sources

All read November 8, 2026.

  • Manage sessions: the entry points, what a resume restores, and the naming rules. Read November 8, 2026.
  • Commands: /resume, /continue, /restart, /clear, /branch, /rename and /export. Read November 8, 2026.
  • Claude Desktop: /resume in the prompt box, its local-only limit and --desktop --resume. Read November 8, 2026.
  • CLI reference: --continue, --resume, --fork-session, --session-id, --name and --desktop. Read November 8, 2026.
  • Changelog at v2.1.319: the v2.1.243 picker change, the v2.1.246 plan-mode restore, the v2.1.257 finished-background change and the v2.1.285 background and Desktop changes. Read November 8, 2026.
  • The two issue pages above. Read November 8, 2026 through GitHub's API, with each issue's state and comment count taken from the issue itself.
  • Omniscio's session lifecycle library page, read November 8, 2026.
  • Two captures here on November 8, 2026: claude --version printed 2.1.319 (Claude Code), and --help listed -c and -r.