Photo: Merlin Lightpainting / Pexels
Anthropic's CLI tool now lets developers pick up exactly where they left off, eliminating one of the most annoying friction points in AI-assisted coding.
Anyone who has ever lost a deep coding session with an AI assistant knows the particular frustration of having to re-explain your entire project from scratch. Anthropic just made that problem significantly 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. It works through a simple interactive session picker that lists saved sessions by name, timestamp, or ID.
How the session resumption actually works #
Sessions are stored locally in project directories, typically under ~/.claude/projects/. That means your work persists even after you exit the program, close your terminal, or switch tasks entirely.
For developers who prefer the command line over the interactive picker, running claude –continue automatically resumes the most recent session in your 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 you hit a rate limit mid-session, the tool now picks up where you left off once your quota refreshes.
A broader toolkit for managing conversation flow #
The CLI now supports named sessions, so you can label your work by feature branch, bug fix, or whatever naming convention keeps your brain organized. There’s also project-relevant filtering with the –from-pr flag, which lets you scope sessions to specific pull requests.
/clear wipes a conversation’s context when you need a fresh start. /branch and /fork let you create alternative conversation paths, allowing you to explore different approaches to a problem without losing your original thread.
The desktop app maintains separate session histories while still allowing cross-referencing with CLI tasks.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our