Right now CCV only handles real-time streaming from claude CLI. I'd like it to also read and summarize old sessions from ~/.claude/projects/.
I review past sessions pretty often, and loading 500MB of raw JSON into Claude's context just to get a summary burns tokens. A --history mode would let me do that locally.
Session files are JSONL with user, assistant, progress, and file-history-snapshot messages. The assistant messages have thinking, text, tool_use, and tool_result blocks. Most of that is noise if you just want to know what happened - thinking blocks are huge, tool results contain entire file contents.
The mode could pull out just the useful bits: user prompts, assistant responses (minus thinking), tool names and counts, timestamps, token usage.
ccv --history ~/.claude/projects/-Users-arun-ccv/
ccv --history --since "2025-01-20"
ccv --history --project ccv --last 5
The content block parsing in types.go already handles most of these structures.
Right now CCV only handles real-time streaming from
claudeCLI. I'd like it to also read and summarize old sessions from~/.claude/projects/.I review past sessions pretty often, and loading 500MB of raw JSON into Claude's context just to get a summary burns tokens. A
--historymode would let me do that locally.Session files are JSONL with
user,assistant,progress, andfile-history-snapshotmessages. The assistant messages havethinking,text,tool_use, andtool_resultblocks. Most of that is noise if you just want to know what happened - thinking blocks are huge, tool results contain entire file contents.The mode could pull out just the useful bits: user prompts, assistant responses (minus thinking), tool names and counts, timestamps, token usage.
The content block parsing in
types.goalready handles most of these structures.