Every team that put AI coding agents on subscription seats created an ecosystem by accident. Subscriptions meter usage, so seats got caps, and caps produce behaviour. Watch the usage table for a week and four species emerge.
The Tuesday Extinction. Hits the weekly cap by Tuesday and honestly does not know why. Every question is a fresh session, every session inhales the whole repo, and by Tuesday lunch the meter reads zero. Not recklessness: a workflow bug, same genus as a memory leak.
The Ghost. Has never seen the limit screen and half suspects it is a myth. Asks one precise question and closes the terminal. In the usage table this row looks like an instrumentation error.
The Absentee Landlord. Wrote a cron job months ago that runs an agent nightly, then forgot it exists. It spends a slice of the cap while its owner sleeps, faithfully, indefinitely.
The Cartographer. Writes issues so complete that anyone could implement them. Also frequently broke, because a spec that good burns tokens too. The team's best specifications and its emptiest wallet share a chair.
Before you claim the Ghost: the heaviest burners are the surest of their restraint, so let a spend plugin that reads Claude Code's local session logs and reports per project and per branch assign your species.
This is not a personality quiz
I took personality tests and this is none. The field guide documents a market with no clearance mechanism: surplus on one side, starvation on the other, same team, same tool. The variance is habits and workflow, not talent or effort.
The whispered workaround, multiple subscriptions, is a terms-of-service violation, so no.
The Cartographer scopes an airtight issue and has no budget left to run it. The Ghost picks it up cold, zero context and zero further input, and spends leftover budget to implement it. Call it the Token Donor. The donor contributes compute, not knowledge: not review, not mentorship. One person supplies the thought. The other supplies the meter.
A donor needs a floor under the generosity, and a Tuesday Extinction deserves to find out before the cap decides for them. BudgetClaw, an open-source usage guard, reads the same logs and halts the run at a limit you set.
Efficiency is a skill, and nobody grades it
Token efficiency is a real engineering skill that no ladder document mentions. We promote people for what they built, never for what they declined to spend, so the Ghost's discipline reads as a quirk instead of capacity the team already paid for.
Make the first donated run a deletion. Agents produce comments that restate the line below them and tests that assert a mock returns what the mock was told to return, and nobody funds removal from their own cap. Donated surplus is the first budget subtraction has ever had.
Comments are open: which species are you, and did a dashboard or a hunch decide? Report whether your team hosts an Absentee Landlord nobody has met; the crontab knows things the standup does not. And if a colleague's meter has ever shipped your issue, or yours theirs, file a field report; documented cases are rare.
Top comments (0)