# Claude Sessions > List recent Claude Code sessions (name, last message date, working directory, last prompt) and resume any of them in new iTerm tabs. Use this whenever the user asks about their past or recent Claude sessions, wants to see or page through their session history, asks what they were working on in another session, or wants to reopen, resume, or "bring up" one session or the last N sessions — in a new tab or a new window — even if they never say the word "session". - Skill: `inancgumus/claude-sessions` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add inancgumus/claude-sessions` - Raw SKILL.md: https://api.skillmd.com/api/skills/inancgumus/claude-sessions/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: inancgumus (https://skillmd.com/u/inancgumus) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/inancgumus/claude-sessions --- # Claude sessions The bundled script reads the local session transcripts, so it works without any network calls. Run it from this skill's directory: ```bash scripts/cc-sessions list # 10 most recent sessions scripts/cc-sessions open 1 2 3 # resume those three, one new iTerm tab each ``` ## Listing ```bash scripts/cc-sessions list -n 5 # 5 most recent scripts/cc-sessions list -n 5 --offset 5 # next page scripts/cc-sessions list --all # everything scripts/cc-sessions list --cwd ~/grafana/k6 # only sessions started under a path scripts/cc-sessions list --exclude vivid-cobra --exclude rapid-badger scripts/cc-sessions list --skip-live # hide sessions already open in a tab scripts/cc-sessions list --json # same data, machine-readable ``` Columns: index, session name, last message date (local time), state, iTerm tab name, working directory, session id, last prompt typed. The session running the command is dropped from the list; add `--include-current` to keep it. The `ITERM TAB` column shows up only for sessions that are open right now, and only when iTerm is already running. It is the name of the tab the session sits in, matched by tty, so the user can find the tab they mean. `--no-iterm` skips that lookup. Report the output as a markdown table, keeping the index numbers, because the user selects sessions by index. Keep the session name and the last message date in the table: those are how the user recognizes a session. When there are more pages, say so and offer the next page instead of dumping everything. A `~` after the date means the session has no message timestamps and the date comes from the file's modification time. An empty state column means the session is not running; anything else (`idle`, `busy`, `shell`, ...) is the live status Claude Code reports for a session that is open in some tab right now. `--pager` pipes the output through `$PAGER` (default `less -SRFX`). That only helps a human at a terminal, so use `--offset` for paging instead. ## Resuming ```bash scripts/cc-sessions open 2 # one session, new tab scripts/cc-sessions open 1-3 7 # ranges and single indexes mix scripts/cc-sessions open golden-orca # by name scripts/cc-sessions open 10951267 # by session id or id prefix scripts/cc-sessions open -n 5 --skip-live # the 5 most recent not already open scripts/cc-sessions open 1 2 --window # one new window, a tab per session scripts/cc-sessions open 1 --dry-run # print the commands, open nothing ``` Each tab runs `cd && claude --resume `. ## Naming the tabs Tabs keep Claude Code's own title by default (`✳ `, which also shows whether it is working). To label them instead: ```bash scripts/cc-sessions open 3 --tab-name "kb: k6 notes" # one tab, one name scripts/cc-sessions open 1 2 --tab-name kb --tab-name docs # a name per session scripts/cc-sessions open 1-3 --tab-name review # review 1, review 2, review 3 scripts/cc-sessions open 1-3 --name-tabs # from each session's prompt scripts/cc-sessions open 1-3 --name-tabs cwd # or name, cwd, id ``` A named tab gets `CLAUDE_CODE_DISABLE_TERMINAL_TITLE=1`, so Claude stops rewriting the title and the name stays put. The name is written by the tab itself with an escape sequence rather than by AppleScript, because a zsh `preexec` hook retitles the tab when the command starts and would otherwise overwrite it. Whatever iTerm's profile appends to a tab title (the running job name, for example) still appears after the name. Ask which label the user wants when it is not obvious. They name tabs to know what each one is about, so a name they chose beats one derived from a prompt. Indexes come from the same ordering `list` produces, and that ordering shifts whenever a session receives a new message. If minutes passed since the last `list`, or if the user's request needs to be exact, pass session ids instead of indexes. `open` refuses to resume a session that is already running in another tab, since two live copies of one session write to the same transcript. Tell the user the session is already open rather than passing `--force`, unless they ask for it. ## Where the data comes from Both commands read `~/.claude/projects//.jsonl`, the transcript Claude Code appends to. Session names come from the `custom-title` records inside it, so a session that never got a name shows `-`. Sessions running right now are matched against `~/.claude/sessions/*.json`, which holds one file per live process; the script checks the recorded pid is still alive, so stale files do not show up as live. Subagent transcripts live in subdirectories and are never listed as sessions. ## Requirements macOS with iTerm2 (tabs are created through AppleScript) and python3.