codex-bridge

Name: codex-bridge
Author: xallindrome-labs

by xallindrome-labsversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.xallindrome-labs/codex-bridge

Install

Overview

Description from the maker (original English)

Lets Claude Code consult the Codex CLI for plans and images, as durable background jobs.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CODEX_BIN, CODEX_BRIDGE_HOME, CODEX_BRIDGE_IDLE_TIMEOUT_MS, CODEX_BRIDGE_PLAN_MODEL, CODEX_BRIDGE_PLAN_EFFORT, CODEX_BRIDGE_IMAGE_MODEL, CODEX_BRIDGE_IMAGE_EFFORT

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "codex-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@xallindrome-labs/codex-bridge"
      ],
      "env": {
        "CODEX_BIN": "your-value",
        "CODEX_BRIDGE_HOME": "your-value",
        "CODEX_BRIDGE_IDLE_TIMEOUT_MS": "your-value",
        "CODEX_BRIDGE_PLAN_MODEL": "your-value",
        "CODEX_BRIDGE_PLAN_EFFORT": "your-value",
        "CODEX_BRIDGE_IMAGE_MODEL": "your-value",
        "CODEX_BRIDGE_IMAGE_EFFORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add codex-bridge --env CODEX_BIN=your-value --env CODEX_BRIDGE_HOME=your-value --env CODEX_BRIDGE_IDLE_TIMEOUT_MS=your-value --env CODEX_BRIDGE_PLAN_MODEL=your-value --env CODEX_BRIDGE_PLAN_EFFORT=your-value --env CODEX_BRIDGE_IMAGE_MODEL=your-value --env CODEX_BRIDGE_IMAGE_EFFORT=your-value -- npx -y @xallindrome-labs/codex-bridge

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "codex-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@xallindrome-labs/codex-bridge"
      ],
      "env": {
        "CODEX_BIN": "your-value",
        "CODEX_BRIDGE_HOME": "your-value",
        "CODEX_BRIDGE_IDLE_TIMEOUT_MS": "your-value",
        "CODEX_BRIDGE_PLAN_MODEL": "your-value",
        "CODEX_BRIDGE_PLAN_EFFORT": "your-value",
        "CODEX_BRIDGE_IMAGE_MODEL": "your-value",
        "CODEX_BRIDGE_IMAGE_EFFORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "codex-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xallindrome-labs/codex-bridge"
      ],
      "env": {
        "CODEX_BIN": "your-value",
        "CODEX_BRIDGE_HOME": "your-value",
        "CODEX_BRIDGE_IDLE_TIMEOUT_MS": "your-value",
        "CODEX_BRIDGE_PLAN_MODEL": "your-value",
        "CODEX_BRIDGE_PLAN_EFFORT": "your-value",
        "CODEX_BRIDGE_IMAGE_MODEL": "your-value",
        "CODEX_BRIDGE_IMAGE_EFFORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CODEX_BIN env
Path to the Codex CLI binary. Auto-detected when unset.
CODEX_BRIDGE_HOME env
Where job files are stored. Default: ~/.codex-bridge
CODEX_BRIDGE_IDLE_TIMEOUT_MS env
Stop a run after this many ms with no Codex output. Default: 600000
CODEX_BRIDGE_PLAN_MODEL env
Model for codex_plan. Default: your Codex config.
CODEX_BRIDGE_PLAN_EFFORT env
Reasoning effort for codex_plan. Default: your Codex config.
CODEX_BRIDGE_IMAGE_MODEL env
Model for codex_image. Default: gpt-6-luna
CODEX_BRIDGE_IMAGE_EFFORT env
Reasoning effort for codex_image. Default: high

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account xallindrome-labs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32708 servers in this category
Published to the registry more recently than 71% of the other 32708 servers in this category
Basic checks equal to or better than 100% of the other 32708 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is codex-bridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, OpenTakeoff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

OpenTakeoff

by Kentucky-ai

Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

codex-bridge

Codex jobs for Claude Code that survive crashes, closed windows and reboots, with Codex image generation built in. A dependency-free MCP server built Windows-first: every call is a job saved on disk, so you can close Claude, lose power, or kill a process, and pick the work up again with codex_resume.

Roles: Claude Code implements. Codex plans and builds images. Optionally (opt-in, one folder), Codex can also write code while Claude reviews: see Let Codex write code. And an optional pane beside the chat lists your jobs live and shows your Codex usage and when it resets: see Codex jobs pane.

The server calls in this recording are real (Codex at effort: low, idle time trimmed); the claude mcp add line is scripted. The raw recording is docs/demo.cast; play it with asciinema play docs/demo.cast.

Quickstart

You need Node.js 20 or newer and the Codex CLI installed and logged in.

claude mcp add codex-bridge -- npx -y @xallindrome-labs/codex-bridge

Restart Claude Code, then ask it something like *"Get a plan from Codex for adding rate limiting, in the background, and keep going"*. Claude will call codex_plan with background: true and collect the answer later.

Other MCP clients: run npx -y @xallindrome-labs/codex-bridge as a stdio server.

Platform note: developed and tested on Windows 11, where real Codex jobs have been run. CI checks on Linux, macOS and Windows (Node 20 and 22) that the server starts, speaks MCP and works when installed from the npm tarball, and on Linux and macOS that jobs run, finish and survive the server being killed, using a fake codex. CI has no real Codex CLI, so real Codex jobs on macOS and Linux are untested. Reports and fixes are welcome.

Tool	What it does	Sandbox	Default model / effort
`codex_plan`	Codex writes implementation plans, design reviews and second opinions. It inspects the project in `cwd`.	`read-only` (always)	Your Codex config defaults
`codex_image`	Codex generates or edits images. The bridge copies each one into `output_dir` as soon as it's made.	`read-only` (always)	gpt-6-luna / high
`codex_code`	Off by default. Codex implements a change by editing files in one folder you choose. See below.	`workspace-write`, that folder only, no network	Your Codex config defaults
`codex_result`	Gets a job's result or progress (`wait_seconds` up to 240), or lists recent jobs.
`codex_resume`	Continues an interrupted, timed-out or failed job from where it stopped.
`codex_cancel`	Stops a running job.

codex_plan, codex_image and codex_code accept:

effort: low, medium, high, xhigh, max or ultra (Luna supports up to max).
model: overrides the default model for that call.
background: true: returns a job_id immediately so Claude can keep working.
session_id: continues an earlier Codex thread, for example "make the icon darker".

codex_image also takes count, the number of images wanted. Set it for batches: it enables k/count progress and resumes that ask for exactly the missing images.

Let Codex write code (opt-in)

By default Codex can only read. If you want it to implement things while Claude reviews, name the one folder it may edit:

claude mcp add codex-bridge -e CODEX_BRIDGE_WRITE_ROOT=/path/to/your/project -- npx -y @xallindrome-labs/codex-bridge

Restart Claude Code and a fourth tool, codex_code, appears. Ask for it in plain words: *"Have Codex implement the plan in the background, then review its diff."*

One folder. cwd must be CODEX_BRIDGE_WRITE_ROOT or inside it. Anything else is refused, checked on real paths so .. and symlinks don't escape. A drive root or your home folder is refused as too broad.
No network, no commits. Codex runs with network access off and is told to leave changes uncommitted so you can see them in git diff. The no-commit rule is a prompt, not a sandbox rule.
Claude reviews. Every codex_code result ends with a reminder to read the diff before accepting it. A failed or cancelled run says Codex may have left partial edits.
Same job machinery. It survives restarts, background: true and codex_resume work the same way, and a resume re-checks the folder rule.
Temp files. In our test on Windows 11, writes outside the folder and network access were blocked, but the system temp folder stayed writable. Treat temp as writable. CODEX_BRIDGE_WRITE_ALLOW_TMP=1 stops asking Codex to block it.
Don't edit the same files yourself while a codex_code job runs.

Unset the variable and restart, and the tool is gone; codex_plan and codex_image are always read-only.

Codex jobs pane

An optional add-on that opens a pane beside the Claude Code chat listing your Codex jobs live: running, done, interrupted, with age, request and images k/n for batches. It also shows your Codex usage: the 5-hour and weekly windows, percent used, when each resets, and how many images were generated in each (Codex has one shared meter, so images use the same limits). It only reads the job files on disk, so it shows jobs from any session, including ones that kept running after you closed Claude. It also puts codex: N running in the status line and shows a toast when a job you watched finishes.

At the prompt of a terminal Claude Code session:

/plugin install codex-jobs --marketplace xallindrome-labs/codex-bridge

In the desktop app, where /plugin does not run: click + next to the prompt box, then Plugins, Add marketplace with xallindrome-labs/codex-bridge, then Add plugin. Without a marketplace, for one session: claude --plugin-dir "$(npx -y @xallindrome-labs/codex-bridge --pane-path)".

Then type /codex-jobs. It also opens by itself the first time a job is running in a session. Details and how it works are in plugins/codex-jobs. It needs a Claude Code build that supports mods; it is tested against the engine's own test kit, not every surface's paint.

How it compares

OpenAI's codex-plugin-cc is the official way to use Codex from Claude Code, and it's good at what it does: slash commands for review and rescue. codex-bridge is an MCP server instead, with a different focus: jobs that don't get lost, and images.

Several open issues in the plugin's tracker are about jobs getting lost, and codex-bridge is designed to avoid each of them. These come from reading the designs, not from a head-to-head test:

Reported in codex-plugin-cc	How codex-bridge handles it
Background job shows "running" forever after its worker dies (#704, #699)	Status is worked out from files on disk plus a heartbeat and a process check. A dead runner shows as `interrupted`, never "running", and `codex_resume` continues it.
Windows `cancel` silently fails (#708)	Cancel writes a marker file; the runner that owns the Codex process sees it within about 2 seconds and stops the process tree by calling `taskkill.exe` directly, with no shell in between.
Windows broker processes leak (#718, #782)	There is no shared broker. Each attempt is one runner process that exits when Codex does.
One session ending kills other sessions' jobs (#671)	Runners are started outside Claude's process tree (via WMI on Windows), so closing a session can't take them down.

What the plugin does that this doesn't: slash commands, and its review-gate and rescue workflows. And this one is newer, with far fewer users. If the plugin works for you, keep using it. If you've lost jobs, or want Codex to generate images that survive a crash, try this.

Jobs survive restarts

Every call is a job saved under ~/.codex-bridge/jobs/ /, including calls that aren't run in the background.

Claude closes or crashes: the job keeps running. server.mjs starts runner.mjs through WMI (Win32_Process.Create), so the job isn't part of Claude Code's process tree. Closing Claude can't kill it, and any later Claude session can collect it with codex_result.
The job itself dies (reboot, power loss, Codex crash, or killed process): the job is marked interrupted. The next Claude session is told about it when it starts. codex_resume continues it:

It copies out any images generated just before the interruption.
It resumes the same Codex thread: "N are already done, generate only the remaining ones."
If no Codex thread had started yet, it reruns the original request.

How images are collected

Codex never writes image files. Its image tool stores every generated image in ~/.codex/generated_images/ /. The runner checks that folder every 2 seconds and copies new images into output_dir as .png, -2.png, and so on, in the order they were made. copied.json in the job folder records what has been copied, so an image is never copied twice across attempts.

This gives three benefits:

Image jobs run in a read-only sandbox.
A crash loses at most the one image being generated.
Resume counts exactly what's done.

It also avoids a real problem: when Luna was allowed to save files itself, it re-typed each image as base64 through dozens of shell commands. That was slow, and the saved file no longer matched the original.

Codex stalls: the runner stops a run after 10 minutes with no output. The job is marked timed_out, and it can be resumed.

Each attempt keeps its own prompt.txt, events.jsonl (the Codex event stream), stderr.txt, heartbeat and result.json. Finished jobs are deleted after 14 days.

How it works

Each attempt runs codex exec --json (or codex exec resume ) with the prompt on stdin. No shell is involved.

Every call runs read-only, except codex_code when you have opted in (it runs workspace-write in your one folder, with network off). New sessions pass -s read-only plus -c sandbox_mode="read-only"; resumed sessions pass -c sandbox_mode="read-only" (codex exec resume takes no -s). Your Codex config may default to danger-full-access, but that default never applies to bridge calls. The plan smoke test checks that a write attempted from a resumed session fails.

File	Role
`server.mjs`	The MCP server. It creates jobs, launches runners, works out job status from the files on disk, and handles resume and cancel.
`runner.mjs`	Runs one attempt: starts Codex, records the heartbeat, watches for a stall or cancellation, collects images and writes `result.json`.
`lib.mjs`	Shared helpers: finding the Codex binary, building arguments, parsing events, handling images.

Install options

# for all your projects

claude mcp add -s user codex-bridge -- npx -y @xallindrome-labs/codex-bridge

or from a local checkout

claude mcp add codex-bridge -- node /path/to/codex-bridge/server.mjs

Remove it with claude mcp remove codex-bridge (add -s user if you installed it that way).

Configuration (env vars)

Var	Default
`CODEX_BIN`	Auto-detected. It prefers a `codex.exe` next to `codex-code-mode-host.exe`, which is currently `~/.codex/plugins/.plugin-appserver/codex.exe`.
`CODEX_BRIDGE_HOME`	`~/.codex-bridge`

| CODEX_BRIDGE_IDLE_TIMEOUT_MS | `600

Only the beginning is shown; read the rest in the repo

codex-bridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

OpenTakeoff

README from the maker

codex-bridge

Quickstart

Let Codex write code (opt-in)

Codex jobs pane

How it compares

Jobs survive restarts

How images are collected

How it works

Install options

or from a local checkout

Configuration (env vars)