Feature Request
Problem
Claude Code stores all session transcripts in ~/.claude/projects/, but there's no way to browse them meaningfully. The current /resume command shows a bare list of session IDs and timestamps — you can't tell what any session was about without opening it manually.
Competing tools (e.g. OpenCode) offer a /sessions command that shows titled session headings, letting you browse, select, and resume a session directly from the list.
Proposed Solution
A /sessions command that:
- Lists recent sessions with a short auto-generated title/summary (derived from the first user message or the session's topic)
- Allows selection — pick a session from the list to see what was done
- Shows a summary of the selected session (what was worked on, what was completed, what's pending)
- Resumes from the selected session if desired
Current Workaround
Users have to manually parse .jsonl files in ~/.claude/projects/ or ask Claude to do it for them, which is slow and clunky.
Why This Matters
Session continuity is a core part of the agentic workflow. Without readable session history, users lose context between sessions and have to re-explain work that was already done. A simple titled session browser would make Claude Code significantly more useful for ongoing, multi-session projects.
Example UX (rough)
/sessions
Recent sessions (markets_g3pro):
1. [May 12 08:39] not_on_shift state — full implementation plan (16 tasks)
2. [May 11 17:05] Test suite fixes — TerminalContext & RPC migrations
3. [May 11 13:19] settings/terminals lock date/time feature
4. [May 09 18:20] Cross-business isolation bug investigation
...
Select a session to view summary or resume »
Feature Request
Problem
Claude Code stores all session transcripts in
~/.claude/projects/, but there's no way to browse them meaningfully. The current/resumecommand shows a bare list of session IDs and timestamps — you can't tell what any session was about without opening it manually.Competing tools (e.g. OpenCode) offer a
/sessionscommand that shows titled session headings, letting you browse, select, and resume a session directly from the list.Proposed Solution
A
/sessionscommand that:Current Workaround
Users have to manually parse
.jsonlfiles in~/.claude/projects/or ask Claude to do it for them, which is slow and clunky.Why This Matters
Session continuity is a core part of the agentic workflow. Without readable session history, users lose context between sessions and have to re-explain work that was already done. A simple titled session browser would make Claude Code significantly more useful for ongoing, multi-session projects.
Example UX (rough)