Why one login runs out
Claude plans limit Claude Code twice: over a session window that resets every few hours, and over a week. Run two or three agents at once and a session can run out halfway through a task. Claude Code then stops with a line like this:
You've hit your limit · resets 3amIf you have a second account, say a work seat and a personal plan, you'll want to carry on with the other one. Claude Code won't switch by itself, and by default it only knows one login per Mac.
Doing it by hand with CLAUDE_CONFIG_DIR
Claude Code stores its sign-in, settings and session history in one config folder. Set CLAUDE_CONFIG_DIR and it uses that folder instead, with a login of its own. Sign the second account in once:
# start Claude Code on a new, empty config folder
CLAUDE_CONFIG_DIR=~/.claude-work claude
# then, inside Claude Code, sign in as the work account
/loginFrom then on, start it with the variable for the work account and without it for your default one. An alias saves the typing:
alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-work claude'Codex works the same way with CODEX_HOME, except that the folder has to exist first:
mkdir -p ~/.codex-work
CODEX_HOME=~/.codex-work codex loginTwo things the variable does not do for you:
- Each folder keeps its own history, so you can't resume a conversation from one account on the other. You start a new one and explain the task again.
- There's no warning when an account is close to its limit. You only find out when Claude Code stops.
How Offrun runs several accounts
Offrun uses the same folders and keeps track of them for you. In Settings, then Agents, press Add account under Claude Code, Codex or Agy and sign in through that agent's own login. Each login gets its own folder, and Offrun starts the CLI pointed at it. It never reads, copies or stores your tokens.
Click a login to make it the one new agents use. A chat stays on the login it started with, so a work repository can run on the work seat while a side project runs on your personal plan.
Agy, Google's Antigravity CLI, has no variable of its own, so each Agy login gets its own home folder. Your git identity and SSH keys are linked into it, so its commits and pushes still work.
See what every login has left
Home lists every login with its usage and the time each window resets: the session and the week for Claude Code, the plan's window for Codex, and Agy's model buckets. Offrun asks each CLI for these figures on that login's own folder. For Claude Code that is its /usage command, which answers without calling a model.
What happens when a login hits its limit
- The chat moves to your next login for the same agent and tells you in the chat, for example: Work hit its limit, so this chat moved to Personal.
- You send your message again. The new login starts its own thread and is handed the conversation along with your message, so it knows what was going on.
- The spent login is passed over for an hour, so the next turn does not land straight back on it.
- If every login for that agent is spent, the chat offers another agent you are signed in to, such as Codex or Antigravity. One press switches the chat and sends your message again, with the whole conversation.
Each switch shows up as a line in the chat naming both logins, so you always know which account a reply came from.
Questions
Can I use more than one account?
Each account is yours, on its own plan and its own terms. Offrun only starts the CLI on the login you picked. Check your provider's terms for how they expect accounts to be used.
Does Offrun see my password or tokens?
No. The agent signs in through its own login and keeps its credentials in its own folder. Offrun hands the CLI the folder's location and nothing else.
Does this work for Codex and Antigravity too?
Yes. Codex, Claude Code and Agy can each have several logins, and the same limit handling applies to all three.
What does it cost?
You keep paying for your own Claude, ChatGPT or Google plans, as you do now. For what Offrun itself costs, see pricing.