ccsession

An fzf-powered session picker for resuming local agent sessions.

ccsession lists local agent sessions (Claude Code by default, with optional OpenCode, Grok, Codex, Pi, Oh My Pi, Kiro CLI, and Cortex Code backends), lets you fuzzy-find across all of your projects with a live preview pane, and resumes the one you pick in its original working directory.

Features

• Cross-project listing — every session from every project in one view, sorted by last activity.
• Three search modes — fuzzy (default), directory-only, and full-text grep over JSONL transcripts, with configurable mode-switch keys.
• Live preview — last 30 messages of the highlighted session, with timestamps and roles. In grep mode the matched query is highlighted in the preview so you can spot the hit at a glance. Set CCSESSION_PREVIEW_MESSAGES to change the preview length.
• Faithful resume — chdirs back to the session’s original cwd before exec’ing the selected agent’s resume command, so paths and tooling Just Work.
• Single static binary — written in Go with no cgo; bundles a pure-Go SQLite reader (for OpenCode support) and a small TOML parser for the optional config file.

Requirements

ccsession depends on newer fzf actions such as transform, rebind, unbind, disable-search, and change-nth. The newest of those, change-nth, landed in fzf 0.58.0, so older versions may start but the mode switch bindings will not work correctly.

Install

Go

go install github.com/sorafujitani/ccsession/cmd/ccsession@latest

