Codex Mobile

Keep working even when you are away from your computer. Review, guide, and approve Codex tasks from your phone.

Codex Mobile does not squeeze a full IDE into your phone. Instead, it connects your phone to a computer or remote environment where Codex is already running, so you can review task status, continue conversations, approve operations, and handle work that is waiting for your input.

Choose a Connection Method OpenAI Codex GitHub Back to Codex Desktop

LIVE Monitor Tasks Live View active threads, status updates, and results from your phone.

ASK Continue Guiding Add requirements, adjust direction, or continue an existing task.

OK Approve Remotely Handle operations and permission requests that need your confirmation.

SYNC Move Across Devices Continue the same workflow across desktop, remote environments, and mobile.

Connection Methods

Official mobile experience or an open-source community option?

The official route provides the most complete experience. Open-source options are better suited to users who want to review the code, control the bridge service, and explore local-first connectivity.

OFF

Recommended

Official Codex Remote

Connect to a machine running Codex from the ChatGPT mobile app, then review active tasks, approval requests, extensions, and project context. This route is provided by OpenAI, but the ChatGPT mobile app itself is not an open-source GitHub project.

Best for users who want the official mobile experience and the complete feature set.

Your phone and Codex environment must complete device connection or pairing.

Features and platform support may roll out gradually by region, operating system, and version.

Read the Official Guide Codex Open-Source Repository

OSS

Experimental Open Source

Remodex Community Bridge

A local-first, open-source remote-control bridge for Codex. It keeps the Codex runtime on a Mac and connects an iPhone through a paired session. Remodex is not an official OpenAI product.

Designed for technical users who can build software, review source code, and manage network configuration.

Before use, review the repository status, license, release history, and security notes.

Do not treat an experimental community tool as an official mobile client.

View on GitHub Read the Open-Source Route

Open-Source Tools

Every computer-side tool comes from GitHub.

The official mobile app is distributed through OpenAI’s official app-store channels. This guide does not provide APK or IPA files. All computer-side and open-source bridge tools link directly to their GitHub repositories.

OpenAI Codex

OpenAI’s official open-source Codex project for running Codex CLI and desktop workflows on a local computer.

Official Open Source CLI Desktop Remote Host

GitHub Project Releases

CC Switch

A cross-platform, open-source configuration manager for setting the OmniDino Base URL, API Key, Codex model, and Responses protocol on your computer.

Windows macOS Linux Configuration Manager

GitHub Project OmniDino Guide

Remodex

A community-developed Codex remote bridge with a local-first design, intended for exploring how an iPhone can connect to Codex running on a Mac.

Community Project iPhone Mac Host Experimental

GitHub Project

GIT

Git

Use Git to clone Codex, Remodex, and other open-source projects, and to manage local repositories and version history.

Version Control Clone Diff Cross-Platform

Git for Windows Official Git Repository

Download warning: Do not download a “Codex Mobile APK,” “cracked Codex Mobile,” or third-party IPA from search ads, cloud drives, Telegram groups, or unknown websites. The official mobile experience uses OpenAI’s official mobile app. Obtain experimental open-source options only from the project’s GitHub repository.

Before You Begin

Your phone is the controller. The real working environment remains on the computer.

Codex Is Running

Codex is installed on your computer or remote environment and can open a real project.

OmniDino Is Configured

Codex has successfully completed a basic request through the OmniDino Responses endpoint.

Mobile Entry Point

The official route uses OpenAI’s mobile app. The open-source route uses the mobile client specified by the project.

Network and Device Pairing

The computer is online, the device connection is valid, and the network allows a remote session.

Official Route

Connect your phone with Codex Remote.

Interface labels and button names may change as Codex and ChatGPT are updated. The steps below describe the general connection flow.

macOS Codex App

The official mobile connection is usually initiated from a Mac running the Codex app. Confirm that the desktop app has opened the project and is ready to accept a connection.

Update Codex to a version that supports Remote.

Open Remote, Connect Phone, or the device-connection entry point in the desktop app.

Scan the QR code with Codex on your phone, or select a previously connected device.

Keep the Mac online and verify that active threads appear on the phone.

9:41 Codex Remote ●

OmniDino Website Connected to Mac · Active

Task running Updating the WordPress guide page and checking responsive styles.

Approval required Codex wants to modify 3 project files.

Approve

Review

Windows Codex Host

Mobile connectivity on Windows may roll out gradually by version. Check the Codex app, official documentation, and GitHub Issues first instead of applying macOS instructions mechanically to Windows.

Update Codex to the latest version.

Check whether Remote or Phone Connection is available in the desktop app.

If your version has no connection entry point, use Codex CLI for now or wait for official support.

Do not install an unofficial “Windows Mobile Bridge.”

9:41 Device Status ●

Windows Host Feature availability depends on version

Check desktop first Look for Remote, Connect phone, QR pairing, or connected devices.

No pairing option? Use Codex CLI and watch official release notes.

Remote Environment or Mac mini

The official mobile experience can connect to a dedicated machine or remote environment running Codex, but that environment must remain online and available.

First confirm that the project and Codex run correctly on the host.

Keep the network, device connection, and authorization status valid.

Mobile is suitable for supervision and guidance, not as a replacement for remote system administration.

When the host goes offline, the phone cannot continue executing local tool calls.

9:41 Remote Machine ●

Dedicated Mac mini Online · 2 active threads

Thread 01 Reviewing API connection test page.

Thread 02 Waiting for permission to run tests.

Open thread

View all

How OmniDino relates to the mobile connection: OmniDino provides the model API and billing for Codex on the computer. Codex Remote or an open-source bridge handles the phone connection. You normally do not enter the OmniDino API Key separately on the phone.

