Claude Status Update

A Claude Code plugin that automatically generates a standup-ready summary of what you built in the last 24 hours.

Timeline • Role

2025 • Built with Sebastian Tremblay

Problem

Standups are a tax on building. Every morning, developers interrupt their flow to reconstruct what they did the day before scanning git logs, digging through Slack threads, trying to mentally replay hours of context. The update itself takes minutes to say but often takes longer to remember. The irony is that all the raw material already exists locally, in your session history.

Solution

Claude Status Update parses your Claude Code session logs from the last 24 hours and produces a clean, categorized standup summary executive overview, bugs fixed, features shipped, and everything else without you typing a single word. It runs entirely on device. Nothing leaves your machine.

Part 1: Understanding the problem

The problem started as a personal annoyance. I kept showing up to standups and blanking on what I'd actually done, even after productive sessions. I'd look at my git history, piece things together, and realize I was spending real cogve energy reconstructing work I'd literally just done. The session traces Claude Code writes locally turned out to be the missing piece a structured, timestamped record of every task I'd worked on.

Part 2: Coming up with ideas and solutions

The core design decision was to keep the tool invisible. No configuration, no manual input, no UI. You run one command inside any project and get a summary back. I wrote the parser in Python to extract user messages from ~/.claude/projects/ over a rolling 24 hour window, pass them to Claude, and have Claude classify and summarize them before wiping the temp file. Local only was non negotiable from the start session traces are sensitive, and any tool that phones home with them would be a nonstarter.

Part 3: DECIDING + PROTOTYPING

The output format went through several iterations. Early versions produced a flat list, which didn't communicate effort or priority well. The final structure a 1 3 sentence executive summary followed by categorized work items (Features, Bugs, Other) mirrors how engineers actually talk in standups and gives readers a fast path to what matters most.

Part 4: ROUND OF TESTING AND IMPROVEMENTS

Distribution was as important as the tool itself. Packaging it as a Claude Code plugin meant zero setup beyond two commands and no dependency on external infrastructure. The install path /plugin marketplace add AlexanderBZ/claude-status-update drops it directly into the workflow where the session data already lives. Friction at install time kills adoption for developer tools, so getting that path as short as possible was a deliberate priority.

Reflections

This project reminded me that the best tools solve problems you've already normalized. I'd been reconstructing standups manually for months before it occurred to me that I didn't have to. The data was already there I just needed to pipe it somewhere useful. Building for yourself first is still the fastest way to find real problems worth solving.