Watched my LLM router burn $11 on a 3-word prompt. Here's the fix.

I run a personal always-on agent fleet — eight seats claiming work in parallel from a shared task board, routing across Anthropic, OpenAI, xAI, Google, and a local Ollama floor. This week the spend forensics said 26.41 in 12 hours, 18.95 of it on five Opus 5 calls. The single worst card: ▎ N9WAJHT — "Fix this issue." — burned 11.20 across 6 attempts. Still blocked. Three words. No detail. No priority signal. It landed in my router's general (zero-signal catch-all), which I'd just re-tiered to L3 because I was tired of "the good models never get used." Vague title × top-brain × retry cascade = a small personal disaster. Five things I changed this afternoon: general back to L2, but keep everything else at their new floors. Reasoning and security stay L4 (Opus 5-class). Code and UI stay L3. Only the zero-signal catch-all got cheapened. Real work still gets the good brain; unsignalled work no longer buys it by default. Widened the ops (bookkeeping) signal list to catch complaint-shaped titles. Regexes for wtf, why is/does/hasn't, what is going on, nothing works, how come, fix this|that|it. These titles route to ops → L1 → gemini-flash-lite (~0.10/M in) instead of general → Opus. Frustration cards no longer trigger frontier models. Per-kind attempt caps. General/ops/speed/bulk cap at 2 attempts; code/UI/reasoning/security keep 3. N9WAJHT would have stopped at 2 = ~3.70 instead of 11.20. Vague retries compound cost; capping the compounding is the fix. Budget circuit-breaker. When today's spend crosses 60% of the daily USD ceiling, general and ui auto-downgrade to L2 for the rest of the UTC day. Reasoning + security + code keep their tiers. It's a soft guardrail: never blocks a task, just picks a cheaper rung. Resets at midnight. Fixed a driver-side reporting bug. Grok agents (and older Claude/OpenAI ones) reliably print a protocol exit line like BLOCKED (reason) but often forget to call the actual vintask block CLI. The driver was mislabeling all of these as "no status recorded" and losing the reason. Added a post-exit parser that accepts the self-declared verdict, extracts the reason text (anchored at line start, optional emoji, optional TID — regression-tested so prose containing the word "BLOCKED" doesn't false-positive). Verified live on the same test cases: "Fix this issue." → ops @ L1 → gemini-3.5-flash-lite (~0.01) "wtf is happening" → ops @ L1 → gemini-3.5-flash-lite "refactor auth module (+detail)"→ code @ L3 → grok-4.3 "analyze tradeoffs of splitting"→ reasoning @ L4 → claude-opus-5-5 Same 12h workload replayed against the new rules: ~7 instead of $26, with top-brain preserved for the reasoning/security cards it actually earned. The bigger lesson I keep re-learning: cost isn't a tier problem, it's a signal problem. The 2026-08 pass raised general to L4 because "top-brain by default is safer" — measured cost was 96% Opus. The 2026-09-20 pass dropped it to L2 because "cheap by default is safer" — user complaint was "the good models never run." Neither is right. What's right is making the signal set catch enough of the cheap work that the default rarely matters, then defaulting cheap. Happy to go into the signal design, the budget circuit-breaker pattern, or the verdict-parser regex if anyone's building similar. Especially curious what other people are doing to prevent runaway spend on multi-agent setups — the cross-provider failover ladder is fun but every hop is a chance to burn. submitted by /u/Vintaclectic [link] [comments]

Running an AI SaaS against local Ollama models — what actually breaks when you swap the provider

Source: r/ollama | 2026-09-25

Related