CLIProxyAPI Codex Setup
This skill is for maintaining a specific personal setup:
CLIProxyAPIruns on a Mac- local Codex uses the Mac loopback endpoint
- Ubuntu Codex uses the Mac LAN endpoint
- ChatGPT Plus accounts are stored as local auth files
- Ubuntu avoids storing the proxy key in
~/.codex/auth.json
Quick workflow
- Read the live setup notes in references/setup-notes.md.
- Check the current files under
/Users/aodu/workspace/cliproxyapi-local. - When routing behavior matters, verify
routing.strategyinconfig.yaml. - When Codex behavior matters, separate:
CLIProxyAPIconfig inconfig.yaml- Codex transport config in
~/.codex/config.toml - runtime key injection versus
auth.json - config-parse problems versus runtime
/v1/responsescompatibility problems
- For Ubuntu, prefer the launcher script flow over writing the proxy key into shared config files.
What this skill should help with
- explain how local Mac and Ubuntu clients should connect
- verify whether one or more ChatGPT Plus accounts are loaded
- switch between
round-robinandfill-first - preserve cache-friendlier routing with
fill-first - manage the
proxy-urlsetting for local VPN or Clash-style proxies - create or update launcher scripts that export
OPENAI_API_KEY - correct common Codex config mistakes such as missing
nameor wrongwire_api - document or restore the current setup after edits
References
- Read references/setup-notes.md for the concrete paths, commands, and current tested behavior.