Repository navigation
Help on Model Fallback feature #150
Replies: 4 comments 4 replies
|
to add onto this, my mental model of this feature was to basically be able to optimize my model provider use, as some have weekly limits, some have monthly limits and so forth, so for example one could do: Opus 4.5 via Anthropic (5 hour limit), then Antigravity (weekly limit), then Copilot (monthly usage limit) and then openrouter (at-cost) all via one virtual model. |
|
Generally, I designed this funciton to fallback same type of model for keeping our vibe coding not interrupted. |
|
It should be noted that Fallback is an experimental feature that I'm still developing. |
|
Bro, Have you joined Discord? https://github.com/nguyenphutrong/quotio/issues/138 |


Generally, I designed this funciton to fallback same type of model for keeping our vibe coding not interrupted.
For example, there are antigravity, cursor, claude code, kiro ,github copliot accounts, you are using claude-opus-4-5-thinking model in your claude code. You can create a virtual model as 'fallback-opus-4-5-thinking', add entry 1 as antigravity/gemini-opus-4-5-thinking, entry 2 as claudecode/claude-opus-4-5-thinking, entry 3 as githubcopliot/opus-4-5-thinking entry 4 as kiro/opus-4-5-thinking and so o.
In terms of sequence, the model will switch between accounts of the same provider, and then try them one by one according to the fallback order.