dzimplei → Features → Hot-swappable
Hit a limit and keep going on another login
A run that dies because a subscription hit its limit is not a failure worth your attention. Order your logins once, and the task moves down the list on its own.
Only the errors that another login would actually fix
The retry fires on credit and usage-limit errors specifically — the ones a different login genuinely resolves. A network blip is not retried onto another provider, because that would just fail twice and hide the real cause.
Filed work, not the conversation in front of you
Fallback applies to tasks running in the background. An attended chat stays where it is: silently moving the conversation you are watching onto another login is a surprise, not a feature.
Each retry starts a fresh session on that provider's own default model, rather than assuming the new login can resume the old one's thread.