Accounts and limits

More than one login per agent

Add a second account for an agent in Settings, Agents, under Agent logins (see Connect your agents). Each login keeps its own folder, sign-in and history. New chats use the login marked with the dot. A chat can also pin a login from the model menu's Account list.

Every account is yours, on its own plan and its own provider's terms. Check those terms for how your provider expects accounts to be used. Usage is billed by your provider, not by Offrun.

See what each login has left

The Usage card on Home has a block for each login, with its plan and each usage window: the window's length, a bar, the share used, and when it resets. A bar changes color at 75% used, and again at 95%. The figures refresh at most once a minute, and right after a turn ends.

• Claude Code shows its 5-hour session and its week, read with its own /usage command, which calls no model.
• Codex shows its windows from its own session logs, once it has run a turn.
• AGY shows its windows split by model group, Gemini and other models, with a note on which models share each limit.
• Grok Build shows its limits only in its own app, and Muse Code does not report them.

When a login hits its limit

Offrun reads the agent's error, replaces it with This login has hit its usage limit. and, if the same agent has another login, moves the chat to it:

Work hit its limit, so this chat moved to Personal. Send your message again to carry on: the new login starts its own thread and is handed this conversation along with the message.

What Offrun does by itself. It sets the spent login aside for an hour, picks the next login in the order Settings lists them (skipping any that hit a limit in the past hour), moves the chat to it, and posts the line above. That login also becomes the one new chats use. It does not send anything to the new login yet.

What you do. Send your message again. ↑ in the message box brings back what you sent.

What the new login gets. When you send, the new login starts a thread of its own, and Offrun hands it the conversation so far together with your message, so it knows what was going on.

The same happens when a provider answers that it is too busy, if there is another login to try.

When every login is out

With no other login left for that agent, a card appears in the chat instead:

• Keep going with another agent, when the agent is out of usage and another agent you are signed in to can take over. It says when the first one resets. Press Continue with and the other agent's name: the chat switches to that agent, which gets the whole conversation, and your last message is sent again.
• Claude Code is busy right now (or the name of whichever agent it is), when the provider is overloaded. Try again sends your last message again on the same agent.
• Claude Code is out of usage, when there is no other agent to offer. Open agent settings takes you to Settings, Agents to add a login.

Offrun never switches a chat to another agent until you press the button.

When a login is signed out

If an agent's sign-in expires mid-chat, the chat shows Claude Code is signed out. with a Sign in button that opens Settings, Agents. Sign that login in again, then send your message again.

More on this

The multiple Claude Code accounts guide shows how the same thing works by hand with CLAUDE_CONFIG_DIR and CODEX_HOME, and what Offrun adds.