Documentation Index
June 17, 2026 · View on GitHub
docs/ is the official long-form documentation directory for CodexManager.
Its purpose is simple:
- Keep governance notes, release guides, and operating manuals inside the repository.
- Make it easy for new contributors to find the right document without relying on tribal knowledge.
Project Snapshot
CodexManager is a local desktop + service-process account pool manager and gateway relay for Codex workflows.
- Unified account, usage, and platform-key management.
- Local OpenAI-compatible gateway for Codex CLI, Gemini CLI, Claude Code, and third-party tools.
- Supports account routing, model/profile overrides, and aggregate API upstream relays.
Feature Overview
- Account pool management: groups, tags, ordering, notes, ban recognition, and filtering.
- Batch import/export: multi-file import, desktop recursive folder import, per-account export.
- Usage display: 5-hour + 7-day windows, single-window accounts, and official extra buckets such as Code Review / Spark.
- Platform keys: create, disable, delete, model binding, reasoning tier, and service tier.
- Aggregate API: create/edit/test third-party relay upstreams with supplier naming and priority ordering.
- Plugin center: built-in, private, and custom source modes with task/log views and Rhai integration.
- Local service + gateway: custom bind/listen settings, upstream proxy, total request timeout, stream idle timeout, SSE keepalive, and a unified compatible endpoint.
- Image generation: automatically injects the official Codex
image_generationtool for/v1/responsesby default, forwards explicit tools unchanged, and exposes compatible/v1/images/generationsand/v1/images/editsendpoints withgpt-image-2as the default image tool model.
Quick Start
- Launch desktop app and click Start Service.
- Open Account Management and complete account authorization.
- If callback parsing fails, paste the callback URL for manual parsing.
- Refresh usage and verify account status.
Screenshots

Scope
- Root
README.mdand localizeddocs/*/README.md: project overview and quick start. - Root
CHANGELOG.md: version history and unreleased changes. report/*: operations, troubleshooting, compatibility notes, and FAQs.release/*: build, packaging, release, and artifact documentation.
Start here
- For the latest release notes, see CHANGELOG.md.
- If you are not sure which document to open first, use the table below.
Sponsors
Thanks to the following sponsors for supporting CodexManager.
|
Thanks to AI夏末 AIXiamo for sponsoring this project! AIXiamo serves developer workflows such as Codex CLI, Claude Code, and Gemini CLI, providing AI membership activation and after-sales assistance for ChatGPT Pro 5x / 20x, ChatGPT Plus, Claude Max, Gemini Pro, Grok, and more. It supports Alipay and WeChat Pay, automatic top-ups, order lookup, tutorials, and after-sales support. It is suitable for developers who need stable access for AI programming, code generation, document processing, and frequent conversations. CodexManager users can get priority consultation for Pro / Codex / Claude / Gemini plan selection. Visit the official site to view services. |
|
Thanks to APIKEY.FUN for sponsoring this project! APIKEY.FUN is a professional enterprise-grade AI API gateway dedicated to providing stable, efficient, and low-cost AI model API access for businesses and individual developers. The platform supports popular mainstream models including Claude, OpenAI, and Gemini, with pricing as low as 7% of the official price. Register through this project's exclusive link to receive an exclusive benefit of up to permanent 5% off top-ups. |
|
Xing Si Yan Gateway provides stable relay and supporting services for Claude Code, Codex, and similar model-call scenarios. It is suitable for developers and teams that require highly available APIs, convenient onboarding, and continuous delivery support. Visit the official site for the latest plans. |
Other supporters: Wonderdch, suxinwl, Hermit, Suifeng023, HK-hub
Ecosystem Pairing
OpenCowork
- Repository: AIDotNet/OpenCowork
- Recommended pairing: use OpenCowork for local file operations, multi-agent execution, workplace messaging, and desktop automation, while CodexManager handles Codex account management, usage tracking, platform keys, and the local gateway entry point.
- Best for: teams that want to separate the execution workspace and office integration from account-pool management and gateway access.
- A simple way to think about it: OpenCowork executes in the real workspace, CodexManager manages accounts and gateway access.
Quick navigation
| What you need | Open this document |
|---|---|
| First launch, deployment, Docker, macOS allowlisting | Runtime and Deployment Guide |
Configure Codex CLI / ccswitch auth.json and config.toml | Runtime and Deployment Guide |
| Environment variables, database, ports, proxy, listen address | Environment and Runtime Configuration |
| Account routing, import errors, challenge interception | FAQ and Account Routing Rules |
| Why background jobs skip or disable accounts | Background Task Account Skip Notes |
| Minimum plugin marketplace integration | Plugin Center Minimal Integration |
| Internal commands and integration surfaces | System Internal Interface Inventory |
| Local build, packaging, and release scripts | Build, Release, and Script Guide |
Directory guide
release/
Release notes, rollback notes, artifact descriptions, and packaging guides.
report/
Operational guides, troubleshooting notes, compatibility reports, and FAQs.
Recommended reading
Operations
| Document | Summary |
|---|---|
| Runtime and Deployment Guide | Desktop first launch, Service edition, Docker, and macOS first-run handling |
| Environment and Runtime Configuration | Runtime configuration, defaults, and environment variables |
| FAQ and Account Routing Rules | Common account-routing issues and troubleshooting tips |
| Gateway vs Official Codex Params | Current outbound parameter differences compared with official Codex |
| Background Task Account Skip Notes | Why background jobs skip, cool down, or disable accounts |
| Minimal Troubleshooting Guide | Fast checks for the most common startup and relay issues |
| Plugin Center Minimal Integration | Minimum fields and interfaces required for plugin marketplace access |
| Gateway vs Codex Headers and Params | Header and request parameter differences between the gateway and Codex |
| Plugin Center Integration and Interfaces | Marketplace modes, RPC/Tauri commands, manifest fields, and Rhai interfaces |
| System Internal Interface Inventory | Internal commands, RPC endpoints, and built-in plugin functions |
Build and release
| Document | Summary |
|---|---|
| Build, Release, and Script Guide | Local builds, script parameters, and GitHub workflow entry points |
| Release and Artifacts | Release artifacts, naming, and publication rules |
| Script and Release Responsibility Matrix | Which script or workflow is responsible for which task |
Contribution rules
Commit documentation when it
- remains useful for future contributors,
- affects development, testing, release, or troubleshooting,
- or serves as a long-term source of truth.
Do not commit documentation when it is
- a temporary draft,
- personal working notes,
- a disposable intermediate file,
- or a local-only experiment record.
Ignored patterns
docs/**/*.tmp.mddocs/**/*.local.md
Do not use those suffixes for formal documentation.
Naming
Long-lived documents: topic.md
One-off reports: yyyyMMddHHmmssfff_topic.md
Maintenance notes
- Add important governance material under
docs/instead of expanding the README indefinitely. - Keep version history in
CHANGELOG.md. - Keep architecture notes in
ARCHITECTURE.md. - Keep collaboration rules in
CONTRIBUTING.md. - Put unreleased change details in
CHANGELOG.md; keep the README focused on navigation and summary.
Contact
- WeChat: add
ProsperGaoto join the group, and please mention your purpose - Telegram group: CodexManager TG group