Claude Code Field Guide
06 / 35

Conversation History & Sessions

Every session is saved automatically. “claude --resume” drops you back into any past conversation, with full context.

Updated since the video
Currency check: Resume is still there and still essential; a few extra session tools have been added around it.

You rarely finish a real project in a single sitting. Claude Code saves every session automatically, and claude --resume shows a list of past sessions so you can pick up exactly where you left off — same project, same context — instead of re-explaining everything from scratch the next day.

What's changed since the video: session management has grown a few useful siblings — /rename to label a session before you clear it, so it's easy to find later; /branch to fork a session and try a different approach without losing the original; and, for very large sessions after a long break, Claude Code can offer to resume from an automatically generated summary rather than replaying the full history (which also saves tokens on the next request).

Closing the laptop mid-build

A user stops for the day halfway through building a feature. The next morning, claude --resume reopens the exact conversation and file context, so there's no re-explaining what was already decided.

Trying two approaches without losing either

Unsure whether to solve a problem with a database change or a caching layer, a developer uses /branch to explore the caching approach in a fork, while the original session (and its working code) stays untouched as a fallback.