dzaurov

Claude Sessions — Communication skill for Claude Code

Communication community

Browse and resume every Claude Code chat across every project, from any terminal.

How to install Claude Sessions

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dzaurov/claude-sessions and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Sessions does

Browse and resume every Claude Code chat across every project, from any terminal. Fuzzy-search by topic, pin favorites, hide noise — Enter and the resumed session takes over your terminal.

Alternatives in Communication

Claudix - Claude Code For VSCode — by Haleclipse - A VSCode extension that brings Claude Code directly into your editor with interactive chat int 1k ★
Agentrove — A self-hosted web and macOS desktop app for Claude Code and Codex, powered by ACP 270 ★
Respond To Comments — Fetch recent comments across the user's social accounts, draft on-brand replies, like the content-free positiv 212 ★

README

ccs — Claude Code Sessions

Browse and resume every Claude Code chat across every project, from any terminal.

The problem

[Claude Code](https://www.anthropic.com/claude-code) stores every chat as `~/.claude/projects//.jsonl` — keyed by the **working directory** the session was started in. Sessions are identified only by UUID; there is no title, no summary, no preview metadata.

The built-in `claude --resume` is hard-bound to your **current** directory. So to resume a chat you have to:

Remember which directory the session was originally started in
cd there
Pick the right UUID out of a list with no preview of what's inside

If you don't remember the directory, the chat is effectively lost. And if a session was started somewhere unusual — a Docker container mount, a worktree, an SSH'd dev box, a one-off `/tmp/foo` experiment — `claude --resume` from your normal terminal will never find it at all.

`ccs` fixes all of this. One ~5 MB Go binary that: