OmniDino
Home Models Pricing Guides About Contact Login Get API Key
EN 中文
Codex CLI

Use OmniDino to power Codex from your terminal.

Install OpenAI’s official open-source Codex CLI, call available Codex models through the OmniDino Responses endpoint, and handle code understanding, editing, refactoring, testing, and automation in real projects.

CLITerminal NativeStart directly inside the project directory without switching to a browser.
OSSOfficial Open SourceOpenAI publicly maintains the Codex CLI source code on GitHub.
AIEngineering TasksUnderstand, debug, refactor, review, and automate development work.
APIConnect OmniDinoUse one Base URL, API Key, Responses protocol, and the actual model name.
Tool Overview

What is Codex CLI?

It is not an ordinary chat window. Codex CLI is a coding agent that can read projects, call tools, and assist with engineering tasks directly from the terminal.

Start inside the project directory so the context stays with the code.

Codex CLI understands files relative to the current working directory, proposes changes, runs permitted commands, and displays the results. Before using it in earnest, confirm that the repository, permissions, model, and OmniDino API are configured correctly.

Interactive SessionsRun codex to keep working with the agent in an ongoing terminal conversation.
Non-Interactive TasksUse codex exec for one-off automated tasks, scripts, and CI workflows.
Resume SessionsUse codex resume to continue an existing thread without repeating the project background.
Open-Source Download Center

Every installation tool comes from GitHub.

CX

OpenAI Codex

OpenAI’s official open-source Codex CLI project, with installation scripts, npm, Homebrew, and GitHub Releases.

WindowsmacOSLinuxApache-2.0
SW

CC Switch

A cross-platform, open-source configuration manager for Codex providers, Base URLs, models, and protocol settings.

WindowsmacOSLinuxProvider Management
GIT

Git

When Codex works in a real repository, Git provides version control, diff review, and change recovery.

Version ControlRepositoriesDiffCross-Platform
NODE

Node.js

Node.js and npm are required only when installing Codex through npm. The official installer and binary methods may not require them.

npmJavaScript RuntimeOpen Source
Do not download modified Codex builds from cloud drives, group chats, or unknown websites. Prefer the official openai/codex installation methods or GitHub Releases.
Install Codex CLI

Choose the installation method for your operating system.

Windows PowerShell

Use OpenAI’s official installer. Reopen PowerShell after installation.

Install Git for Windows first if possible.
Run codex --version to verify the installation.
Approve the administrator prompt if PowerShell displays an execution-policy warning.
PowerShell
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"

codex --version

macOS / Linux

Run OpenAI’s official shell installer, then check the installed version.

Suitable for users who do not want to install Node.js first.
A Linux graphical desktop is not required to use the CLI.
Follow the official README for update instructions.
Terminal
curl -fsSL https://chatgpt.com/codex/install.sh | sh

codex --version

Global npm Installation

Users who already have Node.js and npm can install the official npm package.

Do not use sudo as a blunt workaround for npm permission problems.
After installation, confirm that PATH includes the global npm binary directory.
Run the npm installation command again when upgrading.
npm
npm install -g @openai/codex

codex --version

Homebrew

macOS users can install Codex with Homebrew Cask.

Use --cask.
Use the Cask method for upgrades as well.
Run a version check after installation.
Homebrew
brew install --cask codex

codex --version

GitHub Release

Manually select the official binary that matches your operating system and CPU architecture.

The repository must be openai/codex.
On macOS, distinguish between Apple Silicon and Intel.
On Linux, distinguish between x86_64 and arm64.
Release Files
macOS arm64:
codex-aarch64-apple-darwin.tar.gz

macOS x86_64:
codex-x86_64-apple-darwin.tar.gz

Linux x86_64:
codex-x86_64-unknown-linux-musl.tar.gz

Linux arm64:
codex-aarch64-unknown-linux-musl.tar.gz
Connect OmniDino

Configure the Base URL, model, and Responses protocol.

CC Switch is recommended. For manual configuration, add the provider to the user-level ~/.codex/config.toml.

OmniDino Parameters

Copy the exact model name from the OmniDino model catalog. Do not guess it.