Complete Connection Flow

Get Codex working on the desktop before connecting your phone.

Install Codex and Git

Install the computer-side tools from the official OpenAI Codex and Git GitHub projects.

Configure OmniDino

Use CC Switch or config.toml to set the OmniDino Base URL, API Key, Codex model, and Responses protocol.

Verify Computer-Side Requests

Run a simple task, confirm that Codex responds correctly, and verify that the request appears in the OmniDino console.

Open the Phone Connection

In the Codex desktop app, find Remote, Connect Phone, a QR code, or Connected Devices.

Open Codex on Your Phone

Open the Codex section in OpenAI’s official mobile app, then scan the QR code or select a connected computer.

The phone and computer must meet the official account, device-authorization, and feature-availability requirements.

Confirm the Workspace and Active Threads

Check whether the phone can see projects, threads, approval requests, and active tasks from the computer.

Send a Safe Test Instruction

First ask Codex to report the current task status. Do not use your first remote session to approve file deletion, deployment, or production changes.

Check OmniDino Usage

After continuing the task from your phone, confirm that the OmniDino console shows reasonable requests, token usage, and balance changes.

Open-Source Route

Understand Remodex’s boundaries before using it.

Remodex is a community open-source bridge, not OpenAI’s official mobile client. Because it is a newer project, carefully review its code, permissions, network model, and release history.

MAC

Host

Local Bridge on Mac

The Codex runtime remains on the Mac. A bridge service creates the paired session, so the phone connects to the bridge layer instead of uploading the entire project to a third-party server.

Clone the GitHub repository and read the README.

Review the bridge service’s listening address and firewall rules.

Complete the first pairing only with a test project.

View Remodex

IOS

Client

iPhone Pairing Client

The phone connects to the Mac using short-lived pairing or the authentication method defined by the project. Follow the repository’s current documentation for installation, build requirements, and supported versions.

Confirm that the project provides reviewable iOS source code.

Do not install a prebuilt IPA from an unfamiliar source.

Revoke devices and sessions you no longer use.

Read the Build Instructions

Community project safety: OmniDino does not guarantee the security, availability, or maintenance status of Remodex or any other third-party open-source bridge. Review the code, license, Issues, commit history, and network behavior before use.

Mobile Capabilities

Ideal for supervising and moving active work forward.

View Task Status

See whether Codex is analyzing, editing, testing, or waiting for input.

Continue the Conversation

Add requirements, correct the direction, or ask Codex to continue to the next step.

Handle Approvals

Review file changes, commands, or tool calls that require authorization.

Review Results

Read task summaries, execution results, errors, and Codex explanations.

Manage Active Threads

Switch between multiple Codex threads that are currently running.

Start a New Task

Where supported, create or organize new engineering tasks from your phone.

Limitations

Mobile cannot replace a complete development environment.

Not for Initial Setup

Configure the OmniDino Base URL, API Key, model, and Responses protocol on the computer first.

Not a Replacement for an IDE

A phone screen is not suitable for reviewing large diffs, complex code structures, or extensive file changes.

The Host Must Stay Online

Local projects, tools, and commands still run on the computer or remote environment. Host downtime interrupts these capabilities.

Do Not Approve Blindly

Convenient mobile access is not a reason to approve deletion, deployment, or privileged commands without review.

Remote-Use Security Checklist

Use a dedicated OmniDino API Key and spending limit for Codex.

Lock the computer when you step away, but keep required background services running.

Connect only phones and computers that you trust.

Regularly review and revoke unused device connections.

Before approval, review the command, affected files, and project environment.

Do not handle high-risk production tasks over public Wi-Fi.

Never expose pairing QR codes, short-lived links, or device tokens.

Connect community bridge tools only to test projects during initial evaluation.

FAQ

What should you do when the phone keeps waiting for the desktop?

The official mobile experience is part of OpenAI’s mobile app, not a standalone open-source phone app in the openai/codex GitHub repository. openai/codex is the official open-source Codex codebase and computer-side foundation.

Check that Codex is still running on the computer, the device connection remains valid, the network permits the connection, and the current desktop and mobile versions support the feature. You can revoke the old device and pair it again.

Confirm that the project is open in the Codex app and that the phone is connected to the correct computer or environment. Some SSH projects, extensions, or workspaces may not be fully visible, depending on support in the current version.

The official remote route normally uses the model configuration from the Codex environment on the computer. The phone controls the session, so it should not require you to expose the OmniDino Key again. If a third-party bridge asks for a key, review its architecture and storage method first.

Windows support depends on the current Codex version and the official rollout schedule. Check whether Remote or device connection is available in the desktop app. Do not install an unknown third-party patch when no official entry point is present.

It is not recommended for important production projects without evaluation. Remodex is an experimental community project. Review the code and maintenance status, then validate permissions, connectivity, and logging in an isolated test project.

First confirm that the mobile action actually triggered a model request rather than only displaying local status. Then verify that Codex on the computer still uses the current OmniDino configuration, the model name is correct, and CC Switch is set to the intended provider.

Still unable to connect Codex Mobile?

When contacting support, provide the computer operating system, Codex version, phone operating system, connection method, whether a QR code is visible, the error message, and the time of the issue. Hide API Keys, QR codes, and device tokens.

[email protected]

Complete your Codex workflow.

Previous Guide

Codex Desktop

Finish Codex installation, OmniDino configuration, and project workflows on the desktop.

Next Guide

Codex CLI

Use Codex from the terminal and configure providers, models, and Responses in greater depth.