Windows automatic
The BAT file backs up config.toml and auth.json, asks for your key, and writes the settings into your local .codex folder.
Download BATCodex CLI / IDE setup guide
Run Codex with your unlimitedcodex key
This page helps you run Codex CLI, Codex IDE, or the Codex app with your unlimitedcodex API key and base URL. If you are new, choose one path, enter the key, restart Codex, then run one tiny test.
Step 1
You do not have to run a script. Use Windows auto setup, macOS/Linux command setup, or manual setup. You can also give the TXT instructions to a trusted local AI assistant.
The BAT file backs up config.toml and auth.json, asks for your key, and writes the settings into your local .codex folder.
Download BATRun the command file in Terminal. iPhone and iPad cannot perform this local Codex setup.
Download COMMANDDownload the TXT file and give it to a trusted local/private AI assistant. The assistant should only edit local config files.
Download TXTChecklist
Most setup problems come from the wrong folder, a /v1 suffix in base_url, or forgetting to restart Codex.
Your key arrives in the delivery email. Put it only in auth.json or where the setup file asks for it.
If config.toml or auth.json is missing, sign in to ChatGPT inside Codex, close and reopen Codex, then check again.
In config.toml, base_url should be only https://claude.kadirr.dev. Do not put /v1 there.
After editing config.toml and auth.json, fully close and reopen Codex CLI, Codex IDE, or the Codex app.
New model selection
The active model for new setup is gpt-5.5. Keep the model line on gpt-5.5 while 5.6 Sol and its variants stabilize.
5.6 Sol and its variants are temporarily restricted because of upstream instability and slowness. Use gpt-5.5 for all new setups until support says otherwise.
xhigh is the safe default for coding and agent work. Choose high, medium, or low for faster and simpler jobs.
Manual setup
config.toml tells Codex which API provider to use. auth.json stores your unlimitedcodex API key locally.
Windows folder: %USERPROFILE%\.codexmacOS / Linux folder: ~/.codexWith newer Codex versions, config.toml or auth.json may appear only after you sign in to ChatGPT inside Codex and open Codex once.
model_provider = "OpenAI" model = "gpt-5.5" review_model = "gpt-5.5" model_reasoning_effort = "xhigh" disable_response_storage = true network_access = "enabled" [model_providers.OpenAI] name = "OpenAI" base_url = "https://claude.kadirr.dev" wire_api = "responses" requires_openai_auth = true [features] goals = true
{
"OPENAI_API_KEY": "YOUR_UNLIMITEDCODEX_API_KEY"
}After restarting Codex, run one short test before a large repository task. If it fails, check the key, package status, and base URL.
curl -X POST https://claude.kadirr.dev/v1/responses \
-H "Authorization: Bearer YOUR_UNLIMITEDCODEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.5",
"input": [
{
"role": "user",
"content": [
{
"type": "input_text",
"text": "Hello from unlimitedcodex"
}
]
}
],
"stream": false
}'Debug
Check this table before asking on Telegram. Do not send your full API key to support.
The key may be wrong, inactive, truncated, or written into the wrong file.
Check only the OPENAI_API_KEY field in auth.json. Do not paste the full key into public places.
This usually happens when /v1 is added to base_url inside config.toml.
Keep base_url as https://claude.kadirr.dev. Use /v1/responses only in direct API tests.
Codex may still be running with the old process.
Fully close and reopen Codex CLI, Codex IDE, or the Codex app.
Codex may not have created local files yet.
Sign in to ChatGPT inside Codex, open Codex once, then check the .codex folder again.
Message us on Telegram. Do not send the full key. Send your OS, error text, which file you edited, and only a safe key prefix.