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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。