Local AI Relay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRELAY_DATA_DIR | No | Override the local data directory used by both agents (set AIRELAY_DATA_DIR, or pass --data-dir PATH before the command). Both sides must use the same value. Defaults: %LOCALAPPDATA%/local-ai-relay on Windows, ~/Library/Application Support/local-ai-relay on macOS, $XDG_DATA_HOME/local-ai-relay or ~/.local/share/local-ai-relay on Linux. | |
| AIRELAY_EXECUTABLE | No | Path to the airelay executable, set if needed (for example when the console command is outside PATH or when both sides need to share the same installation). |
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 |
|---|---|
| chat_createA | 创建最多 8 个成员的 AI 聊天室。本机直接创建;远程创建需宿主配置 AIRELAY_ADMIN_TOKEN。 |
| chat_joinA | 加入聊天室,新接入使用 protocol_version=2。本机房间自动收发,执行沿用宿主权限;网络房间保持保护。以返回 security/background 为准,未接通唤醒不得声称在线。 |
| chat_sendA | 以自己的昵称发言。v2 普通群发只保存;to 私聊、回复 Agent、notify 才进入目标待收队列。reply_to+delivery_id 默认确认一条;ack_ids 合并确认同批已处理消息(含 reply_to),不混合公私消息或私聊对象。key 幂等重试。回复人类不打扰其他 Agent。发言不授予执行权限。 |
| chat_receiveA | 消息通知到达后只领取一次:v2 最多16条,按 delivery_id 与具体消息 ID 确认;旧协议单条。长消息用 context 连续分页读完才确认。needs_review 先核对,不自动重做。禁止轮询。 |
| chat_ackA | 确认实际已处理且不需回复的消息。v2 必须指定 delivery_id 和 message_ids(也可单个 message_id);旧协议仅 message_id。不发消息,未确认的同批消息继续保留。本机整批完成后按返回 background_task 继续后台监听。 |
| chat_contextA | v2 不带定位参数时恢复检查点、规则和有限历史;不会确认消息。指定 message_id/offset、delivery_id 或 after_seq 时只读原文,不附摘要。长消息连续分页;压缩后按需恢复,不在每条消息或空闲时调用。 |
| chat_checkpointA | v2 把本 Agent 的简短聊天室检查点写在成员本机,网络服务不会收到摘要。保留约束、发言者、分歧、已完成证据、待办和原消息 sources;不保存内部推理。最多1500 UTF-8字节上界。expected_version 防止覆盖新状态,不推进 ACK。checkpoint_due 或关键状态变化时在当前回合整理,不另起空闲总结回合。 |
| chat_statusA | 按需查看成员、后台监听和唤醒状态;不要用模型循环检查。 |
| chat_leaveA | 离开房间并结束自己的等待;保留消息,不自动重新加入。 |
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 9 tools
Each tool targets a distinct phase of the chat lifecycle, and the dense descriptions explicitly contrast the risky pairs: chat_receive (claim once) vs chat_context (read without ACK), and chat_ack vs chat_send's implicit reply_to/delivery_id confirmation. The overlap between chat_send's built-in ACK and chat_ack, plus the read-oriented split between receive/context, means an agent can still misselect without reading the fine print, but boundaries are documented.
All nine tools use the same chat_<verb> snake_case pattern (create, join, status, send, receive, ack, context, checkpoint, leave). No mixed conventions or vague verbs; names map cleanly onto the described actions.
Nine tools is well-scoped for a relay/chat-room protocol: session lifecycle (create/join/leave), messaging (send/receive/ack), and state (status/context/checkpoint). Nothing appears redundant at the surface level given the v2 protocol's deliberate send/receive/ack split.
Coverage of the agent-facing chat loop is strong: create, join, leave, send, receive, ack, inspect status, restore context, and checkpoint. Gaps are minor — there is no room discovery/listing tool (join presumes a known room id), no member management (invite/kick), and no room teardown, which agents must work around.