Settings & config

Control how CodexUse and Codex windows behave: one window per account on Accounts, the tools in For agents, and one Settings page for preferences, Codex defaults, codexuse in Terminal, and support.

The sidebar

The CodexUse sidebar has three parts:

The Settings page stacks four sections, in this order:

Codex windows

Window behavior lives on the Accounts tab, not in Settings. Each account gets one Codex window: Open starts it and Show brings it forward. The Auto-roll menu below the account list holds its global window options: Take over outside windows and Start refill timers automatically.

Providers

Providers is in the For agents group of the sidebar. Use models from OpenRouter, DeepSeek, Ollama, and other providers in the Codex app. Add a provider with a name, base URL, and API key; add a model and click Save and test; then add a custom-model account for that provider from the Accounts tab. The API key stays encrypted in CodexUse's private app database and is never written into config.toml.

Codex config (config.toml)

Every account follows your own Codex config file, ~/.codex/config.toml. Edit it as you always would; Open in Codex defaults opens it in a text editor. Before an account starts, CodexUse brings its config up to date with the file. A value an account changed for itself, such as a theme picked inside its Codex window, stays on that account. Sign-ins, API keys, and custom-model routing are never copied between accounts.

Codex defaults shows the model, reasoning effort, approval, and sandbox from the file, and lists each account that differs, such as Differs: desktop.theme. Reset gives that account the whole file again. If the file has a syntax error, Settings shows the line, and every account keeps its current config until you fix it.

Codex’s own documentation is the reference for the exact keys. See MCP, skills, and AGENTS.md for the MCP server blocks.

Notifications

In-app status signals track long-running sessions so you do not have to watch them.

AGENTS.md

Write persistent agent instructions once and reuse them across sessions.

• A global AGENTS.md for shared Codex guidance.
• Workspace-level overrides when a project needs them.
• Keep instructions short and actionable.

Account Pool Pro

Let Cursor, scripts, and other apps use your accounts through one local OpenAI-compatible endpoint. When one account hits its limit, the next one takes over. Account Pool publishes /v1/models, accepts /v1/responses and /v1/chat/completions, and generates local API keys.

You can manage the same pool from the CLI too: codexuse account-pool status, codexuse account-pool profiles set ..., and codexuse account-pool keys create for the desktop runtime. The settings, API keys, and pooled sessions belong to the desktop app runtime store.

Updates

macOS builds check for updates and install new releases in-app when available. Automatic updates are disabled on Windows because the packaging runtime cannot apply one reliably yet, so a newer Windows package is installed manually. Linux update artifacts ship with each release, and the full old-to-new lifecycle is still in native QA. See platform support.

Themes

Choose Light, Dark, or Follow system in Preferences. The default is Light. Follow system continues tracking the system appearance after you leave Preferences.