Every morning, I run one command before my team standup:
npx cc-standup --format slack
Output:
*AI Standup — 2026-02-27 (Fri)*
✅ *Yesterday's work:*
• `client-project` — 5h 40m, +9,636 lines
• `cc-loop` — 1h 12m, +2,104 lines
📊 *Total:* 6h 52m | 63 sessions | +11,740 lines
🔜 *Continuing:* `client-project`, `cc-loop`
I paste it into Slack. Done.
The thing is: I didn't write any of that code yesterday. The AI did. So the AI writing the standup about its own work seems only fair.
What cc-standup does
It reads ~/ops/proof-log/YYYY-MM-DD.md files — session logs that Claude Code generates automatically — and formats them as a standup.
Three output formats:
# Plain text (default)
npx cc-standup
# Slack-formatted (bold, code blocks)
npx cc-standup --format slack
# Tweet-length
npx cc-standup --format tweet
Tweet format for the same day:
AI Standup 02-27 🤖
✅ client-project: 5h 40m (+9.6K lines)
✅ cc-loop: 1h 12m (+2.1K lines)
Total: 6h 52m | 63 sessions
#claudecode #aidev
Ghost Days
Some days I'm not running Claude Code at all. The AI is working autonomously in the background. There's no proof-log for those days.
cc-standup handles this:
📋 AI Standup — 2026-02-26 (Thu)
👻 Ghost Day — AI worked autonomously. No sessions logged.
It's honest: the AI ran, you weren't there, no data.
Why this is useful beyond novelty
The honest reason I built this: I have trouble remembering what I did yesterday when there are 40+ AI sessions.
The proof-log exists. The data is there. But reading it manually is like reading 40 commit messages in sequence — technically complete, practically useless.
cc-standup collapses it into the format my brain actually processes: what project, how long, what changed.
Who this is for
If you use Claude Code and don't have proof-log set up, this tool doesn't work for you (yet). Proof-log is a hook-based system that records sessions automatically.
If you do have proof-log, you now have a tool that answers "what did the AI do yesterday?" in about 3 seconds.
The full toolkit
cc-standup is part of cc-toolkit — all free, all zero-dependency, all local.
| Tool | What it answers |
|---|---|
| cc-standup | "What did the AI do yesterday?" (standup format) |
| cc-weekly-report | "What did the AI do this week?" (full report) |
| cc-ai-heatmap | "What does my AI work history look like?" (visual) |
Is your Claude Code setup actually safe? Run npx cc-health-check — a free 20-point diagnostic. Score below 80? The Claude Code Ops Kit fixes everything in one command.
npx cc-standup --format slack
Paste. Done.
Top comments (0)