Using GPT-6.1 Sol only as planner cuts coding API bill by 77%, local 27B writes code
GapNew4766 · reddit · 2026-09-30
A developer benchmarked three ways to build three small 3D games (pool, bowling, foosball): letting GPT-6.1 Sol do everything, having Sol only plan while a local Qwen 3.8 27B on a single RTX 3090 writes the code, and going fully local. The planner/worker split cut API spend from $0.75 to $0.17 — a 77% saving — at the cost of runtime rising from 6.6 to 43.4 minutes.
The rationale: most tokens in a coding run are the code itself, while planning and review are a small slice, so pushing the bulk of output onto a per-token-free local model saves the most. The open-source tool Atomic Agent implements this as a "Fusion" mode, but any framework that lets you set separate planner and editor models works.
Caveats: savings varied (87% on pool vs 57% on bowling, one run each); it saves API spend only, GPU and power costs remain; and the planner only checks that promised files exist, not that they work — review has to catch the rest.
Related event: Cloud Planner Plus Local Coder Cuts API Costs by 77%(3 posts)→
More from coding & agent
- shadcn boosts @uisdk: one-shot UI rebuild that's instantly E2E-testable by AI — shadcn · 2026-11-16
- AI agent deletes 43,599 lines of OpenClaw test code in one PR — vincent_koc · 2026-11-16
- JPMorgan shows Jarvis, its internal agent assembly line, at Interrupt NYC — LangChain · 2026-11-16
- Dev clarifies: Apple doesn't ban feature flags, only fooling App Review — talkaboutdesign · 2026-11-16
- Antigravity Matches Claude Cowork in Tests, While Gemini Tasks' Purpose Remains Unclear — sebajun2 · 2026-11-16
- One 16GB GPU runs songs, voice, images, 720p video and local RAG — all offline and open source — llama-of-death · 2026-11-16