new-path-codex
v0.2.2
Published
`new-path-codex` signs you in to the New Path GPT proxy, configures the OpenAI Codex CLI, and launches Codex with the proxy token in your local environment.
Readme
new-path-codex
new-path-codex signs you in to the New Path GPT proxy, configures the OpenAI Codex CLI, and launches Codex with the proxy token in your local environment.
The default backend is:
https://vibe-coding-path-new-center.rockiestar-com.workers.devRequirements
- Node.js 18 or newer.
- The OpenAI Codex CLI 0.134.0 or newer, installed and available as
codex. - An email address allowlisted by the New Path proxy admin.
Quick Start
npx new-path-codex auth
npx new-path-codex configure
npx new-path-codexauth sends a one-time code to your allowlisted email and stores a local token. configure creates ~/.codex/new-path-profile.config.toml and adds the provider block to ~/.codex/config.toml. Running new-path-codex launches codex --profile new-path-profile with the token set as NEW_PATH_CODEX_TOKEN.
You can also install it globally:
npm install -g new-path-codex
new-path-codex auth
new-path-codex configure
new-path-codexSign In
npx new-path-codex authThe CLI asks for your email address. If your email is allowlisted, it sends an OTP code. Enter the OTP to store a local user token at:
~/.new-path-codex/token.jsonTo use a non-default backend:
npx new-path-codex auth --backend https://your-worker.example.comConfigure Codex
npx new-path-codex configureThis writes two things:
~/.codex/new-path-profile.config.toml— flat profile file with top-level keys (Codex 0.134.0+ / 2026 profile format). Do not nest these under[profiles.new-path-profile]inconfig.toml.~/.codex/config.toml— adds the[model_providers.new-path-proxy]block and removes any legacy[profiles.new-path-profile]table orprofile = "..."selector if present.
A timestamped backup is created before any edits to existing files.
If you previously used the pre-2026 nested profile format, rerun configure to migrate. Legacy blocks in config.toml can prevent Codex from starting on 0.134.0+.
Make It The Default Codex Provider
npx new-path-codex profile-default onThis sets model_provider = "new-path-proxy" at the top level of ~/.codex/config.toml so running bare codex (without --profile) uses the proxy. Provider credentials and [model_providers.*] blocks always live in config.toml; the profile file layers model and auth overrides when you pass --profile new-path-profile. The previous model_provider value is saved and restored by off.
Restore the previous default:
npx new-path-codex profile-default offRun Codex
npx new-path-codex runLaunch the Codex desktop app with the token in the environment:
npx new-path-codex app
npx new-path-codex app -- /path/to/projectPass normal Codex arguments after --:
npx new-path-codex run -- -m gpt-5.4-mini
npx new-path-codex run -- --cd /path/to/project
npx new-path-codex run -- --ask-for-approval neverRunning without a subcommand also launches Codex:
npx new-path-codex -- -m gpt-5.5Models
Supported models:
gpt-5.5gpt-5.4-mini
Commands
new-path-codex auth [--backend <url>]
new-path-codex configure [--backend <url>]
new-path-codex profile-default <on|off>
new-path-codex app -- [codex app args...]
new-path-codex run -- [codex args...]
new-path-codex --version
new-path-codex --helpLocal Files
~/.new-path-codex/token.json
~/.new-path-codex/state.json
~/.codex/config.toml
~/.codex/new-path-profile.config.tomlThe token file is written with user-only permissions where the platform supports it. Codex config edits are backed up before writing.
Troubleshooting
If auth says your email is not allowed, ask the workspace admin to add your email to the proxy allowlist.
If Codex cannot authenticate, rerun:
npx new-path-codex auth
npx new-path-codex configureIf you want to stop using the New Path proxy as your Codex default:
npx new-path-codex profile-default off