[Feature] Allow "auto/*" combos as fallbacks for custom combos

[yodog]

Problem / Use Case

Currently, Omniroute does not support using the built-in dynamic system routing shortcuts (specifically the auto/* combos) as fallback targets.

This limitation prevents setting up flexible, automated fallback strategies. For example, if a high-tier custom combo exhausts its quota or balance, we cannot gracefully degrade the requests to a cost-effective dynamic system tier like auto/free.

Proposed Solution

Allow the selection of auto/* strings when building a combo.

When the primary custom combo fails or hits its limits, Omniroute should seamlessly hand off the request to the specified dynamic system route, triggering the standard provider/model selection logic associated with that auto/* tier.

Alternatives Considered

Building a custom fallback combo copying the content of the desired "auto" combo

Acceptance Criteria

• A custom combo can be successfully saved/configured with an auto/* route (e.g., auto/free, auto/fast).
• When the custom combo triggers a fallback scenario (e.g., rate limit, quota exhaustion, or provider downtime), the request is successfully routed to the fallback system tier.
• The dynamic selection logic of the auto/* combo executes correctly when triggered as a fallback.
• If the fallback auto/* route also fails, standard error handling or subsequent fallbacks in the list are executed normally.

Area

Proxy / Routing

Related Provider(s)

No response

Additional Context

No specific environmental blockades. This is a purely architectural enhancement to bridge the gap between custom user-defined combos and internal dynamic routing shortcuts

Expected Test Plan

Add a test case simulating custom combo exhaustion where the fallback target is "auto/free". Assert that the request is redirected and processed by one of the free tier providers.

[kilo-code-bot]

This issue appears to be a duplicate of #2099.

[Feature] Zero-config auto-routing: built-in auto combos via auto/ prefix (#2099)

Similarity score: 92%

This comment was generated by Kilo Auto-Triage.

[yodog]

this is not a duplicate of #2099 , but a follow up to improve it.

[diegosouzapw]

Closing — Antigravity CLI 2.0.1 support was aligned in PR #2443 (updated client profile, upstream headers, model aliases). Additionally, open-sse/utils/error.ts parses the "reset after Xh Ym Zs" quota text referenced in the issue.

[diegosouzapw]

Reopening — the previous close comment referenced the wrong issue due to a mapping error on my side. Re-analyzing this issue properly. Sorry for the noise.

[lanyangyangdeh]

我有ccx和cc switch，把mimo 接入codex，怎么老是中断啊

[diegosouzapw]

Hi @yodog! Thanks for the great feature suggestion! 🙏

Apologies for the earlier off-topic close (mentioning Antigravity CLI) — we've re-analyzed your request from scratch and confirmed it's not a duplicate of #2099, but a useful follow-up extension.

We've analyzed your request — it aligns with OmniRoute's roadmap and we have a clear implementation path:

Allow auto/<tier> strings (e.g. auto/free, auto/fast) inside a custom combo's fallbacks[] array — when the primary combo exhausts, OmniRoute delegates to the auto-combo resolver for that tier, with a 1-level nesting cap to prevent auto→auto loops. This is a follow-up extension to #2099, not a duplicate.

We've cataloged it internally and it will be picked up in an upcoming release.

Status: ✅ Accepted — cataloged for future implementation

We'll respond here and tag you once the implementation lands so you can test it before it ships.

Closing for now to keep our open-issue list focused on items still awaiting input. The feature is tracked in our internal backlog and won't be forgotten.

Thank you for helping improve OmniRoute! 🚀