Codex

Configure the Codex CLI to send its requests to FlexInference. Do not change my existing Codex setup: create a separate profile I opt into per run.

You will never see or handle my API key. The profile stores only the NAME of an environment variable, and I export the value myself. Do not ask me for the key, and do not read it from my environment.

1. Create `~/.codex/flexinference.config.toml` with exactly this content:

model = "gpt-5.6-sol"
model_provider = "flexinference"

[model_providers.flexinference]
name = "FlexInference"
base_url = "https://api.flexinference.com/v1"
wire_api = "responses"
env_key = "FLEX_API_KEY"

2. Tell me to export the key myself, in the shell I will run Codex from:

   export FLEX_API_KEY=<paste your key here>

   Print that line for me to run. Do not run it, do not ask for the value, and do not add it to my shell profile.

3. Tell me to start Codex with `codex --profile flexinference`.

Rules that matter, do not deviate:
- Keep the `model` line. Codex defaults to a slug ending in `-codex`, which FlexInference recognizes but holds no price for and never races. Use the full `gpt-5.6-sol`; the bare `gpt-5.6` alias makes Codex print a metadata warning.
- Keep `wire_api = "responses"`. FlexInference serves that surface at `/v1/responses`.
- Never add `service_tier`. FlexInference derives the tier from the key's deadline and returns `400 service_tier_not_allowed` if the request carries its own.
- `env_key` and `auth` are mutually exclusive. Use `env_key` unless I ask for a keychain helper.
- Do not set `request_max_retries`. My key may carry its own retry policy and the two stack.

Verify by checking the file parses under `codex --profile flexinference --strict-config`, then report what you changed.