PandaOSPandaOS
Account and help

Usage limit failover

Keep a chat going on another connection when the one it runs on reaches its usage limit.

Feature Updated 20 Nov 2026

Not on Community

Failover is part of every paid plan. On Community the switch is locked and offers the upgrade.

What failover does

A connection, such as a Claude subscription, can reach its usage limit in the middle of your work. Without failover the chat stops until the limit resets. With failover on, PandaOS moves the chat to the next connection in a list you set, and the work carries on.

It is off until you turn it on, because moving a chat to another connection means another account pays for it.

A limit hit mid-task, failover turned on, and the turn carrying on with the next connection.

Turn it on

Open Settings, pick Models, and under Usage Limit Failover turn on Keep going when usage runs out. Two rows appear underneath: Connections to move to and Switch when usage reaches.

The setting belongs to your profile, not to one project. So failover can be on for everyday work and off in a profile where a chat must never leave the connection you chose.

Settings, Models, Usage Limit Failover. The switch, the ordered chain of connections a blocked chat moves through, and the usage level it fires at.
Settings, Models, Usage Limit Failover. The switch, the ordered chain of connections a blocked chat moves through, and the usage level it fires at.

Set the order

PandaOS tries the list from the top and takes the first connection that is not the one the chat is on and still has usage. Each move lands on an equally strong model, taken from that connection's Tiers.

  1. Under Connections to move to, tick the connections a chat may move to.
  2. Drag them into the order you want them tried.
    A second account of the same subscription is its own row, so two Claude logins are two places to go.
  3. Untick any you want skipped.
    It stays listed, as a reminder that it exists.
  4. Set Switch when usage reaches, from 90% to 100%.
    At less than 100% the chat moves before a turn fails, so you never have to send it again.

What you see when a chat moves

The move happens when you send a message, never in the middle of reading. From then on the chat runs on the new connection and its usage is counted there.

Going back to your preferred account

A chat that was moved goes back to the account it left once that account has usage again. It only moves when you send your next message, never in the middle of a turn. PandaOS looks again after 15 minutes, then 45 minutes, then 2 hours, or at the reset time when the provider gives one. When it goes back you see Back on [account]: that account has usage again.

After three tries it gives up and says This chat is staying on [account]. Your preferred account still has no usage, so switch back from the connection picker when it does. From then on, switching back is up to you.

When every account is out

If every link in the chain is out of usage, the chat stops and waits. You see The accounts in your switch list are out of usage. [account] frees up first, in about N h. Stopped chats continue on their own then.

Waiting chats continue by themselves, one at a time and oldest first, on the account that frees up first: [account] has usage again. Continuing this chat. This only happens while PandaOS is open. Sending a message to a waiting chat yourself takes it out of the wait.

A chat that keeps being refused stops waiting. You see The accounts in your switch list are still out of usage, so this chat will not continue on its own. Send again once one frees up. A chat on the Claude Code engine then also lands in the Inbox as stopped. While it is still waiting, it has no Inbox row.