Switch accounts when quota runs out
Marathon can move to another account with quota left. Your conversation stays open. If no account is ready, it waits.
See how it switches →Free Codex CLI account switcher
When one account runs out of quota, CodexMarathon can switch to another account you manage. Your conversation stays open.
curl -fsSL https://raw.githubusercontent.com/Lem0nTree/codexmarathon/main/scripts/install.sh | shFree download · Linux ARM64 · source available on GitHub
live quotaActive account uses quota. Idle accounts recharge.
Automatic quota recovery
Turn Marathon on once. When Codex reports a usage limit, the native recovery flow can choose another managed account with fresh usable quota—without asking you to copy a prompt or restart the conversation.
Codex reports the usage-limit event and parks its existing recovery turn.
Marathon chooses a healthy managed account with a fresh, usable quota observation.
The switch waits for idle work, reloads native authentication, and verifies the intended identity.
Codex releases the parked continuation exactly once in the same conversation.
Included with CodexMarathon
Marathon can move to another account with quota left. Your conversation stays open. If no account is ready, it waits.
See how it switches →Check the five-hour and weekly quota for every account. You can also see when it resets and how recent the number is.
Learn about quota →Save some or all of your accounts in one password-protected file. Check what is inside before you restore it.
Marathon waits for the current work to finish and checks the new account before it switches.
See how it protects your work →Running Codex on a Linux server? Open the sign-in code on your phone or laptop to add an account.
Open the server guide →Your current conversation continues after the switch. Marathon does not copy your message or send it twice.
On supported Armbian servers, your account quota appears on the welcome screen as soon as you sign in.
CodexMarathon is free. Your ChatGPT plan and usage limits stay the same.
Quota you can interpret
A reset time is only part of the answer. CodexMarathon keeps the five-hour and weekly observations beside their freshness and account identity, so stale data cannot silently authorize an automatic switch.
Read the complete usage-limit guide →Three-step setup
One installer adds the custom Codex CLI and its private account metadata service. Automatic management stays off until you enable it.
See every command on GitHub ↗curl -fsSL https://raw.githubusercontent.com/Lem0nTree/codexmarathon/main/scripts/install.sh | sh
codex marathon statuscodex marathon login personal --device-code
codex marathon login work --device-codecodex marathon on
codex marathon accounts --daemonPractical guides
Questions
CodexMarathon parks the existing recovery turn, selects another eligible managed account with fresh usable quota, waits for account-bound work to become idle, verifies the new identity, and then releases the same continuation once. If no account is eligible, it waits.
No. A switch is accepted only at a safe turn boundary. CodexMarathon does not replace credentials during a model response, tool call, or subagent turn.
No. It manages supported ChatGPT accounts you control and reports provider observations. It does not refill, reset, or bypass provider limits.
Yes. The CodexMarathon download and the features marked Free on this page do not require a CodexMarathon subscription. Your ChatGPT account access and provider usage remain separate.
Yes. The account view shows the active identity, credential health, observed five-hour and weekly quota, reset times, and freshness for managed accounts.
Yes. The Linux ARM64 release supports device-code login, so you can open the verification URL and complete sign-in on another device.
Yes. Choose individual accounts or all accounts and export a password-protected backup. Restoring does not silently replace the active identity.
Free · Linux ARM64 · source on GitHub