POSTTTT

Agent CLI Session — Development skill for Claude Code

Development community

A local web app for browsing, searching, and managing the Claude Code session logs that pile up under ~/.claude/projects/.

How to install Agent CLI Session

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

What Agent CLI Session does

A local web app for browsing, searching, and managing the Claude Code session logs that pile up under ~/.claude/projects/.

Alternatives in Development

  • Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
  • Claude Code Viewer — A full-featured web-based Claude Code client that provides complete interactive functionality for managing Cla 984 ★
  • Coding Agent Session Search — Unified TUI and CLI to index and search your local coding agent session history across 11+ providers (Codex, C 708 ★

README

agent-cli-session

A local web app for browsing, searching, and managing the session logs your coding agents leave behind — **Claude Code** (`~/.claude/projects/`), **Codex** (`~/.codex/sessions/`), **Gemini CLI** (`~/.gemini/tmp/`), and **opencode** (`~/.local/share/opencode/opencode.db`).

Everything runs on your machine. No data leaves your computer, and no API calls are made. Works on macOS, Linux, and Windows.

The header has four tabs — **Claude**, **Codex**, **Gemini**, **opencode** — each with the same Projects / Search / Stats pages.


What it does

Browse

**Projects (`/`)** lists every project folder with its *real* directory path, resolved by reading the `cwd` recorded inside each session rather than trusting the lossy dash-encoded folder name. Two views, toggled by a pill at the top and remembered in `localStorage`:

  • Table — sortable by path, sessions, size, age, or last activity. Click a header to sort, click again to flip direction.
  • Tree — projects nested under their parent directories, with aggregated session count, size, and most recent activity per folder. Single-child chains collapse into one row, so /Users/me/Desktop/GitHub doesn't cost three lines. Separators follow the logs themselves, so Windows paths keep their backslashes even when viewed from another OS.

**Sessions (`/p/[projectId]`)** lists a project's sessions with title (alias → ai-title → first user prompt), message count, model, git branch, input/output tokens, file size, and session UUID.

**Transcript (`/p/[projectId]/s/[sessionId]`)** renders the JSONL as readable messages:

  • Markdown formatting — bold, italic, lists, fenced and inline code, links.
  • Slash commands (/clear, /model, …) merged with their stdout into one compact terminal-style block.
  • Tool calls merged with their matching results in a single card. Long results collapse behind a ▶ toggle with a one-line preview.
  • Collapsible "thinking" blocks.
  • Filter pills: **messages