Requires Go 1.25 or newer (the pure-Go SQLite reader for OpenCode support needs it; see #52).

Version metadata is recovered from runtime/debug.ReadBuildInfo, so ccsession --version works for go install builds as well.

Pre-built binaries

Grab the ccsession___.tar.gz for your platform from the Releases page, extract it, and drop the binary somewhere on your PATH:

tar xzf ccsession_0.1.0_darwin_arm64.tar.gz
install -m 0755 ccsession ~/.local/bin/

If macOS Gatekeeper complains:

xattr -d com.apple.quarantine ~/.local/bin/ccsession

Nix flake

nix run github:sorafujitani/ccsession             # one-off
nix profile install github:sorafujitani/ccsession # install into a profile

Homebrew

brew install sorafujitani/tap/ccsession

The formula lives in sorafujitani/homebrew-tap and GoReleaser refreshes it on every tagged release. fzf is installed as a dependency; the claude CLI must be installed separately. opencode, grok, codex, pi, omp, and kiro-cli are needed only with their matching --source backends — they back optional features (unlike fzf, which is always required), so they are intentionally left out of the formula’s depends_on. cortex (Cortex Code CLI) is similarly optional and only needed with --source=cortex.

Usage

ccsession                            # list -> fzf -> resume
ccsession --grok                     # use Grok sessions from ~/.grok/sessions
ccsession --codex                    # use Codex sessions from ~/.codex/sessions
ccsession --pi                       # use Pi sessions from ~/.pi/agent/sessions
ccsession --omp                      # use Oh My Pi sessions from ~/.omp/agent/sessions
ccsession --kiro                     # use Kiro CLI sessions
ccsession --cortex                   # use Cortex Code sessions from ~/.snowflake/cortex/
ccsession list  [--grep Q] [--regex] # emit TSV rows to stdout
ccsession list --json --grep Q --limit 5 # emit structured rows for agents
ccsession preview [--query Q] [--regex]  # render the preview pane (Q highlighted)
ccsession preview --json         # emit structured preview data for scripts/agents
ccsession preview --no-color     # force plain preview output
ccsession resume-spec            # print the resume target without launching it
ccsession resume                 # chdir to the session's cwd, exec the selected agent
ccsession last [-n]                  # resume the most recent session
ccsession last [--here] [--exclude-dir ] # scope to current dir, exclude paths
ccsession --version
ccsession --help

Agent Skill

This repository ships a Codex Agent Skill at .agents/skills/ccsession. Use $ccsession when you want an agent to recover prior context, compare historical sessions, preview a likely match, or hand off to a previous local agent session.

When Codex is working from this repository checkout, Codex discovers the repo-local skill from .agents/skills/ccsession. Invoke it explicitly with $ccsession or ask for the same workflow in natural language, for example:

Use $ccsession to find the session where we worked on issue 84.

If you installed only the ccsession binary and want the skill available from other repositories, install it with the skills CLI:

npx skills add sorafujitani/ccsession --skill ccsession

Here --skill ccsession selects this skill from the repository. The skill itself is the standard Agent Skills directory format: a folder with SKILL.md plus optional resources.

For a user-wide install:

npx skills add sorafujitani/ccsession --skill ccsession -g

When developing from a local checkout, install from the current directory:

npx skills add . --skill ccsession

Start a new Codex session after installing or updating the skill so the skill metadata is reloaded. The skill assumes the ccsession binary is on PATH.

The skill teaches agents to use ccsession in a read-first workflow:

1. Search candidates with structured output:

   ccsession list --json --grep "" --limit 5
   

   Use a source selector when the target backend is known:

   ccsession --codex list --json --grep "" --limit 5
   ccsession --source all list --json --grep "" --limit 5
   

2. Summarize a small candidate set for the user. The JSON rows include source, id, locator, cwd, cwd_basename, label, last_activity, cwd_exists, and cwd_unknown.

3. Preview the selected candidate before recommending resume:

   ccsession preview --locator "" --query "" ""
   ccsession preview --json --locator "" ""
   

4. Show the non-launching handoff target:

   ccsession resume-spec --locator "" ""
   

   resume-spec prints the selected backend, working directory, binary, and arguments as JSON. It does not start an interactive process.

5. Run ccsession resume --locator "" "" only after explicit user confirmation. resume changes into the recorded cwd and execs the selected agent CLI, replacing the current process.

When using --source, repeat the same source selector on list, preview, resume-spec, and resume; global flags apply only to that ccsession process and the fzf children it starts.

Keys inside fzf

The three mode-switch keys are the defaults and can be overridden (see below).

Configuring the keybindings

If a mode-switch key clashes with your terminal, shell, or muscle memory, you can remap any of the three. Keys are resolved in this order (first wins):

CLI flags > environment variables > config file > defaults

The on-screen header is regenerated from the resolved keys, so the hint always matches what is active.

# CLI flags (highest precedence)
ccsession --bind-grep ctrl-r --bind-fuzzy alt-f

# environment variables
export CCSESSION_BIND_GREP=ctrl-r
export CCSESSION_BIND_DIR=ctrl-o
export CCSESSION_BIND_FUZZY=alt-f

Config file at ~/.config/ccsession/config.toml (lowest precedence before defaults; honors XDG_CONFIG_HOME). ccsession only reads this file — it never creates it, so create it yourself only if you want file-based overrides:

[keybindings]
grep  = "ctrl-r"
dir   = "ctrl-o"
fuzzy = "alt-f"

Any key you leave unset falls through to the next source. A key name must be lower-case fzf syntax (ctrl-r, alt-f, f1, …); the three keys must be distinct and must not be a reserved fzf event name (enter, change, …), or ccsession exits with an error instead of starting the picker.

How it works

1. ccsession list reads the selected backend (~/.claude/projects/*/ by default, or --source=opencode / --source=grok / --source=codex / --source=pi / --source=omp / --source=kiro / --source=cortex) and prints one TSV row per session (id, locator, epoch, relative time, cwd basename, label). ccsession list --json --limit N emits the same candidates as a JSON array for agent integrations.
2. fzf consumes the TSV. The three key bindings swap fzf’s matcher between fuzzy mode, directory-only mode, and grep mode (which reloads via ccsession list --grep on every keystroke). The current query is also forwarded to the preview as ccsession preview --query , which highlights its matches in the rendered messages.
3. ccsession resume-spec resolves the same target as resume and prints the source, cwd, binary, and arguments as JSON without launching anything.
4. On Enter, ccsession resume resolves the session’s original cwd, chdirs into it, and execves the selected agent’s resume command so the resumed process fully replaces the picker.

Backend-specific homes can be overridden with GROK_HOME for Grok, CODEX_HOME for Codex, PI_CODING_AGENT_SESSION_DIR for Pi, and PI_CODING_AGENT_DIR / PI_CONFIG_DIR for Oh My Pi. KIRO_HOME overrides Kiro CLI’s v2 and v3 store, which defaults to ~/.kiro. Codex defaults to ~/.codex, reading sessions from its sessions subdirectory; Pi reads sessions from ~/.pi/agent/sessions, and PI_CODING_AGENT_SESSION_DIR points directly at that sessions directory. Oh My Pi reads sessions recursively from ~/.omp/agent/sessions; PI_CODING_AGENT_DIR overrides the agent root, while PI_CONFIG_DIR changes the config root under the user’s home when the agent-root override is unset. ccsession reads the resulting agent/sessions subdirectory. CORTEX_CODE_HOME overrides the Cortex Code store, which defaults to $SNOWFLAKE_HOME/cortex (SNOWFLAKE_HOME itself defaults to ~/.snowflake). Sessions are read from its conversations subdirectory, and each session’s Snowflake connection name is preserved for resume (cortex --resume -c ).

Development

nix develop                    # Go + fzf + gopls + goreleaser
go build ./cmd/ccsession
go test ./...

Snapshot a release locally

goreleaser release --snapshot --clean --skip=publish
ls dist/

Build with Nix

nix build
./result/bin/ccsession --version

Contributing

Bug reports and pull requests are welcome at . For larger changes, please open an issue first to discuss what you’d like to change.

License

MIT