How one dev routes coding tasks across 5 model tiers from local Qwen to Opus

Short_Regular_7191 · reddit · 2026-10-12

A solo maintainer of a large production web app (Node/Express, Svelte, PostgreSQL+Oracle, hundreds of Cypress tests) shares his multi-tier coding stack: local Qwen3.8 Coder (free, no-decision work) → Haiku 5.5 (parallel mechanical lanes) → Sonnet 5.5 (orchestration, diff review) → Opus 5.5 (parent session, debugging, DB ops) → Fable 5.1 (strict audits and architecture). The biggest token savings come from keeping the orchestrator's context small: sub-agents read big files and reply with 5-line summaries, repeated work becomes scripts the model only reads output from, context compacts at 80%, and models are never switched mid-session to preserve caching. Tasks are graded on an R0–R9 matrix, with DB/irreversible operations restricted to Opus in-session plus human approval.

Original post →

More from coding & agent

coding & agent channel →