Discussing Sub-Agents and Reasoning Mode Costs
reach_vb · x · 2026-07-12
The post discusses practical behaviors within a coding/agent workflow:
- It is pointed out that GPT 5.6 Sol only uses subagents in Ultra mode, unless explicitly prompted in other modes.
- It suggests testing medium / high / xhigh based on different experiments and workflows to observe the required reasoning effort.
- Another reply mentions that excessive triggering of subagents in certain "code-fixing" loops can incur unnecessary costs. It advises considering a switch back to a token-based approach and trying to write guidance into skill or subagent configurations to limit reasoning intensity.
Related event: GPT-5.6 Subagent Mechanism Sparks Cost and Over-triggering Controversy(5 posts)→
More from coding & agent
- Firecrawl offers 2.5x credits to a16z Speedrun founders, unveils $75M Series B — devdigest · 2026-10-27
- Chums: open-source Apple Watch app puts Claude Code and Codex on your wrist — brandon_galang · 2026-10-27
- Open-source Clairic Studio turns pasted text into typed data and working code in 5 languages — dfinke · 2026-10-27
- Matt Pocock shares expand/contract trick: split one-way-door PRs to de-risk big changes — mattpocockuk · 2026-10-27
- Qdrant builds Universal I/O to run vector search mmap code on object storage — qdrant_engine · 2026-10-27
- theo publishes tstack skills, Garry Tan urges everyone to 'publish your stack' — ycombinator · 2026-10-26