claude-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 | {} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_modelsA | List available Codex models. Pass nextCursor as cursor for another page. |
| codex_startA | Start a live Codex agent and return its threadId immediately after acceptance. Codex runs with full filesystem/network access and no approval prompts. Supply an absolute working directory and the complete task context; model and serviceTier (for example "fast") are optional. |
| codex_messageA | Send direction to a running Codex turn, or start another turn in the same thread if it is idle. A race with turn completion can return an error: inspect status before retrying. |
| codex_stopA | Request interruption of a running Codex turn. The interrupted event confirms completion; this does not undo changes already made. |
| codex_resumeA | Attach a saved Codex thread after reconnecting. Use codex_message to continue its work. |
| codex_answerB | Answer a Codex question using its requestId and all question IDs. Ask the user when the answer requires their preference; otherwise answer from the task context. |
| codex_statusA | Read session state, pending questions and the latest answer. Omit threadId to list sessions. Does not wait for completion. |
| codex_eventsA | Read the bounded event journal after a sequence number. gap means older events were evicted. Use to recover results if channel delivery is unavailable; do not busy-poll. |
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 8 tools
Each tool targets a distinct lifecycle operation: start (new thread), resume (reattach saved thread), message (continue/idle turn), stop (interrupt), status, events, answer, and models. The main overlap risk is between codex_status and codex_events, both of which read state, but descriptions differentiate session state vs. event journal.
Every tool uses the codex_ prefix with a clear snake_case verb/noun form (codex_start, codex_message, codex_events, codex_stop). The pattern is uniform and highly predictable.
Eight tools is well-scoped for an agent-bridge server covering session lifecycle, messaging, event retrieval, and model listing. Each tool appears to earn its place without redundancy.
The surface covers the full lifecycle: start, resume, message, stop, status, events, answer, and models. Minor gaps exist, such as explicit session teardown/cleanup or listing historical threads beyond resume, but core workflows are covered.