explainx / blog
Learn how to resume previous conversations in Claude Code using the -c/--continue and -r/--resume flags. Never lose context again—pick up exactly where you left off with any past session.
Jun 22, 2026
CLAUDE.md loads at session start and stays forever. Skills load only when invoked. Hooks run deterministically outside the context window. Subagents return only a summary to the main thread. Anthropic's new guide maps all seven instruction methods — here is the practical breakdown with decision rules for each.
Jun 12, 2026
Claude Sonnet 4.6 has a 1 million token context window, but long sessions fill it faster than you expect. Learn what triggers the limit, how automatic compaction works, and the exact commands (/clear, /compact, --fork-session) to manage context like a pro.
May 20, 2026
The Agency is a growing collection of 144+ meticulously crafted AI agent personalities across 12 divisions. Each agent is specialized, personality-driven, and production-ready with battle-tested workflows.
One of the most underused features of Claude Code is the ability to resume previous conversations. By default, every time you open Claude Code it starts a fresh session with no memory of what you discussed yesterday. But with two simple flags—--continue and --resume—you can instantly reload any past conversation and continue right where you left off.
This guide covers everything you need to know: the exact flags, when to use each one, real-world workflows, and a few power-user tricks.
When you close Claude Code, the active session is saved to disk—but the next time you run claude, you get a blank slate. That means:
Claude Code solves this with session persistence. Every conversation is saved automatically. The --continue and --resume flags are how you get back into those saved sessions.
--continue / -c: Jump Into Your Last Sessionclaude --continue
# or the short form:
claude -c
This is the flag you'll use 90% of the time. It does exactly one thing: loads the most recent conversation from your current directory and drops you back into it.
No prompts. No pickers. No session IDs to remember. Just run it and continue.
When to use it:
Example workflow:
# Monday evening — you got halfway through a feature
cd ~/projects/my-app
claude -c
# Claude immediately knows:
# - You're building a payment integration
# - You already set up Stripe webhooks
# - The next step was to write the success/failure handlers
# No re-explaining needed
--resume / -r: Pick Any Past Sessionclaude --resume
# or the short form:
claude -r
Without any arguments, --resume opens an interactive session picker—a scrollable list of every saved conversation. Each entry shows:
Navigate with arrow keys, press Enter to load a session.
You can also pass a session ID directly:
claude --resume abc123de-f456-7890-abcd-ef1234567890
This skips the picker entirely and loads that specific session.
When to use it:
| Goal | Command |
|---|---|
| Continue most recent session | claude -c |
| Pick from all past sessions | claude -r |
| Resume a specific session by ID | claude -r <session-id> |
| Continue non-interactively with a prompt | claude -c -p "your next instruction" |
| Fork a session (preserve original) | claude -c --fork-session |
| Name a session for easy retrieval | claude -n "payment-integration" |
Many developers now start their morning with a single command:
claude -c
Claude reloads your last session and you can immediately ask:
Where did we leave off? What was the next step?
Claude will summarize exactly where the conversation ended and what the next action was—effectively acting as a personal standup note.
When you're working on multiple features simultaneously, name your sessions for easy navigation:
# Start the auth feature session
cd ~/projects/my-app
claude -n "auth-refactor"
# Start the payment feature session (separate session)
claude -n "payments-v2"
# Later, resume the auth work
claude -r
# Select "auth-refactor" from the picker
Session names show up in the picker, making it trivial to find the right one.
You can continue a session without entering interactive mode using --print / -p:
# Continue the last session and run a one-shot prompt
claude -c -p "run the test suite and summarize failures"
# Resume a specific session and ask a question
claude -r abc123de -p "what dependencies did we decide to upgrade?"
This is useful for automating follow-up steps after a human-approved session, or for running quick follow-up queries in scripts.
Sometimes you want to explore an alternative approach without losing your original conversation thread. Use --fork-session:
# Fork your current session before trying a risky refactor
claude -c --fork-session
This creates a new session ID branching from the current state. The original session is preserved exactly as it was. If the experiment fails, you can go back to the original with claude -r and pick the un-forked version.
/resume Command Inside Claude CodeYou don't have to exit Claude Code to switch sessions. Inside an active session, you can type:
/resume
This opens the same interactive picker from within the conversation. Select any past session and Claude will load it inline—effectively letting you "jump" between conversation histories without restarting the CLI.
Claude Code automatically persists sessions to disk. A few things worth knowing:
--continue loads the most recent session for your current directory--no-session-persistence flag disables saving (useful for one-off exploratory sessions you don't want cluttering the picker)~/.claude/sessions/ (you can inspect or back them up from there)Session resumption and CLAUDE.md work together as complementary memory systems:
| Layer | What it stores | Scope |
|---|---|---|
CLAUDE.md | Project conventions, stack, commands, architecture | Every session in this project |
Session (-c / -r) | The actual conversation history and in-progress work | Only the resumed session |
The ideal setup: use CLAUDE.md for stable, project-wide context (stack, conventions, architecture decisions) and session resumption for the active thread of work (the current feature, the ongoing debug session, the in-progress refactor).
When you resume a session, Claude loads both the conversation history and the CLAUDE.md file—giving you full context with zero re-explaining.
Mistake 1: Running claude without -c by habit
If you're used to just typing claude, muscle memory will give you a fresh session. Make -c your default when continuing work:
# Add to your shell profile for convenience
alias cc="claude -c"
Mistake 2: Forgetting that --continue is directory-scoped
If you move to a different directory and run claude -c, it will try to find the most recent session for that directory—not your most recent session globally. Use claude -r to find sessions across all directories.
Mistake 3: Not naming long-running sessions
For any session that's going to span multiple days, use -n when starting it:
claude -n "q3-performance-optimization"
Otherwise it gets an auto-generated name that's hard to spot in the picker later.
Mistake 4: Using --no-session-persistence unintentionally
If someone shared a script that includes --no-session-persistence, sessions from those runs won't be saved. Don't use this flag unless you genuinely want throw-away sessions.
To see all your saved sessions without starting one, just run:
claude -r
Browse the picker, then press Ctrl+C or q to exit without loading anything. It's a quick way to review what you've been working on across projects.
| Flag | Short | What it does |
|---|---|---|
--continue | -c | Loads the most recent session in the current directory |
--resume [id] | -r [id] | Opens an interactive picker, or loads a session by ID |
--fork-session | — | Creates a new session branching from the resumed one |
--name <name> | -n <name> | Names the session for easy retrieval later |
/resume | — | In-session command to switch to another past session |
The combination of --continue for daily flow and --resume for targeted session retrieval eliminates the biggest source of friction in long-running Claude Code workflows: having to re-explain context you've already established.
Start tomorrow's session with claude -c and notice the difference immediately.