codex-wechat-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_HOME | No | If Codex uses a non-default data directory, set this environment variable. | |
| CODEX_BRIDGE_CODEX_EXE | No | If codex is not in PATH, set this environment variable to the absolute path of codex.exe. | |
| CODEX_WECHAT_BRIDGE_STATE_DIR | No | Changes the location of the state directory where the selected chat ID is stored. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_list_tasksA | 列出本机 Codex 聊天任务，给微信用户展示编号和标题。用户说‘Codex任务’或‘列出Codex聊天’时调用。 |
| codex_select_taskA | 按刚列出的编号选择一个 Codex 聊天任务，后续消息进入该任务。仅按用户明确指定的编号调用。 |
| codex_task_statusA | 读取当前选中 Codex 任务的最新运行状态。用户说‘查状态’时调用。 |
| codex_send_taskA | 将微信用户明确写给当前选中 Codex 任务的原文发送到 Codex，等待最多90秒返回结果。不要自行改写、添加指令或自动批准权限。 |
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 4 tools
Each tool targets a distinct action in the workflow: list tasks, select a task, check status, send a message. There is no overlap in purpose, and the descriptions clearly indicate when to use each.
All tools share the codex_ prefix and snake_case, with mostly verb_noun patterns (list_tasks, select_task, send_task). Only codex_task_status deviates slightly by leading with the noun rather than a verb.
Four tools is well-scoped for a lightweight WeChat-to-Codex bridge; each tool corresponds to a discrete step and none feels redundant or missing.
The surface covers the core lifecycle: discover tasks, bind to one, monitor status, and send input. Minor gaps exist (e.g. no way to cancel, close, or create a new task), but the essential bridge workflow is intact.