Claude Codex

Claude Codex Adapter

Production TypeScript adapter that lets the Codex desktop app talk to
Claude Code through the native Codex app-server protocol in Remote mode.

Codex App still runs its normal SSH version probe, bootstrap, and app-server
proxy flow — but codex app-server is handled by this adapter instead of the
real Codex runtime, so agent turns run on Claude Code.

Claude, asked in a Codex App chat to chart six months of signups,
answers with an inline visualization that the
App renders inside the reply. The request was in Chinese, so are the labels.

📖 Documentation:

Quick start
Requires Node.js 24+ for stable node:sqlite. Set CLAUDE_CODEX_NODE to
pin a node binary if your default is older.

Then install the codex shim on the remote host and add a Remote connection in
the Codex App:

Provide credentials only through your local shell or secret manager. Do not
commit API keys, OAuth/session data, .env files, or acceptance-test logs.

Full walkthrough → Getting started.

How it works

Agent text and reasoning stream into the conversation, Claude's thinking as the
reasoning summary the App shows (CLAUDE_CODEX_REASONING_VISIBLE=0 hides it);
Bash and other tools become command approvals; Edit/Write/MultiEdit
become file-change approvals with live diffs; MCP tool calls get the App's MCP
tool approval card. Runtime selection maps only to existing backend paths today: default
in-process Claude Agent SDK, agent-http, agentapi, claude-p, codex-proxy,
and mock.

The App starts one adapter daemon with codex app-server --listen unix:// and
reaches it through codex app-server proxy. Neither names a socket, so both use
$CODEX_HOME/app-server-control/app-server-control.sock by default. To put it
somewhere else, set CLAUDE_CODEX_SOCKET_PATH to an absolute path in a folder…