codex-bridge

Name: codex-bridge
Author: xallindrome-labs

de xallindrome-labsversión 0.1.0i★ –iSe ejecuta en tu computadora

Nombre en el registroio.github.xallindrome-labs/codex-bridge

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en tu computadora
Transporte: stdio
Categoría: Otros

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 1 de 1 superadas
Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
Debes completar tú: 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

Necesitas

npmNode.js instalado (para el comando npx)

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
      }
    }
  }
}

Ejecuta esto en tu 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

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "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"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

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

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub xallindrome-labs, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
– No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
– No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
… Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 32683 servidores de esta categoría
Publicado en el registro más recientemente que el 71% de los otros 32683 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 32683 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro codex-bridge?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro hace 15 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

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

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses

Instalar

Remote Desktop Commander

de desktop-commander

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

Se ejecuta en la nube★ 211Actualizado anteayer

Instalar

MCP Server Autocad Lisp Helper

de radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

Se ejecuta en tu computadoraActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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

Solo se muestra el principio; lee el resto en el repo

codex-bridge

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

MCP Server Autocad Lisp Helper

README del creador

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)