[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Title: Feature: Named sessions with selectable memory context on startup

Body:

▎ Problem

▎ When working on multiple projects, Claude Code's memory is scoped to the working directory. This works, but there's no way to:
▎ 1. Give a session a meaningful name so its memory is clearly identifiable
▎ 2. Choose which session context to load at the start of a new conversation
▎ 3. Avoid confusion when multiple sessions run from the same directory

▎ Proposed solution

▎ - Named session contexts — allow tagging a session (e.g. saltstack, gitlab) so memory files are grouped under that name
▎ - Session picker on startup — optionally prompt: "Found previous contexts: [saltstack] [gitlab]. Which would you like to load?"

▎ Current workaround

▎ Starting Claude Code from a project-specific subdirectory (e.g. ~/saltstack/) gives natural isolation since memory is directory-scoped. Worth
documenting as a best practice.

▎ Use case

▎ A home-lab / DevOps user managing multiple systems (Kubernetes, Salt, GitLab…) wants to resume the right context without mixing concerns across
sessions.

✻ Cooked for 33s · 2 background tasks still running (↓ to manage)

Proposed Solution

Proposed solution

▎ - Named session contexts — allow tagging a session (e.g. saltstack, gitlab) so memory files are grouped under that name
▎ - Session picker on startup — optionally prompt: "Found previous contexts: [saltstack] [gitlab]. Which would you like to load?"

Alternative Solutions

Current workaround

▎ Starting Claude Code from a project-specific subdirectory (e.g. ~/saltstack/) gives natural isolation since memory is directory-scoped. Worth
documenting as a best practice.

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

Use case

▎ A home-lab / DevOps user managing multiple systems (Kubernetes, Salt, GitLab…) wants to resume the right context without mixing concerns across
sessions.

Additional Context

_No response_