The project's README from github.com/BytePioneer-AI/codex-host. As one markdown file: README.md.
Run Pi and other Harnesses inside Codex Desktop
We believe Codex Desktop offers the best desktop development experience today.
But Codex isn't the only great Agent Harness — Claude Code and Pi are great too.
CodexHost lets you run other Harnesses natively inside Codex Desktop and have them work together.
⭐ If CodexHost is useful to you, please give it a star! ⭐
Download · Cross-Agent Collaboration · Remote · Community · 简体中文 · 한국어
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
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.
macOS: "App can't be verified" on first launch
xattr -dr com.apple.quarantine /Applications/codexhost.app
Windows: using a portable Codex Desktop
Point CODEXHOST_INSTALL_ROOT at the folder where you extracted Codex Desktop:
[Environment]::SetEnvironmentVariable("CODEXHOST_INSTALL_ROOT", "D:\CodexPortable", "User")
Quit Codex Desktop completely, open a new terminal, and run codexhost.
|
Full workspace
|
|
|
Diff review panel
|
Fork from any message
|
|
Delegate to other Agents with #
|
Tool calls and thinking
|
|
Visible Subagents
|
Remote development
|
|
Usage at a glance
|
One-click account import
|
|
Mermaid diagram rendering
|
Every Harness gets Codex Desktop's native Edit Diff, Fork, message editing, and slash commands.
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-codereview this change on its own and flag any compatibility risks.Have
#pifigure out why this test is flaky.Have
#ompimplement this feature while I keep working on the docs.Have
#opencodeverify 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.
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) |
Before you start, add the remote machine in Codex Desktop under Settings → Connections → SSH. Your local machine can run macOS, Linux, or Windows.
Install and start codexhost on the remote machine:
npm install -g @codexhost/cli
codexhost remote install
codexhost remote start
codexhost remote status
On your local machine, launch Codex Desktop through codexhost and open the SSH workspace.
Pick a Harness from the composer's Agent / Model selector.
SSH setup, diagnostics, and uninstall →
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.
Most multi-agent clients build their own chat UI and plug Harnesses in through a common protocol.
CodexHost does it differently:
|
Join the Community Scan the QR code to join our WeChat group and chat about CodexHost.
|
|
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
Using Pi as an example, here is how a single request flows from left to right: Desktop → shared layer → Pi plugin → native process.
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.