openai / openai/codex

docs: PZERO custom model_providers example

Open Beginner friendly
#41,266 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CLI config custom-model documentation
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What is the type of issue?
  • Documentation is missing
What is the issue?

Codex already supports custom model_providers in ~/.codex/config.toml. People looking for prepaid, privacy-first inference still have to guess base_url, wire_api, and whether the key goes in experimental_bearer_token or a ChatGPT login.

A named PZERO example on the custom-provider docs (or docs/example-config.md) would let users copy this and launch. No bundled Codex plugin required.

Append to ~/.codex/config.toml. Do not pin model or model_provider in the file. Pick those at launch.

[model_providers.pzero]
name = "PZERO"
base_url = "https://api.pzero.studio/v1"
experimental_bearer_token = "pzero_YOUR_KEY"
wire_api = "responses"
requires_openai_auth = false
codex -c model_provider="pzero" -c model="deepseek-v4-flash"

Get a key: https://pzero.studio/agents (sign-in free; min top-up 1 USDC on Base; no starter credits). Live text ids: GET https://api.pzero.studio/v1/models (public). A pzero/ model prefix is optional.

PZERO POST /v1/responses exists (401 without a key). That is why wire_api = "responses". Chat completions also exist at POST /v1/chat/completions if a later Codex path needs them.

I am not asking for a first-party provider next to OpenAI. Custom model_providers is the existing seam.

Every AI Credit is at least 20% off $1 list. Usage is paid. Do not start implementation on my behalf until the board says Ready; the config is for users today.

Where did you find it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/config.md and the custom model_providers section linked in the issue; compare whether docs/example-config.md is the better location. Add the PZERO TOML example and launch command without pinning model or model_provider, then verify the documentation clearly explains the provider settings and key setup.

Written by the indexing model from the issue text.

Assessment

Domain
cli, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.