t3-autopilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| T3_AUTOPILOT_HOME | No | Overrides the data directory (default ~/.t3-autopilot), where policy.yaml (your policy override) and log.jsonl (delegations and outcomes) are 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_modelA | Call before every child task, including ones you would start with your native subagent tool. Returns 1-3 candidates, best first; pass a candidate's providerInstanceId, model and options as delegate_task.target (sameAsOrchestrator: true means your native subagent tool also works). If the first cannot start or hits a usage limit, use the next. Always pass taskType, one of:
|
| log_delegationB | Optional. Record a delegate_task you just made; returns a delegationId to pass to log_outcome later. log_outcome also works without it. |
| log_outcomeA | Call after reviewing a child's result. Pass delegationId (from log_delegation) or taskType + providerInstanceId + model. outcome: success (accepted as is), corrected (needed fixes) or failure. |
| get_statsB | Summary of the local delegation log by task type and model: counts, outcomes and success rate. |
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
The tools cover distinct lifecycle stages: recommendation, optional delegation logging, outcome logging, and statistics. The main possible confusion is between log_delegation and log_outcome, but the descriptions clarify that log_delegation is optional and log_outcome records the final result.
All four tool names follow a consistent verb_noun snake_case pattern: recommend_model, log_delegation, log_outcome, and get_stats. There are no mixed conventions or vague standalone verbs.
Four tools is well-scoped for a model-recommendation and delegation-tracking server. Each tool has a clear role in the workflow, and the set is neither bloated nor trivially thin.
The surface covers the core workflow: recommend a model, optionally log the delegation, log the outcome, and view aggregate stats. Minor gaps exist, such as listing or inspecting individual delegation records, but the main lifecycle is complete enough for the stated purpose.