> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gatetrix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Codex subscriptions and accounts

> Use an existing ChatGPT subscription in MTS, add multiple accounts, and control manual or automatic switching.

<Info>
  **Use your existing subscription.** MTS's built-in Codex integration uses
  **Sign in with ChatGPT** and your account's Codex access. It does not currently
  support API-key billing or other providers' subscriptions. You can add multiple
  eligible ChatGPT accounts. Their own limits and workspace policies still apply.
</Info>

Codex itself supports more than one authentication method; MTS currently exposes
ChatGPT sign-in for its embedded teammates. See OpenAI's
[Codex authentication documentation](https://developers.openai.com/codex/auth/)
for the distinction between subscription and API access.

For another provider or billing option, contact
[hello@gatetrix.ai](mailto:hello@gatetrix.ai?subject=MTS%20provider%20support).
You can also [connect an external agent](/mts/connections#connect-an-external-agent-to-mts)
using its own runtime and provider.

## Add an account

1. Open a teammate's conversation menu and choose **Codex accounts…**.
2. Enter a recognizable account name and choose **Add and sign in**. Complete
   **Sign in with ChatGPT** in the browser, using the intended account.
3. Repeat for another eligible subscription if you want to use more than one.
4. Check the account list. **Using now** marks the account selected for the
   current conversation; **Default** marks the first account eligible for
   automatic selection.

Accounts are shared across projects and teammates in this MTS workspace. Each
has a separate sign-in. Usage is shown when Codex reports it; unknown usage
does not mean the account has no allowance left.

## Choose priorities

In the account dialog, **Global** settings apply to agents using **Use global
settings**. Select **This agent** and turn that setting off to customize the
agent's account order and switching preference across its conversations.

Use the up/down arrows to set priority. **Use automatically** makes an account
eligible for defaults and fallback. Turn it off to keep the account **Manual
only**. New conversations skip accounts known to be unavailable; changing the
order does not move an existing conversation to another account.

## Switch a conversation manually

Stop active work and resolve pending integration requests first. Choose
**Use for this conversation** on the account you want.

MTS preserves the conversation's visible history, saved Codex context, project
permissions, and working folder. Switching alone does not send a new prompt.
The destination account needs access to the selected model and thinking effort,
and the installed Codex runtime must support transferring the saved context.
If it cannot, MTS reports the failure rather than silently starting without it.

Switching permits that conversation's history to be used with the destination
account and its associated workspace. Consider the accounts' different workspace
policies before sharing a conversation between them.

## When a subscription reaches its limit

**Automatically switch on usage limits** and account eligibility are on by
default. MTS tries eligible accounts in priority order when Codex reports a
supported usage-limit failure before the turn has performed work.

If the turn has already taken actions, or questions or integration requests need
attention, MTS pauses for review instead of replaying the instruction. Maintenance
sessions also require explicit recovery. Generic errors and transient rate limits
do not trigger automatic switching.

If no eligible account is available, the conversation pauses visibly. You can
review the account list, wait for a reset, or switch manually and continue after
checking the work's state. MTS does not proactively switch back when a quota resets.

Turn off **Automatically switch on usage limits** if you want to decide each
switch yourself. An account still used by a conversation cannot be removed;
sign-out is blocked while affected conversations are busy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.