Skip to content
Summer sale. 50% off Pro, $19.50 for life. Desktop app: Apple Silicon Mac only.SUMMER50
CodexUse
Home › Docs › Settings & config

Settings & config

ReferenceUpdated September 2026 · 4 min read

Control how CodexUse and Codex windows behave: one window per account on Accounts, runs on Work, shared Codex defaults, Account Pool, Auto-roll, Cloud Sync, and updates.

What is in Settings

The Settings screen has one rail with nine destinations:

Model Providers

Custom provider connections and published models.

Account Pool

One local API for selected accounts.

Telegram

Bot connection and remote control.

Cloud Sync

Manual encrypted push and pull.

Codex defaults

Validated shared Codex settings and optional account overrides.

Preferences

Theme, usage display, and close behavior.

CodexUse CLI

Install state and status for the optional codexuse-cli.

Support

Diagnostics you can copy when you report a problem.

Features

Opens the feature catalog.

Model Providers, Account Pool, Telegram, and Cloud Sync are grouped under Connections in Settings.

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. Settings holds the two global window options that Auto-roll uses: Take over outside windows and Start refill timers automatically.

Docs: Accounts One Codex window per account

Model Providers

Model Providers is a row under Connections in Settings. Run models from OpenRouter, DeepSeek, Groq, or your own Mac inside the Codex app. Add a connection with a vendor name, base URL, and credential; publish the models you want; then add a custom-model account on that connection from the Accounts tab. The credential stays in the macOS Keychain and is never written into config.toml.

Custom model providers Custom provider guide

Codex config (config.toml)

Open Codex defaults to edit one validated shared TOML source. Add an account override only for values that account needs. CodexUse preserves unknown valid keys, protects authentication and provider routing values, rejects secrets, saves atomically, and shows which idle windows need a restart.

Model defaults

Model, review model, and reasoning defaults.

Approvals

How much Codex asks before it acts.

Sandbox mode

Read-only, workspace-write, or full access for shell and file actions.

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.

Tip: keep the dashboard visible during long-running tasks to avoid manual polling.

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.

Cloud Sync Pro

Move your accounts, config.toml, and app settings between devices with manual push and pull. Nothing syncs in the background, and run state and conversation history are never uploaded. Typical flow: push from your main machine, then pull on the second one.

What syncs

Account credentials, config.toml content, and CodexUse settings. Codex conversations and run state stay local.

Push & Pull

Go to Settings → Cloud Sync and click Push or Pull. Or use codexuse sync push / codexuse sync pull from the CLI on any machine where you installed codexuse-cli.

Pull behavior

Pull replaces local accounts and settings. It replaces config.toml only when the remote snapshot contains one, and it does not create a backup first.

Note: Cloud sync is manual. The trial can test it on its current device; cross-device sync requires Pro. Nothing syncs without your action. Conflicts use last-writer-wins — if your push is older than the remote, you will be asked to pull first.

Example with Pro: keep your main setup on a MacBook, then run codexuse sync pull on another machine with the CLI installed to start with the same accounts and config.

For a full walkthrough, see the cloud sync guide.

Account Pool Pro

Expose selected Codex accounts behind one local OpenAI-compatible endpoint. Account Pool publishes /v1/models, accepts /v1/responses and /v1/chat/completions, generates local API keys, and keeps a pooled session alive by rolling over to another eligible account when one runs into trouble.

Endpoint

Copy the base URL from Settings → Account Pool and hand that exact local endpoint to the client that should use the pool.

Routing

Choose least-used or round-robin for new pooled sessions, while CodexUse keeps continuity for ongoing pooled work.

Published models

Expose only the base models and alias variants you actually want local clients to see.

Start here: read the Account Pool docs for setup, routing, and failover details, then use the client setup guide if you are wiring another OpenAI-compatible tool into the pool.

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

Current desktop releases target macOS on Apple Silicon. Those builds can check for updates and install new releases in-app when available.

Manual upgrade path: If you are on CodexUse 2.5.8 or older, redownload the current app manually once and replace the old install. Intel Mac and Linux desktop builds are not shipped in the current release line.

Themes

Two theme modes are available: Dark and Light. Each theme defines a comprehensive surface palette covering every UI element. The app can follow your system preference automatically.

Dark

Deep surfaces with transparency layers. Designed for low-light environments and extended sessions.

Light

Clean surfaces with slate undertones. Designed for well-lit rooms and daytime use.

Next

Account Pool Accounts Custom model providers MCP, skills, and AGENTS.md CLI reference Troubleshooting