Provideromnidino
Base URLhttps://api.omnidino.com/v1
Wire APIresponses
API Key EnvOMNIDINO_API_KEY
ModelThe exact name shown in the model catalog
Store the API Key in an environment variable instead of a project file that may be synchronized or committed.
~/.codex/config.toml
model_provider = "omnidino"
model = "ENTER_THE_ACTUAL_CODEX_MODEL_NAME"
model_reasoning_effort = "high"
disable_response_storage = true

[model_providers.omnidino]
name = "OmniDino"
base_url = "https://api.omnidino.com/v1"
env_key = "OMNIDINO_API_KEY"
wire_api = "responses"
Set the API Key
export OMNIDINO_API_KEY="PASTE_YOUR_OMNIDINO_API_KEY"

codex
Common Commands

From interactive sessions to automated tasks.

CommandPurposeRecommendation
codexStart an interactive Codex CLI session.Enter the correct project directory first.
codex --versionShow the installed version.Record the version before troubleshooting.
codex --helpDisplay commands and options supported by the installed version.Trust the output from your local installation.
codex exec "TASK"Run a one-off non-interactive task.Useful for scripts, automation, and CI.
codex resumeSelect and resume an existing session.Resume it from the correct project directory.
codex resume <session-id>Resume a specific session.Useful for precise continuation or handoff between tools.
codex appLaunch the Codex desktop experience when supported by the installed version.Continue using the CLI if unavailable.
Recommended Model Types

Choose a model for the task, not just by its name.

01

Codex-Specialized Models

Best for complete engineering tasks, tool calls, multi-file changes, and long coding sessions.

02

Advanced Reasoning Models

Best for architecture analysis, complex debugging, migration plans, and technical decisions.

03

Cost-Efficient Models

Best for code explanation, summaries, simple edits, and batch tasks.

04

Long-Context Models

Best for large repositories, documentation-heavy projects, and cross-module analysis.

05

Multimodal Models

Best for workflows that combine screenshots, designs, logs, and code.

06

Self-Hosted Models

Best for cost-sensitive batch processing and controlled infrastructure.

Complete Workflow

From installation to your first real task.

01

Install Git and Codex

Use the official GitHub projects and installation methods, then verify the installed versions.

02

Create a Dedicated API Key

Create a Codex-specific Key in the OmniDino console and set a sensible spending limit.

03

Configure the OmniDino Provider

Use CC Switch or user-level config.toml to set the Base URL, Responses protocol, and model.

04

Set the Environment Variable

Store the API Key in OMNIDINO_API_KEY instead of placing it directly in project source code.

05

Run an API Connection Test

Test /v1/models and /v1/responses first to confirm the Key, model, and endpoint are working.

06

Enter a Test Repository

Do not open an important production project first. Use a small Git repository to verify permissions and editing behavior.

07

Start Codex

Run codex and ask it to explain the README or complete a small, reviewable task.

08

Review Usage and the Diff

Confirm that the OmniDino request logs, balance changes, and Git diff all match your expectations.

FAQ

Start here when configuration fails.

Reopen the terminal, confirm that installation succeeded, and verify that the Codex executable is on PATH. npm users must also ensure that the global npm binary directory is included in PATH.
The env_key in config.toml points to OMNIDINO_API_KEY, so the current terminal must contain an environment variable with the same name. Set it again, then run codex in that same terminal.
Check that the API Key was copied completely, has not been disabled, contains no unintended quotes or spaces in the environment variable, and has permission to access the target model.
Confirm that the Base URL is https://api.omnidino.com/v1, wire_api is responses, and both the selected model and upstream channel actually support Responses.
Sensitive provider and model-provider settings should be stored in the user-level ~/.codex/config.toml. Some versions ignore model_provider and model_providers in project-level configuration.
Custom-provider model discovery and interface display may vary by Codex version. You can still use the model directly when config.toml contains the correct name and the Responses request succeeds.
Work inside a Git repository, use a separate branch, review the plan and diff first, never approve privileged commands blindly, and use an isolated project for initial testing.

Still unable to connect Codex CLI?

Provide the operating system, Codex version, installation method, model name, Base URL, wire_api value, HTTP status code, and complete error message. Hide the API Key.

[email protected]
Continue Reading

Move to the next client guide.