duplex-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DUPLEX_CODEX_BIN | No | Absolute path for non-standard installs of the Codex CLI. | codex |
| DUPLEX_HTTP_PORT | No | HTTP server port, always bound to 127.0.0.1. | 8787 |
| DUPLEX_STATE_DIR | No | Directory for conversation ledger and thread metadata. | ~/.duplex-bridge |
| DUPLEX_WORKSPACE | No | Root the two agents work on. Fixed at startup: the MCP caller cannot change it. Defaults to the process current working directory. | process cwd |
| DUPLEX_CLAUDE_BIN | No | Absolute path for non-standard installs of the Claude CLI. | claude |
| DUPLEX_BEARER_TOKEN | No | Required by the HTTP server. Minimum 32 characters. Used for authenticating requests from ChatGPT. | |
| DUPLEX_ALLOW_API_KEYS | No | Set to '1' to let API keys through to the child process, deliberately choosing the pay-per-token path. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_chatgptA | Interpella un agente ChatGPT su questo repository e restituisce la sua risposta. Non può modificare file. Adatto a revisioni, secondi pareri, analisi. ChatGPT vede questo repository su disco, quindi cita i file per percorso. Il contesto della conversazione viene ricostruito dal bridge: non serve incollarlo. |
| ask_chatgpt_writeA | Chiede a ChatGPT di modificare file in questo repository (fix, refactor, nuovo codice). PUÒ scrivere su disco. ChatGPT vede questo repository su disco, quindi cita i file per percorso. Il contesto della conversazione viene ricostruito dal bridge: non serve incollarlo. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly differentiated by capability: one is read-only for analysis and review, the other can write files. The names and descriptions explicitly state this distinction, leaving no ambiguity about which to invoke.
Both tools follow the exact same 'ask_chatgpt' prefix, with '_write' appended to denote the mutating variant. This is a clean, consistent naming pattern.
With only 2 tools, the surface is thin. For a specialized bridge between an agent and ChatGPT on a repository, the read/write pair is a minimal but functional set, yet it feels slightly under-scoped for a general-purpose bridge.
The core lifecycle of 'ask ChatGPT' and 'ask ChatGPT to modify files' is covered. There may be missing auxiliary operations (e.g., conversation history, tool configuration), but for the stated purpose the basic read/write coverage is sufficient with minor gaps.