Codex settings without editing config.toml: models, reasoning, MCP

Stop hand-editing config.toml. CodexUse ships a Config panel with quick selects for models, approval policy, sandbox mode, and MCP servers. It writes to the same Codex CLI files already on disk.

What you can change from the UI

• Model and review model: Pick from defaults or type a custom name.
• Reasoning effort and summary style: Set effort and summary keywords without guessing config keys.
• Verbosity: Control how chat replies are logged.
• Approval policy: Never, on-request, on-failure, or untrusted prompts.
• Sandbox mode: Read-only, workspace-write, or danger-full-access.
• MCP servers: Add stdio/http/sse servers with command, args, env, or URL.
• Manual edit: Edit config.toml directly if you want full control.

Set defaults in minutes

1. Open CodexUse.
2. Click the Settings gear, then open Models.
3. Set model, reasoning effort, summary style, verbosity, approval, and sandbox mode.
4. Click Save changes. The app writes to the same config.toml the CLI uses.
5. Need exact ownership? Use the Raw config.toml editor instead of guessing at generated presets.

Manage MCP servers without mistakes

• Add a server with a name, choose stdio/http/sse, and fill command plus args or URL.
• Optional fields: environment variables for stdio servers.
• Edits stay on your machine. Nothing syncs out.

When to use Manual edit

• You already have a config you trust and just want to paste it in.
• You need a key the quick form does not expose yet.
• You are copying a known-good config.toml block between machines. CodexUse will save it as-is.

Troubleshooting saves

• If a field is invalid, the app shows a Sonner toast with the exact error. Fix the field and retry.
• Custom values are allowed; just type them in the custom inputs when the select shows “Custom value”.
• If the file is locked by another process, close that process and click save again. The app logs the failure but keeps your inputs.