On a flat AI subscription, every session costs something the moment you open it, whether or not anything ships. ccusage and similar tools will tell you the total. They won't tell you which part of that total actually turned into a commit.
We added two commands to Estela this month that try to answer that, starting from data the tool was already collecting for estela ai-cost --by branch: the hours in a session, and whether that session's branch ever got a commit linked to it.
Two different ways money disappears
estela ai-cost --undelivered splits the unlinked spend into two buckets that never overlap:
- Sessions without a commit: a chat with no commit of yours in that repo during it, or in the half hour after it ends. If a commit does land on that branch later, it moves out of this bucket entirely, because iterating before you're happy with the result is still work.- Stale branches: a branch that has AI cost attached to it but has sat idle for 14 days by default (configurable with --stale-days), with nothing delivered on it since.The two cases are easy to confuse and worth keeping separate. The first is exploration you walked away from mid-session. The second is a branch you fully intended to come back to and didn't. Lumping them into one "wasted spend" number hides which problem you actually have. ### Nothing new is being tracked This is the part we liked most about building it: there's no new instrumentation. Estela already links a session's cost to a branch to answer "what did this feature cost" for billing. --undelivered just asks the inverse question of the same linkage: which branches have cost attached to them and nothing to show for it. That also means the same caveats from the attribution system apply here. A PR merged with squash leaves no merge commit, so a branch can look stale even after it shipped, unless the squash merge is read from the PR itself. Copilot sessions count their hours but carry no cost, since Copilot is a flat subscription with no per-token price. Anything with no basis for attribution goes to "Unattributed," not spread across projects by guesswork. ### Why bother None of this is about feeling bad over an abandoned branch. It's about having a real denominator. "I spent $40 in AI this month" means something different once you know $6 of it never turned into a commit versus $6 of it is sitting on a branch you're still actively iterating on. Only one of those is actually a problem to go fix. Estela is open source and runs entirely on your machine: npx estela setup rebuilds your history from what Claude Code, Codex, Copilot and git already wrote to disk, nothing leaves it. If this is useful to you, a star helps more people find it: https://github.com/jdleonruiz/estela-cli?utm_source=devto&utm_medium=post&utm_campaign=undelivered-spend
Top comments (0)