Copasetic Flow

  This is kind of cool! I started a new project today using codex --yolo, (I didn't want to use my Claude tokens until I'd worked out the design and architecture a bit more.) When I got done coding with codex, I asked it to create a repo for the work we did. That seemed to work, but I wanted to verify that the repo was ok, so I typed  gt status and was immediately presented with  I answered y and the extension was off and running adding my new repo to Gas Town. I didn't actually have Gas Town up and running on my Linux client, so I had to get it started and then try again manually with  cd gt && gt rig add ssm_overlay https://github.com/hcarter333/ssm_overlay.git and it just worked!

 Just noting a feeling, nothing quantitative, but I think I've noticed that if more Claude agents are working at once, they each tend to create fewer subagents. If that's true, and it's a big if, I wonder if there's something at Anthropic that trottles or budgets overall effort to an account. Just to be clear, I've also watched five polecats descend into a complete and utter subagent storm like this one. True or not, I need the storms to either stop or I need to gain the ability to control them, so I'm working more on subagent storm control today. As promised, I did not watch my agents. Intead, I showed the mayor how to watch and mange polecats creating subagents. Here's the start of my conversattion At that stage, I hadn't considered the obvious fact in the figure above that subagents are occasionally beyond recursive. (As an aside, the kid here tells me this is actually a plot point in one of Matrh Well's MrubderBot books.) The next thing I asked...

 I've seen a few posts in the last week that talk about engineer's loosing their time to think because they're too busy watching what their LLM agents are doing. Anthropic's models, even under GasTown, have decide to spontaneously fork and find other ways to farm work out to subagents, occasionally causing agent storms on my project in the last week, so I can sympathize a bit more now that I did at the start of the week. There are a few solutions I'd like to propose for this issue. Here goes. How to Get Your Thinking Time Back First, if you're agents are doing marginally what you want, this is pretty simple. Stand up, back away from your desk, and leave . If it makes you feel better, setup a notification so the agent messages you when it's done. Perhaps, something like this If you don't trust your agents for the moment, still don't watch them. Come up with metrics to know if they worked or not and control your agents or modify their activities AUTOM...

 Working with Fable last week, I noticed that it can get very excited about fanning out tasks, (to the point of crashing my WSL session.) I experimented with prompting agents to split out tasks on their own, but haven't found a successful to do this yet. Consequnetly, I reverted back to my original prompt which does not explicitly call for task splits. Then, this morning, running on Sonnet 4.6, another task storm sprung up. I wonder if the new 50% higher token limit  till August is Anthropics way of buying themselves some head  room while they experiment with models creating subagents?  Are other  people seeing the same thing? It's particularly worrisome that Sonnet 4.6 has started a subagent storm becuase it really doesn't ahve the context to deal with the results.

Cooper95 Incident Report — 11 July 2026 (v1.13) Fable-5 Agent and Subagent Research Tasks and How to Evaluate Them Root-session reconstruction, eleven descendant transcripts, nine fork manifests, and eight timestamped screen captures. host Cooper95 (WSL2 guest) · project bg_trav · worker rust · root session 28797a95… Claude Code v2.1.207 · cwd /home/hcarter/gt/bg_trav/polecats/rust/bg_trav report status: v1.13 — timestamped UI and Windows host telemetry added to the v1.12 integration baseline · all times PDT (UTC−7); transcripts carry UTC §0 · Summary Tracing agentic AI processes, especially with all the new models rolling out, is incredibly valuable, and it can be easy. You can find out what's working in your agentic system as well as what's not. As an example, I've included an analysis of a fable-5 research process below. I was studying an agent that made a leap to a very good research finding, and then, ultimately, in combination with a cast of other ...