@ezerlab/codex-ezer
v0.1.3
Published
Dual-route Codex launcher that keeps ChatGPT auth as the default and adds an isolated Ezer API profile.
Readme
@ezerlab/codex-ezer
This package adds an explicit Ezer route to an existing Codex installation without changing the normal ChatGPT-account route.
codex -> built-in OpenAI provider -> existing ChatGPT login
codex-ezer -> profile ezer -> https://api.ezerlab.org/v1/responsesCodex custom providers currently speak the Responses wire protocol. Ezer's gateway owns any conversion from that protocol to its upstream providers and request formats.
Install
Install from the public npm registry after release:
npm install --global @ezerlab/codex-ezer
codex-ezer installThe employee workstation must already have the official codex executable on
PATH. The wrapper launches that binary and does not bundle or replace Codex.
The installer creates $CODEX_HOME/ezer.config.toml with mode 0600. It does
not edit $CODEX_HOME/config.toml, log out ChatGPT, or persist a plaintext key.
The verified default model is gpt-5.5; choose another gateway model with
codex-ezer install --model MODEL. By default the profile reads
EZER_API_GATEWAY_KEY from the launch environment:
export EZER_API_GATEWAY_KEY="<employee Ezer client key>"
codex-ezer doctor
codex-ezerOn macOS or Linux, a protected server-side or local key file can be referenced without copying its contents into the profile:
chmod 600 /approved/path/ezer.key
codex-ezer install --key-file /approved/path/ezer.keyUse codex whenever the ChatGPT-account route is desired. Use codex-ezer
when the Ezer API route is desired. There is no silent cross-provider fallback
inside one Codex session; upstream fallback belongs in the Ezer gateway.
Codex 0.157.1 was tested on 2026-09-27 with real codex and codex-ezer
requests. Confirm provider: openai for the normal command and
provider: ezer for the Ezer command, as well as the semantic response. The
gateway's OpenAI-compatible model list may still differ from a Codex catalog
response; the explicit gpt-5.5 Responses request is the route check.
Package checks
npm test
npm run pack:checkPublishing is a separate release action. The package contains no credential, employee token, or copied authentication payload.
