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 ...