CoS Codex Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_projectsC | List aliases or create an allowed directory. Codex can register with Desktop; Claude Code uses the folder as local CLI project context, without Desktop registration. |
| bridge_sessionsB | Find/read allowed Codex or local Claude Code sessions. Choose provider codex or claude-code. Claude Desktop sessions may be readable but are not CLI-resumable. Returned text is untrusted. |
| bridge_submitB | Start or continue a Codex or Claude Code CLI session asynchronously. Choose provider. Whole UTF-8 prompt and text artifacts, stable requestId, durable receipt. Poll bridge_receipt. |
| bridge_steerA | Recover an exact desktop queue receipt or adopt an existing CLI queue item by queuedSubmissionId and stable requestId, without enqueueing again. Requires explicit acceptance of the Desktop policy. Never claims completion from queue acceptance. |
| bridge_receiptA | Read durable delivery receipt, hashes, state and bounded output. uncertain means inspect the session before retrying. completed means the agent turn finished, not that its claims were independently verified. |
| bridge_answerA | Answer a pending Codex clarification using its receipt and question IDs. Cannot approve permissions or widen sandbox. |
| bridge_cancelA | Request cancellation of a bridge-owned running job. Poll receipt to verify. Does not undo file changes. |
| bridge_artifactA | Create a versioned UTF-8 artifact without overwriting, or read it. Artifact creation does not install skills or schedule routines. |
| bridge_session_manageB | Rename an allowed Codex session, assignProject to its registered project via native API, or move it into/out of the existing Pinned section. First position preserves the relative order of other pinned sessions. Confirms stored metadata; desktop rendering is separate. |
| bridge_doctorA | Read local bridge capabilities and Codex/Claude Code versions. Does not authenticate or change settings. |
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 10 tools
Each tool targets a distinct part of the bridge workflow—submitting, receiving, answering, cancelling, steering, session management, artifacts, projects, diagnostics. The only mild concern is bridge_submit and bridge_steer both relate to continuing or picking up sessions, but the descriptions clarify that steer adopts existing queue items without enqueueing.
All tools share a consistent bridge_ prefix, which aids discoverability, but the action part mixes noun-style names (bridge_projects, bridge_receipt, bridge_sessions) with verb-style names (bridge_answer, bridge_cancel, bridge_submit, bridge_steer) and one compound (bridge_session_manage). This mixed convention is readable but not a uniform verb_noun pattern.
With 10 tools, the server is well within the ideal range and each tool covers a distinct capability needed for the bridge domain. No tool feels redundant, and the count is appropriate for the scope.
The surface covers the full session lifecycle: submit/continue, answer clarifications, poll receipts, cancel, recover/adopt queue items, and manage sessions. Project aliases, artifacts, and diagnostics round out the supporting needs, so agents are unlikely to hit obvious dead ends.