The practical answer is platform and workflow. CodexMarathon is a custom Codex CLI that manages supported accounts on a server or workstation, with a private metadata service, safe turn-boundary transitions, encrypted profile backups, and a documented parked-recovery path. Codex Switcher is presented by its vendor as an independent macOS menu-bar utility for choosing among local Codex account profiles. Choose based on where Codex runs and how much transition automation you need.
The Codex Switcher claims in this comparison are vendor-public claims, not an inspection of its implementation. I reviewed the linked pages on September 15, 2026; product behavior, compatibility, and pricing can change. See the vendor’s Mac account switcher page, usage page, and home page. CodexMarathon’s scope comes from its home page and local product documentation.
The short comparison
| Question | CodexMarathon | Codex Switcher public description |
|---|---|---|
| Where is it positioned? | A custom Codex Rust CLI with a bundled account metadata service | An independent Mac menu-bar utility for Codex accounts |
| How do you choose an account? | Native codex marathon switch or /marathon switch, gated by a safe boundary | Select an account from the Mac menu bar, according to the vendor’s public pages |
| What happens during a running turn? | The documented contract waits until account-bound work is idle | The public pages advise finishing or pausing work; they do not document CodexMarathon’s transition journal for this product |
| What usage data is shown? | Five-hour and weekly observations, reset times, health, and freshness through accountd | The vendor says five-hour and seven-day usage can appear when local Codex tools provide the data |
| Headless-server workflow? | Device-code login is documented for servers | The vendor positions the product as built for macOS; do not infer an undocumented server flow |
| Usage-limit recovery? | Parks, selects, verifies, and resumes one existing continuation | No claim is made here about undocumented automatic recovery behavior |
| Backups? | Encrypted account-profile export/import with conflict policies | The cited public pages describe account selection, not CodexMarathon’s encrypted backup format |
The table keeps the comparison honest. A difference in documentation is not proof that a product lacks an internal capability. It is a reason to follow the public contract for the product you choose.
Pick CodexMarathon for a native CLI and server workflow
CodexMarathon ships the modified codex executable, codexmarathon-accountd, and user service units as one package. The installer enables the service and can persist a custom state directory. On a headless AWS machine, you can sign in without moving a browser session to the server:
codex marathon login work --device-code
codex marathon on
codex marathon statusAccountd stores aliases, IDs, quota observations, reset times, freshness, and transition metadata. It remains credential-free and local over an owner-only Unix socket. This makes it useful when the main Codex workflow is a shell session, a long-running user service, or a server where a Mac menu bar is not the control surface.
The switch contract is equally explicit. Marathon waits for account-bound work to become idle, checks the source identity again, validates and persists the target, asks native Codex to reload authentication, and verifies the target before committing. A rejected or uncertain transition remains visible for reconciliation. Read how to switch Codex accounts without losing your conversation for the full sequence.
Pick a Mac menu-bar workflow when that is the requirement
Codex Switcher’s public Mac account-switcher page describes adding accounts once, naming them by role, and selecting the active profile from the menu bar. The same page says the product is built for macOS 14 or later and identifies it as independent software with no OpenAI affiliation. Those are vendor statements reviewed on September 15, 2026.
The vendor’s usage guide says the menu can show five-hour and seven-day usage, reset timing, and available resets when local Codex tools provide the data. It also says unknown usage means the current value could not be read, not that the profile cannot switch. That is a useful warning: visibility is a planning signal, while OpenAI controls account access, plan limits, and service behavior.
The public workflow is a good fit if you want a visible account label before opening a local task on a Mac. Keep the account context explicit, finish or pause work before changing it, and follow any organization policy attached to a work or client profile. The vendor pages do not provide the same transition or recovery contract as CodexMarathon, so this article does not claim one exists.
Compare quota interpretation carefully
Both products describe account-specific usage rather than a magic way to create capacity. CodexMarathon’s CLI reports the observations stored by accountd:
codex marathon accounts --daemon --format tableRead both windows and freshness. A reset timestamp that has passed is stale until a fresh native observation arrives. The Codex usage limits guide explains why a displayed value is not a universal plan allocation.
The Codex Switcher vendor’s public usage page similarly tells readers to match the account label, usage window, and reset time, and to check the authoritative OpenAI status when needed. This is an attributed summary of that page, not a claim that both products collect data in the same way.
Do not select an account to evade a provider or organization rule. Use only profiles you are authorized to use, and treat separate account capacity as separate. Neither public product description supports transferring usage between accounts.
Compare recovery and automation boundaries
CodexMarathon documents a specific automatic path after UsageLimitExceeded: Codex parks its existing recovery turn; Marathon selects a fresh eligible managed account; the switch waits for a safe boundary; native Codex verifies the target identity; and Codex releases the parked continuation exactly once. If no eligible account exists, it waits. See automatic switching when quota runs out.
That guarantee is part of CodexMarathon’s native contract. Codex Switcher’s public pages explain account selection and usage visibility, but this comparison makes no claim about automatic parked-turn recovery because the cited vendor pages do not state one. If exactly-once recovery on a server is the deciding requirement, evaluate the documented contract rather than a similar product name.
Compare backup and ownership needs
CodexMarathon can export selected saved profiles to an authenticated encrypted .cmbackup archive, then import them with dry-run and conflict policies. Imports stay inactive and never replace the destination’s active auth.json. The passphrase is collected through a masked local workflow or a tightly permissioned file; it is not accepted in process arguments or environment variables. See using multiple Codex accounts safely for account workflow context and the CodexMarathon repository for implementation documentation.
The cited Codex Switcher pages focus on local Mac account selection and do not document this archive format. That is not a negative assertion about the vendor’s software; it simply means backup requirements should be confirmed directly before purchase or migration. In either workflow, never copy credentials into chat, shell history, or an unprotected file.
Make the decision by contract
Choose CodexMarathon when you need a native shell/server workflow, device-code login, accountd metadata, safe turn-boundary transitions, documented exactly-once recovery, or encrypted profile transfer. Choose the Mac menu-bar workflow described by Codex Switcher’s public pages when a local visual selector and account usage glance are your priority.
Whichever tool you use, keep accounts separate, verify the active identity before sensitive work, and respect provider and organization limits. The right comparison is not which product promises “more quota.” It is which documented control surface matches your platform and your safety requirements.