config-reference.md +29 −0
2227For ChatGPT Business and Enterprise users, Codex can also apply cloud-fetched2227For ChatGPT Business and Enterprise users, Codex can also apply cloud-fetched
2228requirements. See the security page for precedence details.2228requirements. See the security page for precedence details.
2229 2229
2230Use `[features]` in `requirements.toml` to pin feature flags by the same
2231canonical keys that `config.toml` uses. Omitted keys remain unconstrained.
2232
2230| Key | Type / Values | Details |2233| Key | Type / Values | Details |
2231| --- | --- | --- |2234| --- | --- | --- |
2232| `allowed_approval_policies` | `array<string>` | Allowed values for `approval_policy` (for example `untrusted`, `on-request`, `never`, and `reject`). |2235| `allowed_approval_policies` | `array<string>` | Allowed values for `approval_policy` (for example `untrusted`, `on-request`, `never`, and `reject`). |
2233| `allowed_sandbox_modes` | `array<string>` | Allowed values for `sandbox_mode`. |2236| `allowed_sandbox_modes` | `array<string>` | Allowed values for `sandbox_mode`. |
2234| `allowed_web_search_modes` | `array<string>` | Allowed values for `web_search` (`disabled`, `cached`, `live`). `disabled` is always allowed; an empty list effectively allows only `disabled`. |2237| `allowed_web_search_modes` | `array<string>` | Allowed values for `web_search` (`disabled`, `cached`, `live`). `disabled` is always allowed; an empty list effectively allows only `disabled`. |
2238| `features` | `table` | Pinned feature values keyed by the canonical names from `config.toml`'s `[features]` table. |
2239| `features.<name>` | `boolean` | Require a specific canonical feature key to stay enabled or disabled. |
2235| `mcp_servers` | `table` | Allowlist of MCP servers that may be enabled. Both the server name (`<id>`) and its identity must match for the MCP server to be enabled. Any configured MCP server not in the allowlist (or with a mismatched identity) is disabled. |2240| `mcp_servers` | `table` | Allowlist of MCP servers that may be enabled. Both the server name (`<id>`) and its identity must match for the MCP server to be enabled. Any configured MCP server not in the allowlist (or with a mismatched identity) is disabled. |
2236| `mcp_servers.<id>.identity` | `table` | Identity rule for a single MCP server. Set either `command` (stdio) or `url` (streamable HTTP). |2241| `mcp_servers.<id>.identity` | `table` | Identity rule for a single MCP server. Set either `command` (stdio) or `url` (streamable HTTP). |
2237| `mcp_servers.<id>.identity.command` | `string` | Allow an MCP stdio server when its `mcp_servers.<id>.command` matches this command. |2242| `mcp_servers.<id>.identity.command` | `string` | Allow an MCP stdio server when its `mcp_servers.<id>.command` matches this command. |
2282 2287
2283Key2288Key
2284 2289
2290`features`
2291
2292Type / Values
2293
2294`table`
2295
2296Details
2297
2298Pinned feature values keyed by the canonical names from `config.toml`'s `[features]` table.
2299
2300Key
2301
2302`features.<name>`
2303
2304Type / Values
2305
2306`boolean`
2307
2308Details
2309
2310Require a specific canonical feature key to stay enabled or disabled.
2311
2312Key
2313
2285`mcp_servers`2314`mcp_servers`
2286 2315
2287Type / Values2316Type / Values