fix(agent): raise output limit and allow 3 recoveries

[atishpatel]

Summary

Raise the built-in output and recovery defaults so long-running agents have more room to finish useful work instead of terminating after repeated 32,768-token reasoning-only responses.

• Raise BUZZ_AGENT_MAX_OUTPUT_TOKENS from 32,768 to 65,536
• Raise the finite output-truncation recovery allowance from 2 to 3 via BUZZ_AGENT_MAX_TOKEN_RECOVERIES; 0 still disables recovery
• Strengthen the recovery prompt so the model stops prolonged reasoning, uses tools immediately, and builds scripts or artifacts in small verifiable steps
• Preserve the safety invariant that incomplete truncated tool calls are discarded and never executed
• Keep proactive handoff independently at 90% of BUZZ_AGENT_MAX_CONTEXT_TOKENS (180,000 tokens with the 200,000 default), regardless of the output allowance
• Add request-loop and configuration regressions for exact-N recovery, disabled recovery, successful tool-first recovery, discarded truncated calls, and finite round bounds

BUZZ_AGENT_MAX_OUTPUT_TOKENS remains an explicit per-agent deployment setting. Operators should configure it at or below the served model's output limit; this PR does not perform live provider capability discovery or automatic clamping.

Risk: Medium — this increases the default request size and permits one additional recovery attempt by default. Recovery remains finite and bounded by BUZZ_AGENT_MAX_ROUNDS. Deployments whose served model rejects 65,536 output tokens must set a lower per-agent value.

Current output limits

• model - output token max
• DeepSeek V4 Flash - 384,000 tokens
• Qwen 3.8 (Max) - 131,072 tokens
• GLM 5.2 - 131,072 tokens
• GPT 5.6 - 128,000 tokens
• Claude Opus 5 - 128,000 tokens
• Gemini 3.6 Flash - 65,536 tokens
• Kimi K3 (Moonshot)- 131,072 tokens

Related issue

None found. Originating benchmark analysis: buzz://message?channel=c3252dd2-0142-4e01-88c7-a2183c3960a5&id=91e991aab5fd49094583c3937477f6c12db57a41d86edf7fd4745d0d57d10017

Testing

• cargo fmt --all -- --check
• cargo test -p buzz-agent — 595 passed, 0 failed, 0 ignored at bd6de557b367850f50325bafdd3c046131942bef
• cargo clippy -p buzz-agent --all-targets -- -D warnings
• Previously failing cancelled_turn_with_usage_emits_notification_before_response passed alone and in the full rerun
• Push hooks passed: organization guard, branch skew, Rust tests, and Desktop Tauri checks

Update — 2026-08-11

Per review feedback, the recovery default is 3. The OpenRouter live /models output-cap discovery, cache, request clamp, and related tests/documentation were removed. Per-agent output configuration is now the sole output-cap mechanism. Proactive handoff and its pre-usage byte fallback now depend only on 90% of BUZZ_AGENT_MAX_CONTEXT_TOKENS; with the 200,000 default, the handoff threshold is 180,000 regardless of BUZZ_AGENT_MAX_OUTPUT_TOKENS.

Generated with Brainy Bumble

Targeted validation — 2026-08-11

Ran the exact PR binary once on each of the 11 benchmark tasks causally affected by the previous 32,768-token ceiling, using OpenRouter with deepseek/deepseek-v4-flash-0731 pinned to Fireworks and maximum reasoning effort. Relay-429 collection failures were excluded and rerun at concurrency 2.

• 6/11 passed: circuit-fibsqrt, feal-linear-cryptanalysis, model-extraction-relu-logits, path-tracing, schemelike-metacircular-eval, and sqlite-db-truncate
• 5/11 reached the benchmark deadline: adaptive-rejection-sampler, dna-assembly, path-tracing-reverse, regex-chess, and write-compressor
• regex-chess reached exactly 65,536 output tokens, triggered one output-limit recovery, and then reached the deadline. This directly confirms that the larger ceiling and recovery path were active, but not that recovery guarantees completion.

For context, ten of these tasks were 0/5 in the historical baseline; sqlite-db-truncate, the clean control, was 4/5. This is targeted one-attempt-per-task validation rather than a statistically powered comparison. The result should not be attributed solely to the recovery default of 3: this PR also raises the output ceiling and strengthens recovery behavior, and OpenRouter routing conditions may differ from the historical direct-Fireworks runs.

Generated with Brainy Bumble