HermitAgent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_taskA | Run a coding task using a local LLM (default: qwen3-coder:30b). Immediately returns {status:'running', task_id}; poll with check_task(task_id). Return values: {status:"running", task_id} — task is running. {status:"waiting", task_id, question, options} — HermitAgent is asking a question. Reply with reply_task(task_id, message). {status:"done", result} — task completed. {status:"needs_review", result} — execution finished but Hermit found a likely issue. |
| reply_taskA | Send a reply to HermitAgent when run_task returned {status:"waiting"}. Return format is the same as run_task (waiting or done). |
| check_taskA | Check the current status of a background task (use after run_task with background=true). Return values: {status:"running"} — still running. {status:"waiting", question, options} — user input required. {status:"done", result} — completed. {status:"needs_review", result} — completed execution requires host review. {status:"not_found"} — task_id not found (already completed and removed). Use full=true to retrieve the complete result without truncation. |
| cancel_taskC | Cancel a running task. |
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
Each tool maps to a distinct lifecycle action: start (run_task), respond to prompts (reply_task), poll status (check_task), and abort (cancel_task). There is no functional overlap between them.
All four tools follow the same verb_task pattern (run, reply, check, cancel). The naming is predictable and makes the API easy to navigate.
Four tools is well-scoped for an async agentic task runner. Each tool earns its place and the surface is neither bloated nor thin.
The core lifecycle is covered: launch, interact, poll, and cancel. However, the needs_review state lacks an explicit approve/resume action, and completed tasks are not retrievable after removal, which are minor gaps.