Sponsors

Click to collapse

Thanks to 星链AI (Xinglian AI) for sponsoring this project! Xinglian AI provides a stable, efficient API relay service for AI coding tools such as Codex and CodexHost, with quick access to mainstream AI models: stable routes · fast responses · multi-model compatibility · ready to use out of the box. It cuts the cost of configuring and switching APIs, so you can focus on coding. Try it now →

Thanks to VibeAPI for sponsoring this project! Built for power developers and teams, VibeAPI provides unified access to mainstream AI models, focusing on the Codex and Claude series with a self-managed, traceable account pool. It offers ultra-fast time to first token, 99.9% SLA availability, and cache hit rates of 95%+. Human technical support is available 24/7, with corporate invoicing and enterprise partnerships fully supported. Grab some cyber goodies →

Interface Preview

No more switching apps: Pi, Claude Code, Grok Build, and ten-plus other Harnesses all run right inside the same Codex Desktop window.

https://github.com/user-attachments/assets/c48192d7-23ff-4f6e-b61a-6345a655bb76

Interface

Quick Start

Option 1: npm (macOS / Windows / Linux)

npm install -g @codexhost/cli
codexhost

Option 2: Installer (macOS / Windows)

Grab the installer for your platform from Releases.

Linux is supported on x64 and ARM64. See the Linux guide.

Run codexhost update to check for the latest release and prepare an upgrade from your terminal. Quit Codex Desktop first if an upgrade is available. Once preparation completes, the background updater installs it and restarts codexhost. An up-to-date installation exits without changes.

xattr -dr com.apple.quarantine /Applications/codexhost.app

Highlights

Full workspace Sessions from different Harnesses share one sidebar; switch Agents from the bottom-right of the composer
Diff review panel Every turn summarizes its changes; click Review to open the full Diff on the right	Fork from any message Branch in the current workspace, or in a new Worktree for parallel work
Delegate to other Agents with # Each Agent runs in its own session, in parallel · Learn more	Tool calls and thinking Expand any edit, command, or thinking step to see the details
Visible Subagents Each Subagent has its own icon; open its full conversation on the right	Remote development Add a VPS as a project and run Agents directly on the remote machine · Learn more
Usage at a glance Cache hit rate, cost estimate, and context usage, live	One-click account import Copy your locally signed-in Codex and Grok credentials to Pi, with live quota
Mermaid diagram rendering Left: Codex Desktop + Pi renders the diagram; right: the Pi TUI only shows the source

Feature Status

Every Harness gets Codex Desktop's native Edit Diff, Fork, message editing, and slash commands.

Show full feature matrix

Capability
Streaming responses	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Tool status	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Edit Diff	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Questions / cancellation	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Model / Thinking selection	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Tool approvals	✅	✅	✅	✅	✅	✅	—	✅	✅	✅	✅	✅	✅
Permission modes	—	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Cross-Agent task collaboration	✅	✅	✅	✅	✅	✅	✅	✅	—	✅	✅	✅	✅
Usage	✅	✅	✅	✅	✅	✅	✅	✅	✅	—	✅	✅	✅
Fork	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	◐
Context compaction	✅	✅	✅	✅	✅	✅	—	✅	✅	—	✅	✅	✅
Slash commands	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Edit previous message	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅

Cross-Agent Collaboration

Type # in the chat input to choose an Agent to delegate a task to, or to find commands and skills available for the selected Harness.

Ask the current Agent to hand off a self-contained task to another Harness. For example:

Have #claude-code review this change on its own and flag any compatibility risks.

Have #pi figure out why this test is flaky.

Have #omp implement this feature while I keep working on the docs.

Have #opencode verify this fix in a separate Thread and run the related tests.

CodexHost spins up a separate Native Session in the target Harness. It shows up in the Codex Desktop conversation list, so you can open it anytime to check progress or pick up the conversation.

Remote Harness

Drive Harnesses on another machine from your local Codex Desktop: tasks run remotely, the UI stays local. Both machines need the same codexhost version.

Remote machine	How to connect
macOS / Linux	SSH
Windows	Remote Control (experimental)

SSH

Before you start, add the remote machine in Codex Desktop under Settings → Connections → SSH. Your local machine can run macOS, Linux, or Windows.

1. Install and start codexhost on the remote machine:

   npm install -g @codexhost/cli
   codexhost remote install
   codexhost remote start
   codexhost remote status
   

2. On your local machine, launch Codex Desktop through codexhost and open the SSH workspace.

3. Pick a Harness from the composer's Agent / Model selector.

SSH setup, diagnostics, and uninstall →

Remote Control (Experimental)

Use Harnesses on a Windows machine from another computer, built on the pairing and sign-in of Codex Desktop's official Remote Control.

Before you start, make sure official Remote Control can already run Codex tasks. No public services or ports are opened, and Harness credentials never leave the Windows machine.

Remote Control setup, transport boundary, and diagnostics →

微信交流群

微信交流群 Scan the QR code to join our WeChat group and chat about CodexHost. Get help with installation Share feature ideas and feedback Talk about development For bugs, please open an issue Contributions are welcome.

Development

Please read the contributing guide before opening an issue or PR. See repository maintenance automation for PR title labels, CI summaries, and pre-release checks.

Requirements: the official Codex Desktop, Node.js 22.19+ or 24, and Rust.

git clone https://github.com/BytePioneer-AI/codex-host
cd codex-host
npm ci
npm start

To run the current source with a specific runtime version, use npm start 0.12.0 (prereleases such as 0.13.0-rc.1 are also accepted). Host status, console version and update-check version reporting use this value. Without a version argument the version remains <workspace-version>-dev; npm start 0.12.0 -- --no-build reuses artifacts after building once. The override lasts for this launch and does not modify version files or publish packages. Source installations still lack packaged self-update resources; remote npm installation downloads the published package with that version, not the local source.

Runtime Architecture

Using Pi as an example, here is how a single request flows from left to right: Desktop → shared layer → Pi plugin → native process.

Adding a Harness

Most of the work is implementing the plugin's Manifest, factory, Adapter, and Session, plus the native communication and translation logic. The Renderer still has some hard-coded wiring, so full Desktop integration takes extra work.

Tip: point your coding Agent at the in-repo codexhost-add-harness Skill. It covers plugin structure, the shared Adapter interface, capability implementation, and testing requirements.

Acknowledgements

• Thanks to the LINUX DO community for their ongoing support.
• Thanks to Paseo, whose approach to multi-Harness integration and architecture inspired ours.

Contributors

Thanks to everyone who has contributed to CodexHost.

Star History