agent-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_BRIDGE_HOME | No | Set this to move the directory where replies are stored. By default, replies are stored in ~/.agent-bridge/jobs/. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List projects (folders) for app = 'codex', 'claude_code' or 'claude_cli', most recently active first. |
| list_chatsC | List chats in a project (name or path from list_projects), newest first. codex chats show their goal status; claude chats show busy / idle / closed. |
| read_chatB | Read the last messages of a chat (id or exact title): what was asked and each turn's final answer. |
| send_messageA | Send |
| wait_replyA | Wait until the chat behind job_id has answered (or timeout_s passes) and return the job with its reply. |
| codex_goalB | Read or steer the goal of a Codex chat (id or exact title).
action: 'get' | 'pause' (the stop button) | 'resume' (the start button) | 'edit' (opens Edit goal, replaces the
objective with |
| codex_generate_imageA | Ask Codex (new chat in |
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 7 tools
Each tool has a distinct resource+action: list_projects vs list_chats vs read_chat are clearly layered by scope, and send_message/wait_reply form a complementary pair rather than overlapping. codex_goal and codex_generate_image are Codex-specific but clearly named, though a few tools (read_chat vs list_chats) require reading descriptions to fully separate.
Most tools follow a consistent verb_noun pattern (list_projects, list_chats, read_chat, send_message, wait_reply). The codex_* prefix on codex_goal and codex_generate_image is a sensible namespace convention rather than a break, giving mostly consistent naming.
7 tools is well-scoped for an agent-bridge: it covers discovery, messaging, waiting, and two Codex-specific extras without bloat. Each tool earns its place in the bridging workflow.
Core lifecycle is covered: list projects/chats, read, send, wait for reply, plus goal control and image generation. Creation is implicitly handled by send_message with an empty chat, but there is no explicit project creation, chat deletion/close, or job cancellation—minor gaps agents can mostly work around.