
Turn ChatGPT into a local agent runtime. Operate your computer, use local tools, discover MCP
Turn ChatGPT into a local agent runtime. Operate your computer, use local tools, discover MCP servers, and delegate work to your own models through one MCP connection.
·
English · 繁體中文
Build your own ChatGPT agent workflow — without building the agent runtime from scratch.
OpenChatX is a batteries-included, fully customizable local agent platform: coding-grade file and shell tools, computer control, MCP aggregation, Skills, Rules, Projects, Tasks, Subagents, cross-session Summaries, and more — all exposed through one official ChatGPT MCP connection, with Toolboxes to customize how your agent works.
[!IMPORTANT] OpenChatX runs through regular ChatGPT Chat. It does not consume your ChatGPT Work / Codex agentic allowance. If your Work or Codex allowance is exhausted, you can still use OpenChatX as long as your normal Chat usage is available.
[!CAUTION] OpenChatX runs with your local user permissions. A trusted ChatGPT caller can run commands, edit files, use connected MCP servers, and control supported applications.
OpenChatX uses OpenAI's documented MCP integration path. It does not reverse-engineer ChatGPT, call undocumented ChatGPT backend endpoints, reuse browser session cookies, or intercept ChatGPT traffic.
The connection works like this:
tunnel-client creates an outbound HTTPS connection to an OpenAI Secure MCP Tunnel. Your local MCP server does not need a public inbound port.ChatGPT remains the model and planner. OpenChatX is the local tool/runtime layer; it does not impersonate ChatGPT or make hidden model calls on ChatGPT's behalf.
The Runtime API key configured in OpenChatX is used for the official Secure MCP Tunnel control plane and is stored in the operating-system credential store. It is not a scraped ChatGPT credential or a workaround around ChatGPT's supported interfaces.
Official references:
This is the recommended way to use OpenChatX. You do not need to install Node.js, npm, PM2, or tunnel-client yourself.
Download the matching DMG from the latest release:
OpenChatX-macos-arm64.dmgOpenChatX-macos-x64.dmgThe macOS release is signed with Developer ID and notarized by Apple.
For most PCs, download:
OpenChatX-Setup-x64.exeFor Windows on ARM:
OpenChatX-Setup-arm64.exePortable ZIPs are also available.
[!WARNING] Windows may warn because the binary is unsigned. The Windows build is currently distributed without Authenticode signing. Download it only from this repository's GitHub Releases page.
Latest release:
https://github.com/XiaoPuOuO/openchatx-mcp/releases/latest
OpenChatX uses OpenAI Secure MCP Tunnel. The Desktop App manages the local runtime and bundled tunnel-client; you only need to create the tunnel once.
The Developer Mode toggle currently appears to be missing from ChatGPT. Some users have reported that they can create an MCP app without enabling Developer Mode, so for now, skip this step and continue directly with the Plugins flow below.
Then open Plugins, click +, choose Create app, and then choose Create MCP app.
Enter the app name and description, switch the connection type to Tunnel, and click Create tunnel.
Open the OpenAI Platform Tunnels page:
https://platform.openai.com/settings/organization/tunnels
Click Create tunnel, then configure:
OpenChatX Tunnel.OpenChatX Tunnel.After creation, copy the resulting tunnel_... ID. You will enter this in OpenChatX Desktop.
Open the OpenAI Platform API Keys page:
https://platform.openai.com/settings/organization/api-keys
Create a new secret key for the OpenChatX tunnel runtime. A name such as OpenChatX Runtime Key makes it easier to identify later.
Copy the secret when it is shown. Do not commit it to Git or paste it into chat.
Open OpenChatX Desktop → More → Connect Tunnel…
Enter:
tunnel_... ID from step 2.The Desktop App stores the API key in the operating-system credential store:
Return to ChatGPT:
openchatx (tunnel_...) tunnel.If you want ChatGPT to use OpenChatX tools without prompting for every tool call, you can set the OpenChatX app permission to Allow all tools.
Useful links:
| Feature | What it does |
|---|---|
| MCP Servers | Connect local or remote MCP servers behind one OpenChatX connection, sign in with OAuth when needed, and enable or disable individual tools |
| Runtime health | Check capability status, sign-in requirements, and memory usage from the Dashboard |
| Toolboxes | Add or manage custom TypeScript tools |
| Skills | Portable SKILL.md workflows, loaded only when needed |
| Rules | Persistent .mdc rules with Always / Auto Attached / Agent Requested / Manual modes |
| AGENTS.md | Editable start_here template with runtime placeholders |
| Projects | Bind work to a primary folder and optional additional folders, with workspace-scoped access |
| Goals & workflows | Track longer-running tasks and compose reusable capabilities |
| Summaries | Continue long-running work across fresh ChatGPT conversations with UUID handoffs |
| Subagents | Run independent, tool-using agents in parallel or nested sessions; follow their progress, guide them, and manage approvals |
| Model providers | Configure ChatGPT account access, Anthropic, Gemini, OpenAI, or OpenAI-compatible and local model endpoints |
| Permissions | Choose an access mode, review sensitive actions, and pause agent access when necessary |
| Mobile Dashboard | Use the responsive Dashboard on your phone, optionally through a private Tailscale connection |
| Capability Store | Install built-ins or inspect/install GitHub-hosted community capabilities |
| Dashboard | Manage ChatGPT and Subagent sessions, temporary Summaries, tools, Skills, Rules, MCP servers, Projects, and system status |
| Languages | English, Traditional Chinese, Japanese, Russian, and Vietnamese interface translations |
Subagents can work on separate tasks with their own conversation histories and access to the enabled OpenChatX tools. Delegate work synchronously or asynchronously, run independent jobs in parallel, or allow subagents to delegate further within configured limits. You can keep using the main chat while asynchronous work runs.
From Dashboard → Subagents, connect a supported provider, discover available models, and create model profiles. Options include ChatGPT account sign-in (when your account permits it), Anthropic, Gemini, OpenAI, and OpenAI-compatible APIs, including local model servers. Set each profile's reasoning controls and context/output limits where supported. Under Settings → Subagents, set the maximum delegation depth and number of children per agent.
Open Subagent Sessions to follow each session's messages and tool calls, send guidance while it runs, continue a finished session with new instructions, handle tool approvals, or delete a session and its descendants. Subagents follow the same OpenChatX access and approval boundaries as the parent agent.
You can use the responsive OpenChatX Dashboard from another device on your private Tailscale network without exposing the MCP endpoint to the public internet:
http://<TAILSCALE-IP>:8001/ui/ (replace 8001 if you changed the Runtime port).OpenChatX manages the internal proxy port and Tailscale Serve mapping automatically, including reconnect recovery. You do not need to configure a separate proxy port. Only /ui is forwarded; /mcp remains blocked. The Dashboard can perform administrative actions, so restrict which devices can reach it through your tailnet access policies. Tailscale is not installed or signed in by OpenChatX. See Tailscale mobile access.
Under Settings → Trust, choose Always Question (ask before tool actions), Allow Low Risk (allow low-risk actions and request approval for higher-risk ones), or Full Access (bypass ordinary approval boundaries; use only on a trusted computer). Approval requests can be approved once, allowed for an operation, or denied. You can pause agent access from the Dashboard and use Safe Mode to recover from problematic extensions. These OpenChatX controls are separate from ChatGPT's MCP app permission settings.
If your ChatGPT Pro account has access to Dots, ask your Dot to save the following as your working preferences when collaborating with OpenChatX. This configures Dot's behavior, not a separate OpenChatX Dot listener or tunnel; actual tool access still depends on your connected apps and permissions.
Communication
- Be concise and lead with the answer. Skip greetings and restating the question.
- Clearly distinguish verified information, inference, and unconfirmed details. Never present a guess as fact.
- Start with a summary; expand when details are useful. Avoid generic, overconfident, AI-sounding copy.
- Stay quiet when there is nothing to do or report. Describe progress accurately.
Working style
- After receiving an assignment, continue working toward completion. A progress update does not mean the work is finished; do not wait to be reminded.
- When one part is blocked, continue independent work. Do not duplicate work that another agent is doing or has completed.
- Focus on the requested outcome and use sufficient direct verification. Avoid repeated investigations, audits, and endless confirmation loops.
- Do not create unnecessary backups, parallel versions, temporary scripts, or reports. Preserve necessary results and safely clean up your temporary files.
- Make changes only when they offer a concrete benefit; do not create changes simply to appear busy.
Tools
- Unless explicitly requested, do not switch to Work mode. Prefer creating your own parallel subagents and letting them use OpenChatX capabilities; minimize direct OpenChatX use.
- Parallel subagents are allowed when responsibilities are separated and their work cannot overwrite one another. Report whether they are actually running.
Other
- Work on multiple projects concurrently without letting them block one another. Never push, merge, deploy, or use real customer data without explicit authorization.Remote MCP connections can use OAuth when the server requires sign-in. OpenChatX surfaces an authorization prompt and connection status in the MCP management UI, and stores OAuth credentials in the OS secure store instead of the MCP configuration. The Dashboard also distinguishes authentication-required services from runtime failures.
External MCP and Toolbox schemas stay lazy so the normal ChatGPT tool context stays small.
A key OpenChatX differentiator is that long-running Agent work can survive the ChatGPT conversation itself. When a chat eventually hits practical context limits, OpenChatX provides a handoff layer instead of forcing you to reconstruct the task manually.
When the Agent calls summarize, it stores two parts locally:
OpenChatX returns a UUID. Start a fresh ChatGPT conversation, give the Agent that UUID, and summarize returns the stored summary plus recent context. The handoff is then deleted automatically.
Temporary summaries can also be viewed, created, edited, copied, or deleted from the Dashboard.
Skills are portable Agent Skills owned by a Toolbox:
toolboxes/<toolbox>/skills/<name>/SKILL.mdA Skill contains name, description, and Markdown instructions. Skills are not injected at startup.
skill_search finds up to five relevant Skills by name/description; use action=load with an exact Skill name to load its full Markdown.skill_manage creates, edits, or deletes user Skills.Rules are owned by a Toolbox and live beside that Toolbox's other capabilities:
toolboxes/<toolbox>/rules/<name>.mdcExample:
---
description: "React component conventions"
globs:
- "src/**/*.tsx"
alwaysApply: false
---
Use accessible labels and named exports.OpenChatX supports four Rule modes:
start_here.Rules can be imported/exported with Cursor .mdc, Claude Rules, and AGENTS.md.
~/.openchatx-mcp/AGENTS.md is the editable template used by start_here.
The Toolbox UI exposes it directly. Runtime data is inserted through placeholders such as:
{{MODE_INSTRUCTIONS}}{{PROJECT_CONTEXT}}{{CAPABILITY_CATALOG}}{{ALWAYS_RULES}}Move or remove placeholders to control what start_here returns.
You can usually just ask ChatGPT:
Add this MCP server to OpenChatX and verify it works.
or:
Create an OpenChatX tool that starts my local service and returns its status.
OpenChatX can manage MCP servers, Toolboxes, Skills, Rules, Projects, and Subagents from the Dashboard or through its management tools.
Use this only if you do not want the Desktop App.
tunnel-clientbrew install ripgrep
git clone https://github.com/XiaoPuOuO/openchatx-mcp.git
cd openchatx-mcp
npm ci
npm run setup -- --config-onlywinget install BurntSushi.ripgrep.MSVC
git clone https://github.com/XiaoPuOuO/openchatx-mcp.git
Set-Location openchatx-mcp
npm ci
npm run setup -- --config-onlyThen install the official OpenAI tunnel-client, create the openchatx tunnel profile, export CONTROL_PLANE_API_KEY, and run:
npm run setup
npm startUseful commands:
| Command | Purpose |
|---|---|
npm run status | Show runtime/tunnel status |
npm run logs | Show runtime logs |
npm run print-url | Print local MCP/UI/tunnel URLs |
npm run restart | Rebuild and reload services |
npm run stop | Stop managed services |
npm run auth:reset | Clear the bound ChatGPT subject |
npm ci
npm --prefix ui ci
npm run lint
npm run typecheck
npm test
npm run build
npm --prefix ui run buildDesktop build commands:
npm run desktop:build
npm run desktop:smoke
npm run desktop:windows:build
npm run desktop:windows:build:arm64Maintainer docs: wiki/
MIT — see LICENSE.
Parts of this project are derived from Shellby MCP; see THIRD_PARTY_NOTICES.md.
This repo does not document an install step we could read. Check the README on GitHub.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/openchatx-mcp to learn what the "Openchatx Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server doesn't publish a machine-readable tool manifest, and it doesn't expose a public endpoint we could ask. Connect the server locally to see what it exposes.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Paste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/openchatx-mcp)Nothing comparable is listed yet.
v1.3.0OpenChatX v1.3.0Release notesv1.2.0OpenChatX v1.2.0Release notesv1.1.2OpenChatX v1.1.2Release notesv1.1.1OpenChatX v1.1.1Release notesv1.1.0OpenChatX v1.1.0Release notesv1.0.1-beta.1OpenChatX v1.0.1-beta.1Release notesv1.0.0-beta.3OpenChatX v1.0.0-beta.3Release notesv1.0.0-beta.2OpenChatX v1.0.0-beta.2Release notesv1.0.0-beta.1OpenChatX v1.0.0-beta.1Release notesv0.5.3OpenChatX v0.5.3Release notesv0.5.2OpenChatX v0.5.2Release notesv0.5.1OpenChatX v0.5.1Release notesv0.5.0OpenChatX v0.5.0Release notesv0.4.0OpenChatX v0.4.0Release notesv0.3.0OpenChatX v0.3.0Release notesv0.2.0OpenChatX v0.2.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "openchatx-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.