qoder-as-subagent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QODER_BIN | No | Pin an exact CLI build. | resolved as above |
| QODER_AS_SUBAGENT_STATE_DIR | No | Where job state lives. Deliberately outside any workspace, and separate from cc-as-subagent's. | %LOCALAPPDATA%\qoder-as-subagent |
| QODER_AS_SUBAGENT_PASSTHROUGH | No | Comma-separated variable names to pass through. Everything else is dropped. | |
| QODER_AS_SUBAGENT_WORKSPACE_ROOTS | No | Path-delimiter-separated allowlist. A workspace outside every root is refused. | the server's own cwd |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Liveness check. Reports the server version and the workspace roots it will accept. Never spawns the Qoder CLI. |
| qoder_runA | Start a new Claude Code session in a workspace. Returns a jobId immediately; the run continues in the background. Use qoder_status to poll for the result. Tier "consult" is read-only; "execute" may edit files in the workspace. |
| qoder_statusA | Poll a job for progress and its result. Pass the cursor from the previous call to receive only new events. Returns the final answer once the run completes. |
| qoder_replyA | Start a follow-up turn in an existing session. Takes the jobId of a finished job — the session id stays server-side. Returns a new jobId for the follow-up. |
| qoder_cancelA | Stop a running job and the process tree it started. |
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 5 tools
Each tool covers a distinct lifecycle action: liveness, start, poll, cancel, and follow-up. The descriptions make the boundaries clear, especially qoder_run (new session) vs qoder_reply (existing session).
The four main tools follow a consistent qoder_<verb/noun> pattern, but ping breaks the prefix convention. Minor deviation, easily predictable overall.
Five tools is well-scoped for a subagent orchestration server. Each tool serves a necessary step in the job lifecycle with no redundancy.
The tool surface covers the full lifecycle: discover workspace via ping, start a job, poll progress/results, continue with follow-up turns, and cancel if needed. No obvious dead ends or missing operations for the stated purpose.