pi-subagent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PI_BIN | No | Pi executable override. | |
| PI_SUBAGENT_VIEWER | No | Set to 'off' to disable Run Windows. | |
| PI_SUBAGENT_REGISTRY | No | Session metadata; defaults to ~/.pi-subagent/registry.json. | |
| PI_SUBAGENT_POWERSHELL | No | Viewer executable; defaults to powershell.exe. | |
| PI_SUBAGENT_TRANSCRIPTS | No | Full transcripts; defaults to ~/.pi-subagent/runs. | |
| PI_SUBAGENT_VIEWER_SCRIPT | No | Override viewer/run-window.ps1. |
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 |
|---|---|
| pi_delegateC | 委派任务给 Pi 子代理（默认 async） |
| pi_statusC | 取 run 结果（long-poll）；openWindow 可重开该 Run 的只读窗口 |
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 2 tools
The two tools have clearly distinct purposes: pi_delegate initiates a task delegation, while pi_status retrieves the result of a run. There is no overlap or ambiguity between them.
Both tools follow a consistent pi_ prefix and use a verb_noun pattern (delegate, status). The naming is predictable, though the set is too small to fully demonstrate a broader convention.
Two tools is on the thin side for a subagent delegation server, but it may be sufficient for a minimal async task lifecycle. The count is borderline but not unreasonable.
The pair covers the basic delegate-and-poll lifecycle, but there is no explicit cancel, list, or error-handling tool. Agents can work around this by waiting for status, but the surface feels minimal.