Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_BRIDGE_HOMENoSet 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 text into a chat and press Enter. chat: id or exact title of an existing chat. Or leave chat empty to start a new chat: in project (a project name from list_projects, or any folder path; Codex gets a project made for a new folder), or with no folder when project is empty too. codex / claude_code are driven through the desktop app; a split Claude window is fine (a chat already on screen is used in place, otherwise it opens in the focused pane). The view returns to the chats the user was on. claude_cli runs claude -p --resume headless with permission_mode. Returns a job_id. When the answer is ready it is saved; if you are a desktop chat it is also typed into your chat (notify_caller). Otherwise call wait_reply(job_id).

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 objective, presses Save). Changes are checked against Codex's goal store.

codex_generate_imageA

Ask Codex (new chat in project) to make an image with its image_gen tool, wait, and copy the result(s) into dest_dir. Returns the copied file paths; open them with your image viewer/Read tool.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues