Skip to content
dzimplei
Download

Keep eligible tasks moving through usage limits.

Configure a fallback order for background tasks. When an eligible usage or credit limit stops a run, another configured login may be tried.

The Northstar launch board with work in Backlog, Doing and Done

Keep filed tasks visible while the provider changes. Example data · actual dzimplei interface

Retry the failure another login can fix.

Fallback is for eligible usage and credit errors. Network failures, permission failures and provider safety stops are not invitations to switch providers.

Model and reasoning controls in the dzimplei composer
Northstar launch · example data

Keep the conversation’s boundaries clear.

Background retries start fresh sessions on the next provider’s own default model. An attended conversation is not silently moved to another account.

A Northstar launch workspace with agent conversations and a project sidebar
Northstar launch · example data

A few useful details.

Does fallback bypass a provider safety stop?

No. Safety and policy stops are not retried on another provider.

Will a different provider resume the same thread?

Not necessarily. A fallback starts a fresh session using that provider’s own default model.

Keep exploring.

Providers and models Agent team Accounts and profiles