I tested this with Opus the day 4.6 came out and it failed then, still fails now. There were a lot of jokes I've seen related to some people getting a 'dumber' model, and while there's probably some grain of truth to that I pay for their highest subscription tier so at the very least I can tell you it's not a pay gate issue.

I would consider a lot of mobile apps to also be a 'micro-payment' type model. Clearly there's no issue with people paying for content, I think the real gap here is in the ability for the consumer to pay for the content. If I go to some random news site and it hits me with a paywall for a micro-payment there isn't a simple system by which I can actually give them money without directly signing up for a subscription to that specific site or some other service. If there was a type of wallet for this that I could just put money into and sites asked "would you like to pay X amount from your wallet to read this content?" I would be more amenable to it. It's the same idea with streaming sites and piracy. Companies have made content more expensive and more exclusive so why would I want to jump through the extra hurdles which was supposed to make consuming your content EASIER. It's always about ease of access to the consumer.

Based upon everything we know from Valve's corporate structure, they're basically their own self-contained YCombinator. They have a ton of internal 'startup' groups that are constantly trying new and boundary pushing ideas. Looking at it through this lens, it's not really a good company fit for any junior. Having juniors detracts from your seniors work, but the point is that you're supposed to get value from that when they eventually become mid-level or senior engineers themselves. But if you're constantly working in new complex environments it's hard to bring a junior up to speed and teach them the requisite skills to thrive, especially if that project they just spent 3 months getting up to speed on gets canned because the idea didn't actually pan out.

I was worried about this when I turned it on myself, but under the usage panel it shows that it limited my spending to just the $50 and that auto-reload is off, so it doesn't seem this would be the case.

I've been using Gas Town a decent bit since it was released. I'd agree with you that it's design is sub-optimal, but I believe that's more due to the way the actual agents/harnesses have been designed as opposed to optimal software design. The problem you often run into is that agents will sometimes hang thinking they need human input for a problem they are on, or they think they're at a natural stopping point. If you're trying to do fully orchestrated agentic coding where you don't look at the code at all (putting aside whether that's good or not for a second) then this is sub-optimal behavior, and so these extra roles have been designed to 'keep the machine going' as it were.

Often times if I'm only working on a single project or focus, then I'm not using most of those roles at all and it's as you describe, one agent divvying out tasks to other agents and compiling reports about them. But due to the fact that my velocity with this type of coding is now based on how fast I can tell that agent what I want, I'm often working on 3 or 4 projects simultaneously, and Gas Town provides the perfect orchestration framework for doing this.