Anyone who has ever lost a deep coding session with an AI assistant knows the particular frustration of having to re-explain an entire project from scratch. Anthropic has now made that problem considerably less painful for Claude Code users.

The company's CLI tool now supports a /resume command that lets developers seamlessly pick up previous coding sessions directly within an ongoing conversation. The feature works through a simple interactive session picker that lists saved sessions by name, timestamp, or ID.

Session continuity has become a competitive front in the market for terminal-based AI coding agents, where Claude Code rivals offerings such as OpenAI's Codex CLI and GitHub's Copilot CLI. As developers increasingly run multi-hour agentic workflows from the command line, the ability to preserve and revisit conversation state has turned from a convenience into a core workflow requirement — context loss effectively discards the accumulated understanding an assistant has built about a codebase.

How session resumption works

Sessions are stored locally in project directories, typically under ~/.claude/projects/. Work therefore persists even after a user exits the program, closes the terminal, or switches tasks entirely. Local storage also means session history remains on the developer's machine rather than requiring a separate sync step, though users who work across multiple machines will not automatically find their sessions everywhere.

For developers who prefer the command line over the interactive picker, running claude –continue automatically resumes the most recent session in the current directory.

The latest version, Claude Code v2.1.234, rolled out on August 17, 2026, and introduced automatic session resumption when usage limits reset. If a user hits a rate limit mid-session, the tool picks up where they left off once the quota refreshes. That addresses a common pain point for subscribers on tiered usage plans, where a long-running task could previously stall at a limit boundary.

A broader toolkit for managing conversation flow

The CLI now supports named sessions, so users can label their work by feature branch, bug fix, or any other naming convention. There is also project-relevant filtering with the –from-pr flag, which scopes sessions to specific pull requests.

/clear wipes a conversation's context when a fresh start is needed, while /branch and /fork create alternative conversation paths, allowing developers to explore different approaches to a problem without losing the original thread. Together, these commands resemble version-control concepts — branching and forking applied to conversations — which lowers the learning curve for developers already accustomed to git-style workflows.

The desktop app maintains separate session histories while still allowing cross-referencing with CLI tasks.