Skip to content
This repository was archived by the owner on Aug 30, 2026. It is now read-only.

v3.1.1 — Empty-response detection, fallback chain continuation

Choose a tag to compare

View all tags
@homeofe homeofe released this 12 Apr 13:22
· 77 commits to main since this release
v3.1.1
9d8bd83

Fix: Empty responses no longer stop the fallback chain

Previously when a fallback model (e.g. Haiku) returned an empty response (0 bytes, exit 0), the bridge treated it as success and returned nothing to the user. Now empty responses trigger the next model in the chain.

Before: Sonnet hangs → Haiku returns empty → user gets nothing
After: Sonnet hangs → Haiku returns empty → try Gemini Flash → try Codex

New debug log categories

  • [EMPTY] — primary model returned no content
  • [FALLBACK-EMPTY] — fallback model returned no content, trying next in chain

Also

  • Live logs: newest entries on top
  • All 278 tests passing
Assets 2
Loading