IntegrationsCodexConfigure WebSocket (validation required)

Enable WebSocket

Complete Configure Model Provider first, then run the one-line command to enable the Codex Responses protocol format and WebSocket connection. The script only updates connection capability. It does not read, save, or overwrite your API key.

curl -fsSL https://kineticrouter.com/install/codex.sh | bash

The kineticRouter helper creates a provider config only when no existing Codex config is present. It exits without modifying an existing config so you can review changes manually. The example below uses kineticrouter as the provider name; if your local provider uses another name, replace kineticrouter with that name:

[model_providers.kineticrouter] wire_api = "responses" supports_websockets = true

wire_api = "responses" tells Codex to use the Responses protocol format; supports_websockets = true tells Codex this provider supports a WebSocket connection. Together, they request the Responses format and WebSocket transport. Confirm both behaviors with your account before relying on them.

The API key stays in the CC Switch Codex provider settings. This configuration requests the Codex Responses format and WebSocket connection; runtime support remains account-tested.

If your config uses an inline table under [model_providers], the script updates the existing provider entry instead of forcing another TOML layout.