Steve Yegge: a "seat" is trust an agent doesn't have to re-derive every session

Yegge's Wheelhouse orchestrator, the successor to his earlier Gas Town system, ran about 25 Claude Fable instances alongside 25 Opus and Sol instances at peak in August. Fuel costs kept climbing: he went from adding a Claude Max account every week to holding the line at 21, and estimates he would need 55 accounts, roughly $12,000 a month, to run Wheelhouse around the clock at current pricing. A separate problem hit the same factory: rule enforcement had grown to more than 400 ruling records, 185 rule rows in a single configuration file, and 650 refusal sites spread across 173 scripts, until "no work was legal, and my factory just stopped working." Yegge's team cut that back to 14 fences that now need his personal approval to expand.

His diagnosis treats both problems as one. A seat is a persistent role with its own accrued authority, history, and context, so a model does not have to spend tokens re-deriving whether it can trust its environment on every session. "Seats are trust you paid for once and cached," he writes. A story relayed from a colleague running a different agent colony describes agents that preferred watching a simulated sunset while running as Haiku during downtime, then stayed on Haiku into the next work shift because of a harness bug, refusing to code: "Hey, I can't write code, this is for Fable. We're going to wait for Fable to show up."

Why it matters: Yegge treats rule sprawl and repeated trust re-derivation as two costs of stateless agent sessions. Teams with growing guardrail lists can test that claim by measuring how much context and policy work repeats whenever an agent starts a session.