mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-05-06 02:37:05 +08:00
986ec04048
* docs: document /kanban slash command
The kanban user guide and slash-commands reference only mentioned the
/kanban slash command in passing. Add a proper section covering:
- CLI and gateway both expose the full hermes kanban surface via
hermes_cli.kanban.run_slash (identical argument surface)
- Mid-run usage: /kanban bypasses the running-agent guard, so reads
and writes land immediately while an agent is still in a turn
- Auto-subscribe on /kanban create from the gateway — originating
chat is subscribed to terminal events, with a worked example
- Output truncation (~3800 chars) in messaging
- Autocomplete hint list vs full subcommand surface
Also adds /kanban rows to both slash-command tables (CLI + messaging)
in reference/slash-commands.md and moves it into the 'works in both'
notes bucket.
* docs(kanban): frame the model's tool surface as primary, CLI as the human surface
The kanban user guide and CLI reference read as if you drive the board
by running `hermes kanban` commands everywhere. In practice:
- **You** (human, scripts, cron, dashboard) use the `hermes kanban …`
CLI, the `/kanban …` slash command, or the REST/dashboard.
- **Workers** spawned by the dispatcher use a dedicated `kanban_*`
toolset (`kanban_show`, `kanban_complete`, `kanban_block`,
`kanban_heartbeat`, `kanban_comment`, `kanban_create`,
`kanban_link`) and never shell out to the CLI.
Changes to `user-guide/features/kanban.md`:
- New 'Two surfaces' intro distinguishes the two front doors up front.
- Quick-start section re-labelled so each step says who is running it
(you vs. orchestrator vs. worker).
- 'How workers interact with the board' rewritten:
- Lead with "Workers do not shell out to `hermes kanban`."
- Tool table extended with required params.
- Concrete worker-turn example (`kanban_show` → `kanban_heartbeat`
→ `kanban_complete`) and an orchestrator fan-out example
(`kanban_create` x N with `parents=[...]`).
- Moved 'Why tools not CLI' from a defensive aside to a clean
follow-up section.
- 'Worker skill' section explicitly says the lifecycle is taught
in tool calls, not CLI commands.
- 'Pinning extra skills' reordered — orchestrator tool form first
(the usual case), human/CLI second, dashboard third.
- 'Orchestrator skill' now shows a canonical `kanban_create` /
`kanban_link` / `kanban_complete` tool-call sequence instead of
only describing what the skill teaches.
- CLI-command-reference heading now clarifies this is the human
surface, with a cross-link to the tool-surface section.
- 'Runs — one row per attempt' structured-handoff example replaced:
the primary example is now `kanban_complete(summary=..., metadata=...)`
(what a worker actually does), with the CLI form retained as
"when you, the human, need to close a task a worker can't."
Changes to `reference/cli-commands.md`:
- `hermes kanban` intro marks itself as the human / scripting surface
and links out to the worker tool surface.
- Corrected `comment <id>` description — the next worker reads it via
`kanban_show()`, not by running `hermes kanban show`.
* docs(kanban-tutorial): reframe worker actions as tool calls
Honest answer to Teknium's follow-up: no, the first pass missed the
tutorial. The four stories all showed `hermes kanban claim /
complete / block / unblock` as if the backend-dev, pm, and reviewer
personas were humans running CLI commands. In a real hermes kanban
run those agents are dispatcher-spawned workers driving the board
through the `kanban_*` tool surface.
Changes:
- Setup intro now distinguishes the three surfaces up front
(dashboard / CLI for you, `kanban_*` tools for workers) and
establishes the convention: `bash` blocks are commands *you* run,
`# worker tool calls` blocks are what the agent emits.
- Story 1 (solo dev schema): 'Claim the schema task, do the work,
hand off' block replaced with the dispatcher spawning the
backend-dev worker and a `kanban_show → kanban_heartbeat →
kanban_complete` tool-call sequence. The 'On the CLI' `hermes
kanban show / runs` block re-labelled as 'you peeking at the board'
to keep it correct as a human inspection step.
- Story 2 (fleet farming): note about structured handoff updated
from `--summary` / `--metadata` CLI flags to
`kanban_complete(summary=..., metadata=...)` tool form.
- Story 3 (role pipeline): the big PM/engineer/reviewer block fully
rewritten as three worker tool-call sequences — PM worker
completes spec, engineer worker blocks, human/reviewer
`hermes kanban unblock` (or `/kanban unblock`), engineer worker
respawns and completes. The respawn-as-new-run mechanic is now
explicit.
- Reviewer paragraph: `build_worker_context` replaced with
`kanban_show()` — that's the tool that delivers the parent
handoff to the model.
- Structured handoff section heading and body updated:
`--summary`/`--metadata` → `summary`/`metadata` (tool params),
with a note that the tool surface doesn't expose a bulk variant
for the same reason the CLI refuses multi-task `complete`.
Story 4 (circuit breaker) unchanged — its workers fail to spawn,
so there are no tool calls to show; the `hermes kanban create` and
`hermes kanban runs` commands in it are correctly human-driven.
15 KiB
15 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 2 | Slash Commands Reference | Complete reference for interactive CLI and messaging slash commands |
Slash Commands Reference
Hermes has two slash-command surfaces, both driven by a central COMMAND_REGISTRY in hermes_cli/commands.py:
- Interactive CLI slash commands — dispatched by
cli.py, with autocomplete from the registry - Messaging slash commands — dispatched by
gateway/run.py, with help text and platform menus generated from the registry
Installed skills are also exposed as dynamic slash commands on both surfaces. That includes bundled skills like /plan, which opens plan mode and saves markdown plans under .hermes/plans/ relative to the active workspace/backend working directory.
Interactive CLI slash commands
Type / in the CLI to open the autocomplete menu. Built-in commands are case-insensitive.
Session
| Command | Description |
|---|---|
/new (alias: /reset) |
Start a new session (fresh session ID + history) |
/clear |
Clear screen and start a new session |
/history |
Show conversation history |
/save |
Save the current conversation |
/retry |
Retry the last message (resend to agent) |
/undo |
Remove the last user/assistant exchange |
/title |
Set a title for the current session (usage: /title My Session Name) |
/compress [focus topic] |
Manually compress conversation context (flush memories + summarize). Optional focus topic narrows what the summary preserves. |
/rollback |
List or restore filesystem checkpoints (usage: /rollback [number]) |
/snapshot [create|restore <id>|prune] (alias: /snap) |
Create or restore state snapshots of Hermes config/state. create [label] saves a snapshot, restore <id> reverts to it, prune [N] removes old snapshots, or list all with no args. |
/stop |
Kill all running background processes |
/queue <prompt> (alias: /q) |
Queue a prompt for the next turn (doesn't interrupt the current agent response). |
/steer <prompt> |
Inject a mid-run note that arrives at the agent after the next tool call — no interrupt, no new user turn. The text is appended to the last tool result's content once the current tool completes, giving the agent new context without breaking the current tool-calling loop. Use this to nudge direction mid-task (e.g. "focus on the auth module" while the agent is running tests). |
/goal <text> |
Set a standing goal Hermes works toward across turns — our take on the Ralph loop. After each turn an auxiliary judge model decides whether the goal is done; if not, Hermes auto-continues. Subcommands: /goal status, /goal pause, /goal resume, /goal clear. Budget defaults to 20 turns (goals.max_turns); any real user message preempts the continuation loop, and state survives /resume. See Persistent Goals for the full walkthrough. |
/resume [name] |
Resume a previously-named session |
/redraw |
Force a full UI repaint (recovers from terminal drift after tmux resize, mouse selection artifacts, etc.) |
/status |
Show session info |
/agents (alias: /tasks) |
Show active agents and running tasks across the current session. |
/background <prompt> (alias: /bg, /btw) |
Run a prompt in a separate background session. The agent processes your prompt independently — your current session stays free for other work. Results appear as a panel when the task finishes. See CLI Background Sessions. |
/branch [name] (alias: /fork) |
Branch the current session (explore a different path) |
Configuration
| Command | Description |
|---|---|
/config |
Show current configuration |
/model [model-name] |
Show or change the current model. Supports: /model claude-sonnet-4, /model provider:model (switch providers), /model custom:model (custom endpoint), /model custom:name:model (named custom provider), /model custom (auto-detect from endpoint). Use --global to persist the change to config.yaml. Note: /model can only switch between already-configured providers. To add a new provider, exit the session and run hermes model from your terminal. |
/personality |
Set a predefined personality |
/verbose |
Cycle tool progress display: off → new → all → verbose. Can be enabled for messaging via config. |
/fast [normal|fast|status] |
Toggle fast mode — OpenAI Priority Processing / Anthropic Fast Mode. Options: normal, fast, status. |
/reasoning |
Manage reasoning effort and display (usage: /reasoning [level|show|hide]) |
/skin |
Show or change the display skin/theme |
/statusbar (alias: /sb) |
Toggle the context/model status bar on or off |
/voice [on|off|tts|status] |
Toggle CLI voice mode and spoken playback. Recording uses voice.record_key (default: Ctrl+B). |
/yolo |
Toggle YOLO mode — skip all dangerous command approval prompts. |
/footer [on|off|status] |
Toggle the gateway runtime-metadata footer on final replies (shows model, tool counts, timing). |
/busy [queue|steer|interrupt|status] |
CLI-only: control what pressing Enter does while Hermes is working — queue the new message, steer mid-turn, or interrupt immediately. |
/indicator [kaomoji|emoji|unicode|ascii] |
CLI-only: pick the TUI busy-indicator style. |
Tools & Skills
| Command | Description |
|---|---|
/tools [list|disable|enable] [name...] |
Manage tools: list available tools, or disable/enable specific tools for the current session. Disabling a tool removes it from the agent's toolset and triggers a session reset. |
/toolsets |
List available toolsets |
/browser [connect|disconnect|status] |
Manage local Chrome CDP connection. connect attaches browser tools to a running Chrome instance (default: ws://localhost:9222). disconnect detaches. status shows current connection. Auto-launches Chrome if no debugger is detected. |
/skills |
Search, install, inspect, or manage skills from online registries |
/cron |
Manage scheduled tasks (list, add/create, edit, pause, resume, run, remove) |
/curator |
Background skill maintenance — status, run, pin, archive. See Curator. |
/kanban <action> |
Drive the multi-profile collaboration board without leaving chat. Full hermes kanban surface is available: /kanban list, /kanban show t_abc, /kanban create "title" --assignee X, /kanban comment t_abc "text", /kanban unblock t_abc, /kanban dispatch, etc. See Kanban slash command. |
/reload-mcp (alias: /reload_mcp) |
Reload MCP servers from config.yaml |
/reload |
Reload .env variables into the running session (picks up new API keys without restarting) |
/plugins |
List installed plugins and their status |
Info
| Command | Description |
|---|---|
/help |
Show this help message |
/usage |
Show token usage, cost breakdown, session duration, and — when available from the active provider — an Account limits section with remaining quota / credits / plan usage pulled live from the provider's API. |
/insights |
Show usage insights and analytics (last 30 days) |
/platforms (alias: /gateway) |
Show gateway/messaging platform status |
/paste |
Attach a clipboard image |
/copy [number] |
Copy the last assistant response to clipboard (or the Nth-from-last with a number). CLI-only. |
/image <path> |
Attach a local image file for your next prompt. |
/debug |
Upload debug report (system info + logs) and get shareable links. Also available in messaging. |
/profile |
Show active profile name and home directory |
/gquota |
Show Google Gemini Code Assist quota usage with progress bars (only available when the google-gemini-cli provider is active). |
Exit
| Command | Description |
|---|---|
/quit |
Exit the CLI (also: /exit). |
Dynamic CLI slash commands
| Command | Description |
|---|---|
/<skill-name> |
Load any installed skill as an on-demand command. Example: /gif-search, /github-pr-workflow, /excalidraw. |
/skills ... |
Search, browse, inspect, install, audit, publish, and configure skills from registries and the official optional-skills catalog. |
Quick Commands
User-defined quick commands map a short slash command to either a shell command or another slash command. Configure them in ~/.hermes/config.yaml:
quick_commands:
status:
type: exec
command: systemctl status hermes-agent
deploy:
type: exec
command: scripts/deploy.sh
inbox:
type: alias
target: /gmail unread
Then type /status, /deploy, or /inbox in the CLI or a messaging platform. Quick commands are resolved at dispatch time and may not appear in every built-in autocomplete/help table.
String-only prompt shortcuts are not supported as quick commands. Put longer reusable prompts in a skill, or use type: alias to point at an existing slash command.
Alias Resolution
Commands support prefix matching: typing /h resolves to /help, /mod resolves to /model. When a prefix is ambiguous (matches multiple commands), the first match in registry order wins. Full command names and registered aliases always take priority over prefix matches.
Messaging slash commands
The messaging gateway supports the following built-in commands inside Telegram, Discord, Slack, WhatsApp, Signal, Email, and Home Assistant chats:
| Command | Description |
|---|---|
/new |
Start a new conversation. |
/reset |
Reset conversation history. |
/status |
Show session info. |
/stop |
Kill all running background processes and interrupt the running agent. |
/model [provider:model] |
Show or change the model. Supports provider switches (/model zai:glm-5), custom endpoints (/model custom:model), named custom providers (/model custom:local:qwen), and auto-detect (/model custom). Use --global to persist the change to config.yaml. Note: /model can only switch between already-configured providers. To add a new provider or set up API keys, use hermes model from your terminal (outside the chat session). |
/personality [name] |
Set a personality overlay for the session. |
/fast [normal|fast|status] |
Toggle fast mode — OpenAI Priority Processing / Anthropic Fast Mode. |
/retry |
Retry the last message. |
/undo |
Remove the last exchange. |
/sethome (alias: /set-home) |
Mark the current chat as the platform home channel for deliveries. |
/compress [focus topic] |
Manually compress conversation context. Optional focus topic narrows what the summary preserves. |
/title [name] |
Set or show the session title. |
/resume [name] |
Resume a previously named session. |
/usage |
Show token usage, estimated cost breakdown (input/output), context window state, session duration, and — when available from the active provider — an Account limits section with remaining quota / credits pulled live from the provider's API. |
/insights [days] |
Show usage analytics. |
/reasoning [level|show|hide] |
Change reasoning effort or toggle reasoning display. |
/voice [on|off|tts|join|channel|leave|status] |
Control spoken replies in chat. join/channel/leave manage Discord voice-channel mode. |
/rollback [number] |
List or restore filesystem checkpoints. |
/background <prompt> |
Run a prompt in a separate background session. Results are delivered back to the same chat when the task finishes. See Messaging Background Sessions. |
/queue <prompt> (alias: /q) |
Queue a prompt for the next turn without interrupting the current one. |
/steer <prompt> |
Inject a message after the next tool call without interrupting — the model picks it up on its next iteration rather than as a new turn. |
/goal <text> |
Set a standing goal Hermes works toward across turns — our take on the Ralph loop. A judge model checks after each turn; if not done, Hermes auto-continues until it is, you pause/clear it, or the turn budget (default 20) is hit. Subcommands: /goal status, /goal pause, /goal resume, /goal clear. Safe to run mid-agent for status/pause/clear; setting a new goal requires /stop first. See Persistent Goals. |
/footer [on|off|status] |
Toggle the runtime-metadata footer on final replies (shows model, tool counts, timing). |
/curator [status|run|pin|archive] |
Background skill maintenance controls. |
/kanban <action> |
Drive the multi-profile collaboration board from chat — identical argument surface to the CLI. Bypasses the running-agent guard, so /kanban unblock t_abc, /kanban comment t_abc "…", /kanban list --mine, etc. work mid-turn. /kanban create … auto-subscribes the originating chat to the new task's terminal events. See Kanban slash command. |
/reload-mcp (alias: /reload_mcp) |
Reload MCP servers from config. |
/yolo |
Toggle YOLO mode — skip all dangerous command approval prompts. |
/commands [page] |
Browse all commands and skills (paginated). |
/approve [session|always] |
Approve and execute a pending dangerous command. session approves for this session only; always adds to permanent allowlist. |
/deny |
Reject a pending dangerous command. |
/update |
Update Hermes Agent to the latest version. |
/restart |
Gracefully restart the gateway after draining active runs. When the gateway comes back online, it sends a confirmation to the requester's chat/thread. |
/debug |
Upload debug report (system info + logs) and get shareable links. |
/help |
Show messaging help. |
/<skill-name> |
Invoke any installed skill by name. |
Notes
/skin,/snapshot,/gquota,/reload,/tools,/toolsets,/browser,/config,/cron,/skills,/platforms,/paste,/image,/statusbar,/plugins,/busy,/indicator,/redraw,/clear,/history,/save,/copy, and/quitare CLI-only commands./verboseis CLI-only by default, but can be enabled for messaging platforms by settingdisplay.tool_progress_command: trueinconfig.yaml. When enabled, it cycles thedisplay.tool_progressmode and saves to config./sethome,/update,/restart,/approve,/deny, and/commandsare messaging-only commands./status,/background,/queue,/steer,/voice,/reload-mcp,/rollback,/debug,/fast,/footer,/curator,/kanban, and/yolowork in both the CLI and the messaging gateway./voice join,/voice channel, and/voice leaveare only meaningful on Discord.