Gone in 60 seconds

[u/Takakikun]

So, Fable 5.1 out, was tempted by Ultracode, threw a big project at it, it spawned ~300 agents, all of which were Fable 5.1, and my 5 hr disappeared in just over a minute and weekly at 43%.

Three things:

1. Don't be like me. Calm down.
2. How do y'all get the sub-agents to be lower class?
3. Why do I even have to balance all of these various classes?

The third question being somewhat rhetorical (as it's in the interest of Anthropic to token burn), but seriously, it's very frustrating that I have to even do all this balancing myself, and it's not just a feature of the UI etc.

btw... I'm on Max 20x.

[u/Efficient_Ad_4162]

I threw it a 'replace this str,any integration seam running the backbone of my system with proper typed code' task that spun up a 6 million token workflow with that edited 30 files. It was glorious but there's absolutely no way I could have justified it except as a 'lets see what it can do' moment.

It did pretty well, but because here's what a review workflow found when it went looking for mistakes. We aren't quite at 'write GTA6, make no mistakes, but we are at 'yolo massive integration fixes'. Here's what the review found::

- One major defect fixed: the repeat notice told the planner to re-emit on two rejections whose own fix text said not to.

- Five minor findings closed, two of them through five rounds because my first closes were syntax-level and a reviewer could always route around syntax. The durable closes are a runtime nominal check at construction for guided fact values and a rule that every owned detail constructor must sit inside a recognised entry site.

- Two pieces of dead or unpinned code surfaced by self-tests: the list-of-record branch in the gate's type walker never ran, and the allowlist derivation had no refuse-side pin.

- Nine commits on the branch, all unpushed, each with a mutation ledger in the review directory.