codex-subagent-for-claude
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_SUB_BIN | No | Path to the Codex binary. Default: auto-detected. | auto-detected |
| CODEX_SUB_MODEL | No | Default model for subagents. Default: gpt-6-sol. | gpt-6-sol |
| CODEX_SUB_EFFORT | No | Default reasoning effort for subagents. Default: high. | high |
| CODEX_SUB_SANDBOX | No | Sandbox mode for subagents. Default: danger-full-access. | danger-full-access |
| CODEX_SUB_STATE_DIR | No | Directory for logs and session state. Server and hook must use the same value. Default: %LOCALAPPDATA%\codex-sub. | %LOCALAPPDATA%\codex-sub |
| CODEX_SUB_SERVICE_TIER | No | Default service tier for subagents. Default: default. | default |
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 |
|---|---|
| codex_spawnA | 把一个任务派给 Codex 子代理,立即返回 8 位任务 id(wait_s>0 时先等一会儿,等到就直接给结果)。可以连续派多个,它们在同一个常驻 Codex 进程里并行执行。任务完成后结果会自动送回本会话;也可以用 codex_wait 主动等、codex_status 看进度、codex_steer 中途改方向、codex_interrupt 中断。传 thread_id 可在旧任务的上下文上续问;该 thread 上不能有仍在运行的任务。默认无沙箱、不审批:Codex 会直接改文件、跑命令。 |
| codex_reviewA | 用 Codex 内置的代码审查模式(等价于 |
| codex_waitA | 阻塞等待一个或多个任务结束并返回它们的结果。不传 ids 就等本会话全部运行中的任务。超时只是返回当前状态,任务不会被杀,可以再次调用继续等。已结束的任务立即返回。等待期间每 10 秒发一次进度通知。只想看一眼不想等,用 codex_status。 |
| codex_statusA | 立即返回,不等待。不传 ids:一行一个列出本会话全部任务及状态。传 ids:看详情——运行中的显示最近动作、改动文件、输出预览;已结束的显示完整结果(超过 6000 字截断,full=true 看全文)。被 codex_interrupt 中断的任务,其已产出的部分也从这里取。 |
| codex_steerA | 给一个正在运行的任务追加或修正指令,Codex 在当前步骤结束后转向,不用重来,已做的工作保留。只对运行中的任务有效;任务已结束时报错,此时应改用 codex_spawn(thread_id=...) 续问。想让它停下来而不是转向,用 codex_interrupt。 |
| codex_interruptA | 中断一个正在运行的任务:Codex 收到后立即停止,已完成的部分输出和文件改动保留,任务状态变为 interrupted,结果可用 codex_status 查看。对已结束的任务调用无副作用,直接返回其结果。被中断的 thread 之后仍可用 codex_spawn(thread_id=...) 续问。只想改方向不想停,用 codex_steer。 |
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 6 tools
Each tool targets a distinct lifecycle action (spawn, status, wait, steer, interrupt, review), and descriptions actively disambiguate near-neighbors by naming the alternative ('只想看一眼不想等,用 codex_status'). The main residual overlap is codex_status vs codex_wait, since both return task results, though the blocking-immediate distinction is explained.
All six tools follow a uniform codex_<action> snake_case pattern (spawn, wait, status, steer, interrupt, review). Verbs are consistent and predictable throughout.
Six tools is well-scoped for a subagent-management server, covering spawn, monitoring, control, and review. Every tool earns its place with no redundant additions.
The surface covers the full task lifecycle: dispatch (spawn), monitor (status/wait), control (steer/interrupt), and review, plus thread continuation via thread_id. Minor gap: no explicit tool to enumerate historical/prior threads beyond session-scoped status.