cc-as-subagent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_BIN | No | Pin an exact CLI build. | resolved from `PATH` |
| CC_AS_SUBAGENT_STATE_DIR | No | Where job state lives. Deliberately outside any workspace. | %LOCALAPPDATA%\cc-as-subagent |
| CC_AS_SUBAGENT_RESTRICTED | No | Set to `1` to add `--restricted` (2.1.248+). Stronger confinement, but it loads no user settings — pair it with `CC_AS_SUBAGENT_PASSTHROUGH` for whatever supplies your credentials. | off |
| CC_AS_SUBAGENT_PASSTHROUGH | No | Comma-separated variable names to pass to `claude`. Everything else is dropped. | (none) |
| CC_AS_SUBAGENT_USE_API_KEY | No | Set to `1` to pass `ANTHROPIC_API_KEY` through. Off by default so an inherited key cannot silently switch you from a subscription to API billing. | off |
| CC_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 Claude Code. |
| claude_runA | Start a new Claude Code session in a workspace. Returns a jobId immediately; the run continues in the background. Use claude_status to poll for the result. Tier "consult" is read-only; "execute" may edit files in the workspace. |
| claude_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. |
| claude_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. |
| claude_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
The tools are mostly distinct: ping is a liveness check, claude_run starts a job, claude_status polls it, claude_cancel stops it, and claude_reply continues a finished job. The only mild ambiguity is between claude_run and claude_reply, since both start work in a session, but the descriptions clarify that reply is specifically for follow-up turns on an existing session.
All tools use the claude_ prefix with a clear verb: cancel, ping, run, status, reply. This is a consistent and predictable pattern. The minor deviation is that ping is a noun/verb that doesn't fit the job lifecycle as directly as the others, but it is still clearly named.
Five tools is well-scoped for a subagent orchestration server: start, poll, cancel, reply, and health check. Each tool earns its place and there is no bloat.
The core lifecycle of running and managing a Claude Code session is covered: start, poll, cancel, and follow-up. A minor gap is the lack of a way to list active jobs or sessions, which could be useful for recovery, but agents can work around it by tracking jobIds.