Every flag, tool, and skill.

CLI

Verbatim from sessions --help, read out of src/cli.ts when this page was built.

sessions — find and resume AI coding sessions

Browse sessions from Claude Code, Codex, Pi, and OpenCode with fuzzy search.
Scoped to the current git repo.

  sessions                    Browse all sessions with fzf
  sessions <query>            Search session content for a phrase
  sessions --here             Scope to current repo only

  --here           Scope to current git repo (default: all projects)
  --tool <name>    Filter: claude, codex, pi, opencode
  --errored        Only sessions that hit an error
  --file <path>    Only sessions that touched or read this path (substring
                   match; repeatable — every path must match). Newest first
                   when no query is given
  --mcp            Start as an MCP server (stdio transport)
  --clear-cache    Remove the search index (rebuilds on next use)
  -v, --version    Print the CLI version
  -h, --help       Show this help

  context          Print a context primer for the current repo (markdown)
                   --full widens detail; --limit/--days/--tool filter; --worktree
                   narrows to the current worktree; --out <path> writes to a file
  why <target>     Why does this code exist? Correlate a file, file:line, commit-ish,
                   or free-text topic to the AI sessions behind it. Read-only on git
                   and the index; --json emits the structured evidence
  digest <session> Print the arc of one session as compact markdown (~8k chars):
                   each genuine user turn with its exchange's final assistant
                   reply. Accepts a JSONL file path or an indexed session id
  report           Generate a usage report (HTML dashboard, opens in browser)
                   --out <path> saves instead of opening; --format json|html|both
                   (default html); --stdout prints JSON; --here scopes to the
                   current project; --from/--to/--days/--month limit the period
  wrapped          Your year with AI agents, Spotify-Wrapped style (opens in
                   browser). --year <YYYY> wraps a past year; --out/--stdout,
                   --tool, --extras <json> add agent-authored slides
  memory mine      Mine past sessions for durable facts worth remembering and
                   print the candidate batch as JSON. --repo <path> scopes to one
                   repo container (default: the current repo); --all mines every
                   repo in the index; --since-last mines only transcripts changed
                   since the previous mine
  memory pending   Count the candidates awaiting triage and preview a few of
                   them, as JSON. Reads the store only; it never mines
  memory approve   Record a triage decision for one candidate, by id from the
  memory reject    mine's batch. Rejected candidates stop being emitted; snoozed
  memory snooze    ones stay hidden until their date passes AND new distinct
                   phrasings appear — no mine can produce that bump yet, so a
                   snooze currently hides a candidate indefinitely.
                   approve takes --always-on (return this memory for every topic,
                   and first) and --scope group:<name> (assign a project group
                   from ~/.local/share/sessions/groups.json)
  memory export    Write approved memories as a portable bundle on stdout (--out
                   <path> writes a file instead). Carries no local paths and no
                   triage state; there is no transport, the file is the seam
  memory import    Merge another author's bundle in as candidates to triage.
                   Never overwrites your own approve/reject decisions
  vault status     Show the durable transcript archive: per-tool counts, total
                   bytes, and how many sessions are vault-only (source gone)
  vault inspect    Show one archived session by original path or session id
                   (<target>); prints whether it is live, archived, or both
  setup            Install plugin and configure MCP for detected tools
                   --hooks opts in to SessionStart auto-injection (off by
                   default); without it, an interactive prompt asks when on a TTY
  uninstall        Remove plugin, MCP config, and the SessionStart hook
  cleanup          Uninstall plugin + clear search index (full reset)

  With no argument, opens fzf with session summaries.
  With an argument, greps across session content for matching
  sessions, then opens fzf with the results.

MCP tools · 12

All read-only. Start the server with sessions --mcp over stdio, or let sessions setup write the config for every agent CLI it finds.

{
  "mcpServers": {
    "sessions": { "command": "sessions", "args": ["--mcp"] }
  }
}

Skills · 8

Trigger phrases are quoted straight out of each skill's own description — the text an agent matches your phrasing against. Works with Claude Code, Cursor, Codex, and anything else that reads the skills.sh format.

• /contextoptional repo path

  Prior decisions, dead ends, and the thread you left open.

  “what was I doing here”“catch me up on this repo”“context primer”“what's the open thread”

• /recallproject name or path

  The reasoning behind one past decision, without paging a transcript.

  “what did I do on [project]”“recall [topic]”“history of [project]”“when did I last work on [thing]”

• /whya file path, path:line, commit-ish, or topic

  The sessions behind a file, line, or commit — and a resume command to reopen them.

  “why does this exist”“why did we write it this way”“what was the reasoning behind this line/file/commit”“who changed this and why”

• /standup

  Yesterday and today as terse bullets you can paste into Slack.

  “standup”“what did I do yesterday”“daily summary”“what have I been working on”

• /weekly-summary

  A structured week, then a nudge toward any new memory worth keeping.

  “weekly summary”“what did I do this week”“summarize my week”“weekly recap”

• /session-metricstime period (e.g., "past week", "may", "past month")

  Which tool you actually use, and the hours you actually work.

  “how much have I been coding”“session stats”“show me metrics”“tool usage”

• /session-reflect

  Cited patterns in prompting and delegation, with small workflow experiments.

  “reflect on my workflow”“why do I keep correcting the agent”

• /memoryrepo path (optional, defaults to current repo)

  A mined batch clustered and triaged — approve, reject, or snooze each one.

  “triage memory”“review memory”“mine memory”“/memory”

Report flags

Everything after `sessions report`.

Wrapped flags

Everything after `sessions wrapped`.

Memory

The triage lifecycle, as subcommands.