Who it is forA developer working on one feature across several sittings who keeps losing context between sessions.
The problemRe-explaining a multi-day task from scratch every time a new session starts wastes time and context.
The outcomeEach feature has its own named session, and you can return to it with the earlier context still there.
What you need first
- Claude Code installed and running in a terminal
- A project folder or git repository to work in
- Access to a Claude account that Claude Code can use
Steps
- Start Claude Code in the project folder with
claude. - Run
/renameand give the session a descriptive name, such as oauth-migration. - When you come back later, run
claude --resumeand pick the session by name from the list. - Or run
claude --continueto jump straight back into your most recent session.
Prompt for your agent
In the Claude Code repo at <project-path>, name the current session for the <feature-name> workstream using /rename, then confirm the name appears when you run claude --resume. Report the session name you set and whether it appears in the list.
Caveat. This is a personal tips collection rather than official documentation, so check the linked Claude docs for current session behavior.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for onmyway133/claude-code-tips-tricks and "Resume a multi-day feature in a named Claude Code session"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer