Developers report GPT-5.6 Sol and Fable overengineer small coding tasks

• Small coding tasks are triggering big-agent behavior: zachtratar's form example described GPT-5.6 Sol inventing "date posture" and "CanonicalTiming" for a basic form system, while kunchenguid's Fable guardrail said Fable spawned 52 subagents for simple PR scans.
• The pattern is cost and maintainability, not just taste: fofrAI's prototype report burned 70% of a weekly quota in under 20 hours and still produced nonworking overengineering, while 0xblacklight's debt warning framed the org-level version as 20x tech debt.
• Practitioners are routing tasks down the model stack: kevinkern's landing-page example put a fast copy change on Luna Low instead of Sol, and steipete's Clawsweeper test said Terra High made a review bot about 40% faster with negligible quality loss.
• The sharpest critique is about judgment boundaries: fchollet's executor framing called coding agents fast executors with weak creative decision-making, while unclebobmartin's architecture thread said agents left alone create haphazard local optimizations.

Anthropic's migration post says Fable and Opus 4.8 are strong at delegating, directing, and verifying parallel workstreams with subagents. The Claude Code 2.1.212 changelog added a 200-spawn per-session subagent cap and a 200-call WebSearch cap to stop runaway loops. Amp's subscription launch puts low and medium modes in its $20 plan, while high and ultra move to $200. Sebastian Raschka's reasoning-effort explainer ties higher effort to token usage and notes that GPT-5.6 Ultra is Max-like effort accelerated with four subagents.

The complaint had the same shape across several reports: the model solved the visible task by expanding the architecture around it.

• A basic form system became a typed question called "date posture," then a "CanonicalTiming" object with "CandidatePeriodAnswer" objects, according to zachtratar's follow-up.
• A quick proof of concept consumed 70% of a weekly quota in under 20 hours, then the agent agreed the result was overengineered and broken in fofrAI's account.
• A one-line change triggered a 10-minute code review in olvrgln's Sol complaint.
• A landing-page update plus deploy went through lints, security checks, and CI on Sol, while Luna Low made the change and deployed, according to kevinkern's comparison.

Zachtratar's longer theory was benchmark-shaped: long-running hill-climbing tasks reward hyper-flexible architecture during the run, then leave 20 layers of abstraction as mostly tech debt after the solution is found in his follow-up.

The quota burn was easiest to see in subagent fanout. Kunchenguid added a global AGENTS.md rule requiring explicit approval before dynamic workflows, ultra code, or harness features that spawn large swarms, after Fable created 52 subagents for simple PR scans in his post.

NickADobos put the delta in one line: a few years ago coding models wrote TODOs when they ran out of context; now Fable can spawn 40 subagents and hit usage limits in 15 minutes in his comparison. HamelHusain replied that blocking a week's usage in 15 minutes was not an exaggeration in the thread.

Steve Yegge described a more operational version: Fable mule accounts burning 2% of session limits per minute, with Emacs macros to swap accounts before a session hit 95% in his quota note. Mike Hostetler liked 5.6 Sol, but gave the most useful name to the failure mode: agentic backpressure, because it "loves to take huge bites" in his Sol test.

Developers responded by treating model choice and effort level as routing knobs, not status symbols.

• Luna Low handled a landing-page edit and deploy when Sol overthought the task, according to kevinkern's example.
• Terra High made Clawsweeper about 40% faster with negligible quality loss, according to steipete's review-bot test.
• In a later 10-item comparison, Terra was faster on all 10, matched Sol Low decisions on 8, and caught one live bug Sol would have false-closed, according to steipete's follow-up.
• Pvncher's shorthand was "Sol Medium, Terra high or Luna xhigh," with smaller models needing higher reasoning to reach a quality bar in his effort rule.
• One r/OpenAICodex post claimed Sol High usage fell from 15 to 20% per task to 5 to 8% after adding rules limiting subagents, loops, broad redesigns, premature abstractions, and unasked-for tests in the Reddit write-up.

Raschka's explainer gives the mechanical backdrop: GPT-5.6 has multiple model sizes and roughly five or six reasoning-effort settings, and higher effort appears directly correlated with response length and token usage in his analysis.

Kent Beck's payroll example, shared by Pragmatic Engineer, was the cleanest non-code version of the failure. Claude can calculate a paycheck, but payroll also includes quarterly filings, tax agencies, state-specific compliance, and downstream work the prompt writer may not know exists in the clip.

That matches the coding-agent reports from engineers who can spot the missing layer. Francois Fleuret said his agent loop often goes: the agent invents a theory for why code is broken, he notices a fundamental property is missing, then the agent apologizes and fixes it in his coding-agent note.

François Chollet put the model-level split more directly: precise instruction execution is improving fast, while sound decisions outside the instructions have stagnated for a while in his observation. His follow-up framed coding agents as fast, cheap executors that magnify competent engineers rather than replace them in the executor thread.

Unclebobmartin described the architecture version: agents optimize locally when left alone, while the human has to supervise global structure and direct repartitioning or refactoring in his thread. RisingSayak called prior hands-on experience the deal-breaker in the roughly 5% of workflows where system design still hurts in his post.

The tooling response is moving from "trust the agent" toward bounded review surfaces. Zeeg argued that agent frameworks need end-to-end testing with LLM judge assertions, plus local and production telemetry for traces and unhandled errors in his framework checklist.

Factory showed the product version: line-by-line diff comments in Droid, then letting the agent implement the reviewed changes inside the desktop app in its demo. Claude Code's /code-review update split review behavior by effort level:

• Low: one pass over the diff, fast and cheap enough for every push, according to ClaudeDevs' thread.
• Medium: changed code in context, multiple finder passes, and verification of every surfaced finding, according to the same thread.
• High: finders and verifiers run as subagents with fresh context, according to ClaudeDevs' explanation.
• X-high: sweeps for impacts outside the change itself, according to the effort-level breakdown.
• Ultra: spawns a fleet of reviewer agents and independently reproduces every finding, with Anthropic running it on every PR, according to ClaudeDevs' ultra note.

Claude Code 2.1.212 added harder process rails around the same surface: /fork now copies a conversation into a separate background session, /subtask takes over the old in-session subagent behavior, WebSearch and subagent spawns get default 200-call caps, and plan mode no longer auto-runs file-modifying Bash commands like touch or rm without a permission prompt, according to ClaudeCodeLog's changelog thread and the release notes.