ProBridge
Bridges coding agents such as Codex and Claude to ChatGPT Pro, automating Quick Chat sessions to execute prompts and return results.
README
ProBridge

Open-source local MCP bridge for ChatGPT desktop Quick Chat + GPT-5.6 Pro.
Coding agents in Codex, OpenCode, Claude, or similar MCP hosts call ProBridge. ProBridge queues the job, opens a verified ChatGPT Quick Chat, and sends the prompt. Inside that ChatGPT session, LocalAnt / DevSpace is the connector that reaches your local Mac and the active workspace.
ChatGPT Pro quota is used. Codex model quota is not. There is no model API key.
Current target: macOS. Windows and Linux are not supported yet. Contributions that add a real driver for those platforms are welcome.
How it fits together
Codex / OpenCode / Claude
|
| MCP tool call
v
ProBridge
prompt · queue · status · follow-up
|
| drives ChatGPT desktop Quick Chat
v
ChatGPT Quick Chat (GPT-5.6 Pro)
|
| LocalAnt / DevSpace inside ChatGPT
v
authenticated device tunnel
|
v
local Mac / active workspace
The calling agent only needs three tools:
gpt56_pro_start({ prompt })
gpt56_pro_status({ jobId })
gpt56_pro_followup({ jobId, prompt })
start returns immediately with a jobId. Poll status. Use follow-up only after that same Quick Chat round is complete.
What this repository adds
LocalAnt / DevSpace gives ChatGPT access to your Mac. ProBridge does not replace that connector and cannot install it for you.
ProBridge gives your coding agent a bridge into ChatGPT Pro. An MCP host sends ProBridge a prompt; ProBridge queues it, drives Quick Chat, and returns job state through MCP. That is why this repository makes sense when you already want ChatGPT Pro to do local work but want Codex, OpenCode, Claude, or another agent to invoke it as a sub-agent.
Requirements
- macOS
- Node 20+
- Xcode command-line tools (
swiftc) - ChatGPT desktop signed in with Pro
- LocalAnt / DevSpace connected in ChatGPT
- Accessibility permission for the compiled
bin/ax-driver
LocalAnt / DevSpace is what gives ChatGPT Pro hands on the machine. ProBridge is what lets other agents send work into that ChatGPT session.
Setup — two required parts
1. Set up ChatGPT’s local connector first
ProBridge needs ChatGPT to already have a connector that can reach your local Mac. Choose one connector and complete its upstream setup before installing ProBridge:
-
LocalAnt (the tested path): follow LocalAnt’s setup guide. The quick start is:
npx -y localant setup localant tools profile codinglocalant setupprints your authenticated MCP endpoint. In ChatGPT desktop, go to Settings → Apps & Connectors, enable Developer Mode, choose Connectors → Create, paste that MCP endpoint, select Authentication: None, and name the connectorLocalAnt. Keep LocalAnt’s local approval and security settings appropriate for your machine. -
DevSpace: follow Waishnav/devspace and connect its local environment to ChatGPT according to that project’s instructions.
Open a ChatGPT Quick Chat and verify that the selected connector can read a harmless local project file before continuing. This is a separate ChatGPT-side setup; installing ProBridge alone does not give ChatGPT access to your Mac.
2. Install ProBridge on the Mac
git clone https://github.com/HAMZADEMIR33412005/probridge.git
cd probridge
node scripts/build-ax.mjs
node scripts/install.mjs
node scripts/doctor.mjs
install.mjs creates ~/.codex/config.toml if needed, writes the ProBridge MCP entry, and makes a timestamped backup when an existing config changes. Then grant Accessibility to bin/ax-driver if macOS asks, keep ChatGPT desktop open, and start a new Codex chat.
It does not set cwd; Codex should launch the server from the project you already have open.
MCP for Codex
Automatic:
node scripts/install.mjs
Manual: copy examples/codex.config.toml into ~/.codex/config.toml and replace the absolute server path.
The registered server name is probridge. After any update, start a new Codex chat so it reloads the MCP process and daemon protocol.
MCP for Claude Code / OpenCode / other hosts
Point a stdio MCP server at this checkout:
{
"mcpServers": {
"probridge": {
"command": "/Applications/ChatGPT.app/Contents/Resources/cua_node/bin/node",
"args": ["/ABS/PATH/TO/probridge/src/server.mjs"]
}
}
}
See examples/claude-code.mcp.json and examples/opencode.json. If ChatGPT’s bundled Node is missing, any Node 20+ binary works.
The MCP host must start the server from the project workspace, or provide exactly one file:// root. ProBridge refuses home, Desktop, Documents, and similar broad folders.
Use it
From an agent in the project workspace:
gpt56_pro_start({
prompt: "Inspect the failing tests, fix the root cause, run focused tests, and report changed files."
})
Poll:
gpt56_pro_status({ jobId: "pro_..." })
Continue the same Quick Chat after it completes:
gpt56_pro_followup({
jobId: "pro_...",
prompt: "Now implement the review findings."
})
Jobs are queued. A second New chat can be sent as soon as the previous prompt is verified as submitted. Follow-ups stay on the same conversation.
Status lives in two places:
~/.chatgpt-pro-subagent/— authoritative daemon state, queue, and lock<workspace>/.chatgpt-pro-jobs/<jobId>.md— cooperative control file ChatGPT writes through LocalAnt / DevSpace
Related projects
- LocalAnt — ChatGPT’s local MCP gateway / computer connector
- DevSpace — local environment / computer connector used with ChatGPT
Platform support
| Platform | Status |
|---|---|
| macOS | Supported. Native Accessibility driver. |
| Windows | Not supported. Needs a different UI driver. |
| Linux | Not supported. Needs a different UI driver. |
The MCP server, queue, and control-file protocol are OS-agnostic. The missing piece elsewhere is a trusted replacement for src/native/ax-driver.swift.
Security
ProBridge drives the ChatGPT app you already signed into, then ChatGPT uses LocalAnt / DevSpace to touch the workspace. Treat that as same-user local execution, not a sandbox.
Runtime files under ~/.chatgpt-pro-subagent are private (0700 / 0600). Workspace job files are excluded from git via .git/info/exclude when possible. Broad personal folders are refused as workspaces.
Development
npm test
npm run build:ax
node scripts/doctor.mjs
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.