clawd-tracker

Your Claude Code task, tracked like a pizza order.

A bar above the prompt walks through five stages, Reading → Prepping → Cooking → Taste test → Delivered, while Clawd acts out exactly what Claude is doing right now. Underneath: the current step, a live ETA, elapsed time, tokens, context fill, estimated cost and your plan usage. When it's done you get a receipt and a ding.

Clawd's 20 costumes

| Claude is… | Clawd… | Stage | | --- | --- | --- | | Starting your request | holds up the order ticket | Reading | | Reading a file | puts on reading glasses, turns the pages | Reading | | Searching code (Grep) | sweeps a detective's magnifier | Reading | | Listing files (Glob) | ties on a bandana, scans with a spyglass | Reading | | On the web / in a browser | rides a surfboard | Reading | | Writing a task list or plan | scribbles on a clipboard | Prepping | | Thinking between steps | gets a thought bubble | (stays put) | | Editing code | flips an omelette in a chef's hat | Cooking | | Creating a file | swings a hammer in a hard hat | Cooking | | Editing CSS / SVG | paints in a beret, the brush changes color | Cooking | | Editing docs (.md, .txt) | writes with a quill | Cooking | | Editing config / other tools | turns a wrench, a gear spins | Cooking | | Installing packages | hauls a parcel on its head | Cooking | | Running subagents | juggles, while a mini Clawd per helper shows what each is doing | Cooking | | Running tests, builds, linters | swirls a bubbling flask in lab goggles | Taste test | | Running other commands | types on a tiny laptop | (stays put) | | Using git / gh | delivers a stamped envelope in a mail cap | (stays put) | | Asking you a question, or waiting for your OK | holds up a "?" sign; the bar says "Waiting on you" | (stays put) | | Done | party hat, confetti, pizza box | Delivered | | A step fails | drops the pizza: "Bash hit a snag. Regrouping…" | (stays put) | | Interrupted | drops the pizza | Stopped |

Each activity has a few verbs that rotate ("Simmering ThemeToggle.tsx", "Seasoning api.ts"), so the line never reads the same twice.

Progress and the ETA

Claude Code can't know how far along a task is, so the bar only moves on real events:

• With a task list (TodoWrite or the task tools), the fill is the share of tasks done and slides forward each time one finishes.
• Without one, it fills through the furthest stage Claude has reached. Only real test, build and lint commands count as Taste test; git and other shell commands don't move it.
• Delivered fills only when the work is done. The stage being worked on pulses.

The top right shows the job size (Small, Medium or Large, from the task count or steps so far) and an estimate:

• With a task list: this run's pace per finished task ("about 3 min left"), or, before the first one finishes, your usual pace per task ("~6 min job").
• Without one: how long your past jobs that got this far usually took ("usually about 2 min left"), or "running longer than usual". The tracker remembers your last 60 delivered jobs to learn this, and prefers the current project's own history once it has a few jobs there. Until it has some history it says "sizing up…".

Little moments

• Stage up: when the work reaches a new stage, Clawd hops and sparkles.
• Snags: when a step fails, Clawd reacts and keeps that look while Claude works out a fix.
• Waiting on you: when Claude needs your answer or your OK for a step, the top right turns amber and counts up ("Waiting on you · 1:12"), and the line underneath says what it needs. It shows after a couple of seconds, so an auto-mode check that answers itself doesn't flash it.
• Helpers: each subagent gets a mini Clawd next to the ETA, in the costume of whatever it's doing; it leaves when its work is done.
• The receipt: the delivery line sums up the job, "3 files · +42 −10 · checks ✓ · 23 steps · order #3 today". Lines are counted from Claude's edits; "checks" is the last test, build or lint run.
• The ding: a short chime when a job that took 20 seconds or more is delivered, for when you've looked away.

Themes

Same Clawd, different shop. Pick one in settings:

| Theme | Stages | | --- | --- | | pizza (default) | Reading → Prepping → Cooking → Taste test → Delivered | | coffee | Grinding → Brewing → Pouring → Tasting → Served | | rocket | Fueling → Countdown → Liftoff → Systems check → In orbit | | construction | Surveying → Blueprints → Building → Inspection → Handed over |

Usage numbers

• tok: tokens used this run, including subagents.
• ctx: how full Claude's context window (its working memory for the conversation) is. Amber from 80%, red from 90%, and a one-time tip at 85% to start a fresh conversation for the next task.
• ≈$: an estimate at API list prices. On a Pro or Max plan you aren't billed per token, so treat it as a sense of scale.
• 5h / wk rings: how much of your plan's 5-hour and weekly limits you've used, as reported by the last API response, drawn as two rings on the right. Blue, then amber from 75% and red from 90%, with a one-time heads-up at 90%. Only shown on a subscription; the terminal shows them as text.

Settings

Change them in Claude Code's /config menu, or in settings.json under pluginConfigs:

| Setting | Default | What it does | | --- | --- | --- | | theme | pizza | Stage names: pizza, coffee, rocket or construction | | sound | on | The delivery ding | | showCost | on | Show the ≈$ estimate | | showPlanUsage | on | Show the 5h / weekly usage and the 90% heads-up |

Commands

• /tracker: show or hide the tracker. The ✕ on the bar hides it too; /tracker brings it back.
• /tracker stats: today's orders, time spent, steps, tokens and the longest job.

Works in the desktop app (animated SVG) and in the terminal (text version with an emoji per activity).

What it hooks

The tracker only watches; it never blocks, rewrites or answers anything for Claude Code. Every hook passes the event on unchanged.

| Event | What the tracker does with it | | --- | --- | | session.start | Registers /tracker, loads your past job times (for the ETA) and starts a 1-second clock while a job runs | | prompt.submit | Keeps the first line of your prompt as the order's title | | turn.start / turn.complete | Opens and delivers the order; a subagent's turn adds or removes its mini Clawd | | tool.call | Picks Clawd's costume and the stage from the tool and its arguments, and counts lines for the receipt. Before a step runs it asks Claude Code's permission rules, read-only, whether the step will stop for your OK, so the band can say "Waiting on you". It never makes or changes that decision | | turn.step | Adds up tokens and the estimated cost, reads how full the context is, and shows the thought bubble between steps | | session.measure | Reads your 5-hour and weekly plan usage for the rings | | command.run (/tracker) | Shows or hides the band, or prints /tracker stats | | ui.render (AbovePrompt) | Draws the band |

It stores two things: whether the band is hidden (this session only) and your last 60 job times (to learn the ETA). It reads no files, makes no network calls and keeps no credentials. The delivery ding is synthesized in code, so the plugin ships no audio files.

Development

claude plugin validate plugins/clawd-tracker
claude plugin test plugins/clawd-tracker