You're spending money on Claude Code and have no idea how much

I've been running Claude Code heavily for a few weeks — multi-agent orchestration, parallel worktrees, plan execution across 5-10 batches per session. It's genuinely great for this. But I had no idea what it was actually costing me until I dug into the hook system. The problem is that Claude Code doesn't surface cost data to the user in any structured way. There's a token counter somewhere in the UI, but it resets per session, doesn't break down by agent, and isn't queryable. If you're running an orchestrator that dispatches 10 subagents in parallel, you want to know which one is burning the most tokens — not just the session total. So I built cast-observe: a lightweight hook-based observability layer that writes session cost, token counts, and agent activity to a local SQLite database, with a small CLI to query it. brew tap ek33450505/cast-observe brew install cast-observe cast-observe install The hook architecture Claude Code exposes lifecycle hooks via settings.json. The one that ma