Skip to main content
supakook.DOCS

Sign-in is not available yet.

The account center is not connected yet. For existing orders, use your original purchase channel to find account and delivery details.

Read the user guide

Codex desktop setup

Use a graphical workspace for projects and code changes. The current official Codex App guide points to the ChatGPT desktop app, which includes Codex.

Prepare your connection​

Get an API key, Base URL, and supported model ID from the Supakook API console. The key needs access to the chosen model, and the endpoint must support Responses. A web subscription is not API credit.

1. Install the desktop app​

Use the official Windows download, or run this command in PowerShell.

PowerShell
winget install --id 9PLM9XGG6VKS -s msstore
Official Windows installation guide ↗

The current official desktop app is named ChatGPT. Choose Codex inside the app after installation.

2. Configure Supakook​

Fully quit the app before editing its configuration. This provider uses API Key authentication. ChatGPT subscription sign-in does not replace your Supakook key. CLI and desktop can share user configuration: keep a backup and choose one authentication setup rather than combining both examples.

Back up your configuration, then merge these fields. Keep existing MCP, project, and permission settings; do not duplicate keys.

User configuration file: %USERPROFILE%\.codex\config.toml

Open the configuration file
New-Item -ItemType Directory -Force "$env:USERPROFILE\.codex" | Out-Null
notepad "$env:USERPROFILE\.codex\config.toml"

This is a configuration template. Replace MODEL_ID_FROM_CONSOLE with an available model ID and the entire example URL with your delivered Base URL. Do not append duplicate /v1 or /responses paths.

config.toml
model_provider = "supakook"
model = "MODEL_ID_FROM_CONSOLE"

[model_providers.supakook]
name = "Supakook"
base_url = "https://api.example.com/v1"
wire_api = "responses"
requires_openai_auth = true

Save, fully quit, and reopen the desktop app. Choose API Key sign-in and enter your Supakook key. This uses requires_openai_auth; do not also apply the CLI env_key configuration.

If you set CODEX_HOME, use that configuration directory. WSL has a separate Linux home directory from native Windows.

3. Verify the connection​

Check the active provider and model, then try a small task in your project:

Read the README and summarize this project. Do not modify files yet.

After receiving a reply, check the matching usage record in the console. This confirms which service handled the request; a reply alone does not prove that the intended provider was used.

Troubleshooting​

  • Command not found: Reopen your terminal and check PATH. With npm on Windows, try codex.cmd.
  • Missing environment variable: Set SUPAKOOK_API_KEY in the same terminal that starts the CLI.
  • 401 / 403: Check key validity and model permissions.
  • 404 / Responses unsupported: Verify Base URL, protocol, and model ID.
  • Old configuration remains: Check project overrides, launch arguments, CODEX_HOME, and the actual local or remote environment. Restart the desktop app after changes.

Custom API access covers supported local Codex workflows. Cloud, plugins, and web search depend on client, authentication, and provider support. Initial setup does not require disabling sandboxing or approval prompts.

Sources​

Official CLI guide · Desktop guide · Windows · Linux · Provider configuration · Authentication. Layout and setup flow also draw on New API and Sub2API.