ccbox
Original:🇺🇸 English
Translated
Inspect and summarize local Codex/Claude session logs using the ccbox CLI (projects, sessions, history). Use when asked to list discovered projects, find sessions for the current repo/folder, print a session timeline, or produce an evidence-based “what happened” report from a session .jsonl log under CODEX_SESSIONS_DIR.
17installs
Sourcediskd-ai/ccbox
Added on
NPX Install
npx skill4agent add diskd-ai/ccbox ccboxTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →ccbox
Inspect local agent session logs via CLI and produce quick, evidence-based insights.
ccboxQuick start
- List discovered projects:
bash
ccbox projects- List sessions for the current folder (auto-detect project):
bash
ccbox sessions
ccbox sessions --limit 50 --offset 0 --size- Inspect the latest session for the current folder:
bash
ccbox history
ccbox history --full
ccbox history --limit 200 --offset 0 --full --size- Inspect a specific project or log file:
bash
ccbox sessions "/abs/path/to/project"
ccbox history "/abs/path/to/project" --full
ccbox history "/abs/path/to/session.jsonl" --fullWorkflow (recommended)
- Confirm is available (
ccbox).ccbox --help - Gather facts first (do not guess):
- Use to select the latest session for the current folder, or
ccbox sessionsfor an explicit project.ccbox sessions "/abs/project/path" - Copy the from the first line.
log_path - Run to capture evidence (tool calls, tool outputs, errors).
ccbox history "/abs/log.jsonl" --full
- Use
- Produce an insights report:
- What the user wanted (first USER prompt).
- What the agent did (sequence of tool calls + key outputs).
- What changed (files/commands visible in tool outputs).
- What failed or is risky (warnings, truncated timelines, panics/errors in outputs).
- Next steps (concrete verification commands and follow-ups).
References
- CLI commands + output formats:
references/cli.md - Insights checklist + report template:
references/insights.md