The terminal runs on the account with room.

Altseat works only with accounts you added and are authorised to use. It never shares a login, never handles a token for anyone else and never changes the login of a running process: a handoff ends Claude Code at a turn boundary before the next account starts. It adds no capacity: each account keeps its own limits.

Each account gets its own directory through the setting its vendor documents: CLAUDE_CONFIG_DIR, which Anthropic documents for running separate accounts, CODEX_HOME for Codex and KIMI_CODE_HOME for Kimi Code.

Whether several subscriptions suit your situation is between you and each provider: see Anthropic's consumer terms, OpenAI's terms of use and the Kimi Code membership guide.

For switching, yes: an alias per account with CLAUDE_CONFIG_DIR works, and Anthropic documents it. Altseat adds what an alias leaves to you: the usage of every Claude Code and Codex account in the menu bar, a launch that skips an account at its limit and says which one it started, a Claude Code handoff near the limit that continues the conversation on the next account, settings and sessions shared across accounts, and the same switching for Codex and Kimi Code.

The free version covers 2 accounts, so you can set it against your aliases before you pay.

Each tool signs in with its own login and keeps its own credentials. Altseat never sees a password and never writes, refreshes or copies a token.

By default it reads Claude usage from the status line Claude Code already runs, so it does not read the Keychain. Only the usage endpoint option, off by default, reads Claude's Keychain item, to ask Anthropic for that account's usage. Codex usage comes from the Codex CLI's own local app-server.

Altseat itself sends nothing anywhere except that optional request to Anthropic, the license check (the key, a one-way hash of the Mac's id, the Mac's name and the app version) and the update check.

In Claude Code, the session moves near the limit. When the active account reaches 95 % of its five-hour or weekly window and another Claude Code account you added has room, the agent finishes the step it is on and writes a short handoff file, the session ends, and Altseat starts claude on the next account with room in the same terminal: the same conversation resumes there, the agent reads the handoff and carries on. One line in the terminal and, with the app open, a macOS notification say which account it moved to.

The handoff runs between two Claude Code processes: the first has exited before the next one starts, and Altseat never changes the login of a running process or uses an account you did not add. Each account keeps its own limits. One switch in the Accounts window turns the handoff off, as does altseat handoff off; then a session stops at the limit as it would without Altseat, the next claude starts the next account with room, and claude -c continues the conversation there.

Codex CLI and Kimi Code pick at launch only. When the active Codex account is at its limit, codex starts the next one in your order with room and prints which one, so codex resume --last continues the chat; an automatic handoff for Codex is planned. Kimi Code has no usage reading yet, so kimi starts on the active Kimi Code account; make another one active in the menu bar and kimi -c continues there.

Claude Code: switching, usage and the automatic handoff. Codex CLI: switching and usage; its automatic handoff is planned. Kimi Code: switching and sign-in state, with no usage reading yet. Gemini CLI is not supported.

Not for switching: the claude, codex and kimi commands pick from the usage Altseat last recorded, with or without the app. Claude Code's status line keeps recording Claude usage while it runs, and the Claude Code handoff runs through Claude Code's hooks and the altseat command, with or without the app; the app adds the macOS notification.

The app shows the usage in the menu bar and refreshes Codex usage every 15 minutes, so keep it open for the freshest pick.

No. Altseat 1.x needs a Mac with Apple Silicon and macOS 14 or later.

No. The claude, codex and kimi shell functions are installed in zsh, the default shell on macOS. In bash or fish the commands run without Altseat's pick.

Everything, for 2 accounts in total across Claude Code, Codex CLI and Kimi Code, with no key and no sign-up. A license raises that to 10 accounts per tool on one Mac.

Every 1.x update is included, for free and licensed users alike, and the app offers each one from the menu.

If a 2.0 ever needs a new key, 1.x keys keep working with 1.x and get a reduced price.

The free version works on any Mac. A license key is active on one Mac at a time: for two Macs, set the quantity to 2 at checkout, and every key arrives in the same email.

To move a key, deactivate it in the old Mac's Accounts window, then paste it into the new one. If the old Mac is lost or no longer starts, release the key from your account page, once every 24 hours per key.

In the email that arrives as soon as you buy, and in your account. Sign in with the email you paid with and every key you bought is listed there.

Yes, within 14 days of your purchase, no questions asked. Use the link in your Paddle receipt or write to support@altseat.com. Paddle, our merchant of record, issues the refund and the key is revoked.