Skip to main content

/sessions

A read-only view of every Claude session registered on this machine โ€” the cross-session twin of /status (which shows your work items; this shows your live sessions). No mutations.

Invokes the sessions-view skill, which reads the local session registry (.claude/session/sessions/<id>.json) written by the session-safety hooks and prints a table. Pass --ui (or ask) to also launch the self-refreshing HTML dashboard.

When to useโ€‹

  • You are running several sessions (two VSCode windows, CLI + desktop) and want to see them at a glance.
  • A session pinged you for attention (a notify-attention push arrived) and you want the claude --resume <id> hint.
  • You suspect two sessions are on the same branch+dir (a session-guard collision) and want to confirm before continuing.

Outputโ€‹

Run the skill and print the table it produces: surface ยท branch ยท dir ยท files ยท age ยท live/stale (heartbeat within SESSION_TTL_SECS, default 900s) ยท collision (another live session on the same branch+dir) ยท waiting (a permission/idle prompt the session can't clear itself) ยท the claude --resume <id> hint per session.

Lead with what needs the developer: any waiting session first, then collisions, then live, then stale.

Boundariesโ€‹

  • Read-only. Never archive, reap, or edit a registry entry โ€” the hooks own writes. To act on a session, the developer resumes it (claude --resume <id>) or closes it.
  • The registry is per-repo. By default the skill reads the current repo; for a machine-wide view it passes every active repo root (see the runbook).

Pinned โญ favorites (via /favorite) are shown too โ€” in the chat view, the HTML dashboard, and the SwiftBar menu (click to re-attach). See the favorite-session skill.