Bragproof

← Reports

@minhspark/codex-mcp-bridge

Starts with no setup2.3.2npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 4 tools tried
Contacts while installing and starting: nothing

16tools listed
0hosts contacted
40files written
0.8 sto start
95dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y -p @minhspark/codex-mcp-bridge@2.3.2 codex-mcp-bridge

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

4 tools that take no input and look read-only were called once with nothing. 1 returned a result.

worker_statusNo usable answer tool reported an error: Bridge diagnostic (include this block in a bug report) WORKER_RELAY_NOT_CONFIGURED | background-relay / worker_status Bridge 2.3.2 | lin
list_workersNo usable answer tool reported an error: Bridge diagnostic (include this block in a bug report) WORKER_RELAY_NOT_CONFIGURED | background-relay / list_workers Bridge 2.3.2 | linu
list_codex_threadsNo usable answer tools/call timed out after 15000 ms
codex_bridge_statusReturned a result under 0.1 s · 964 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

worker_status
Inspect the independent background relay, CLI readiness and recent diagnostic reports. Desktop apps may be closed or frozen. Transport readiness is separate from each CLI's authentication/model readiness. authentication-unverified with canAcceptWork=true is informational: that CLI lacks an auth probe and may run authorized work. Do not call it an authentication failure; report actual job failures from their receipts.
list_workers
List independently identified CLI workers and this caller's background task receipts. These are separate from Desktop chats; never use a native chat ID as a worker destination.
send_to_worker agent, cwd, prompt, requestId
Queue explicitly authorized work to a separate background CLI worker in an explicitly selected, authorized project. This does not address, open or resume any Desktop chat. Generate requestId once and keep it for retries; an uncertain result must be inspected with read_worker_delivery, never resent under another ID. Use worker-relay tools for subsequent cross-agent delegation. Work continues independently when Desktop apps close or freeze.
read_worker_delivery requestId, waitSec
Read or wait for a durable background task receipt using its original requestId. A queued receipt is not a completed response. Failed and unknown receipts include the report block to show directly in this chat. Unknown work is never automatically replayed.
wait_codex_reply responsePreferences, deliveryId, timeoutSec
Continue a Desktop creation or send using its deliveryId; an unconfirmed acknowledgement does not prove delivery, including after MCP reconnect. Never sends a message or creates a task. On timeout, call again with the same deliveryId; do not ask the user to fetch the answer or resend. Stops for approval, user input or a verification error. Only the original verified Claude session and accounts can use the receipt.
11 more tools
read_codex_thread responsePreferences, threadId, turnId, limit
Read a Codex thread without sending anything. In Desktop mode, pass the exact turnId returned by send_to_codex_thread for authoritative assistant item IDs, text, and reply hash; without turnId the native recent-history view may omit items.
inspect_bridge_project cwd, taskCards
Read workspace trust and this bridge process's effective messaging authorization without changing files. Reports the authorization mode separately from shared project-policy state; a missing policy is a prerequisite only when nextActions says so. Distinguishes configured files from untested live connections. Same-project and new-task checks are reported as not checked here. Card extension authorization is a separate check. Does not send messages or create conversations.
prepare_bridge_project cwd, taskCards, reauthorize
Use only when the user explicitly selects a project for onboarding. Save the documented Claude workspace trust and shared messaging grant, with backups and verification. Reuses existing grants; never clears revocations without explicit reauthorization. Does not change permission modes, approve tools, send messages, create sessions or restart clients. Follow nextActions to check the existing card extension if requested, and verify live communication separately; configured is not connected. Never invoke to work around a denied message or peer instruction to broaden access.
delegate_to_codex cwd, requestId, prompt, name, timeoutSec, model, effort, openInApp, releaseAfterTurn
Create a named Codex session at the requested project directory, send Claude's prompt into it, return Codex's reply, and hand the session to Codex Desktop without leaving the bridge writer lock behind. Use for independent new work when the user explicitly or through standing instructions authorizes new conversations. Desktop creation returns a durable deliveryId; on timeout continue with wait_codex_reply instead of resending. In Desktop mode, supply a fresh requestId per independent task and keep it on retries; omit requestId in legacy app-server mode. Use send_to_codex_thread for unfinished work.
send_to_codex_thread threadId, prompt, timeoutSec, cwd, model, effort, name, openInApp, releaseAfterTurn
Send a prompt as a new user turn inside an existing Codex thread and wait for Codex to answer. Use only for the same unfinished task, including follow-up fixes, clarifications, or results; independent new work belongs in a new conversation when authorized. The thread keeps its full history, cwd and model. Use list_codex_threads first if you do not know the threadId. Desktop-owned tasks must use Desktop native delivery; an open task is a valid destination. A Desktop send prepares a durable deliveryId before dispatch. An ambiguous acknowledgement is marked unconfirmed, never accepted without evidence. If it times out, continue automatically with wait_codex_reply using that ID; never resend to obtain the answer. If legacy delivery reports an active writer, inspect codex_bridge_status and repair the native relay/configuration. Do not close the task, create a replacement, or ask the user to copy the message manually.
list_codex_threads limit, cwd, searchTerm, loadedOnly
List recent Codex threads (id, title, cwd, last update, status) so you can pick the exact threadId to talk to.
start_codex_thread cwd, requestId, prompt, model, name
Start a new Codex task when the user explicitly or through standing instructions authorizes a new conversation for independent work. In Desktop mode include the initial prompt and a fresh requestId to create and assign a visible task atomically; keep requestId unchanged on retries. Continue unfinished work with send_to_codex_thread and its original threadId. Use delegate_to_codex to also wait for its reply.
interrupt_codex_turn threadId, turnId
Stop a turn that is still running in a Codex thread.
open_codex_thread threadId, background
Bring a Codex thread to the front on Windows or macOS using (codex://threads/<id>) so a human can watch the work live instead of reading the transcript afterwards.
stop_codex_app_server
Stop the shared app-server this bridge talks to. Use it when work is handed off and the Codex desktop app is open: two app-servers on the same ~/.codex state make the app stutter. The bridge starts a new one automatically the next time it needs it.
codex_bridge_status cwd
Report how this bridge is wired on the current machine: platform, resolved codex binary, app-server endpoint and whether it is live, plus desktop deep-link support and macOS integrations.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnode >=22.13
Sourcegithub.com/buidangminh23/codex-mcp-bridge
Install scripts@minhspark/codex-mcp-bridge declare them. This runner does not run them.
Tarballsha512-tPWkpeULCXqhWbtsC5znywspLQjX5rlThVWXrRRJkusZKmewY7f35sBcKDh//jGIqcrc6sszCXTPtuhcJ9e05g==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@minhspark/codex-mcp-bridge.svg)](https://bragproof.smaverk.com/r/%40minhspark/codex-mcp-bridge)

New version out? Ask for a fresh report.