CLI Mastery — Hermes Agent Commands and Flags

Hermes Agent ships with a powerful command‑line interface (CLI) that lets you interact with LLMs, manage sessions, configure models, and extend functionality through plugins and skills. This guide walks you through every flag, sub‑command, and best practice for both interactive and automated workflows.

What is the Hermes CLI?

The Hermes CLI is the primary entry point for all local LLM interactions. It can be invoked in three distinct modes:

Mode	Command	Typical Use‑Case
Interactive	hermes	Launches a REPL‑style chat where you type and receive responses in real time.
Query (non‑interactive)	hermes chat -q "<prompt>"	One‑off query useful for scripts, CI pipelines, or quick lookups.
TUI (Terminal UI)	hermes --tui	Opens a full‑screen, curses‑based UI with panels for history, context, and model selection.

All modes share a common set of global flags (--model, --temperature, --tui, etc.) that can be overridden per invocation.

Session Management

Hermes automatically groups a series of exchanges into a session. Sessions enable you to preserve context, switch between projects, and resume conversations after closing the terminal.

Starting a New Session

hermes           # starts a fresh interactive session
hermes --model gpt-4o   # start with a specific model

When you launch without --resume, Hermes creates a new session ID (UUID) and stores it under ~/.hermes/sessions/.

Resuming an Existing Session

hermes resume <session-id>

If you omit <session-id>, Hermes will present an interactive picker of recent sessions.

Listing Sessions

hermes sessions   # prints a table of session IDs, timestamps, and model used

You can also filter by date or tag:

hermes sessions --since 2024-01-01 --tag research

Slash Commands Reference

Inside any interactive or TUI session, Hermes recognises slash commands that control the environment without leaving the chat. Below is a quick‑reference table.

Slash	Description
/help	Show this cheat‑sheet inside the session.
/model	Switch the active LLM model on the fly (opens picker).
/clear	Erase the current conversation history while keeping the session alive.
/context	Display or edit the system prompt and user‑defined context blocks.
/save	Persist the current conversation to a markdown file (<session-id>.md).
/skills	List available skills; you can also invoke a skill with /skills <name>.
/plugins	Show installed plugins and enable/disable them per session.
/tools	Expose tool‑calling capabilities (e.g., web‑search, code‑exec).
/config	Open an inline editor for runtime configuration overrides.
/doctor	Run a health check; see the Health Check section for details.
/quit	Exit the current session cleanly.

You can type / followed by Tab to get auto‑completion in the TUI.

Configuration Commands

Hermes stores its persistent configuration in ~/.hermes/config.yaml. The CLI provides helpers to edit it safely.

Global Config Editor

hermes config          # Opens your default $EDITOR with the config file.

Typical entries include default model, temperature, API keys, and plugin directories.

Model Picker

hermes model          # Interactive selector of all models defined in config or discovered from providers.

You can also specify a model directly:

hermes --model claude-3-opus

Plugin Management

Plugins augment Hermes with domain‑specific capabilities (e.g., database connectors, custom parsers). They are installed as npm packages or local binaries.

List Installed Plugins

hermes plugins list

Output includes plugin name, version, and a short description.

Install a New Plugin

hermes plugins install @hermes/plugin-redis
# or from a local path
hermes plugins install ./my-custom-plugin

After installation, run hermes plugins reload to make the plugin available without restarting the CLI.

Skills Commands

Skills are reusable snippets of prompt engineering that can be invoked via /skills. They are stored as YAML files under ~/.hermes/skills/.

List Skills

hermes skills list

Create a New Skill

hermes skills create <skill-name>

The command launches an editor pre‑filled with a scaffold:

name: <skill-name>
description: "Brief description"
prompt: |
  # Write your prompt template here
  {{input}}

Edit an Existing Skill

hermes skills edit <skill-name>

You can also delete a skill with hermes skills delete <skill-name>.

Health Check

Running a health diagnostic ensures that API keys, network connectivity, and plugin integrity are all functional.

hermes doctor

Typical output:

✔ API keys: OK
✖ Redis plugin: Not found
✔ Network latency: 42ms

Auto‑Fix Mode

hermes doctor --fix

The --fix flag attempts to resolve detected issues automatically (e.g., re‑install missing plugins, prompt for missing keys).

Quick Query Mode for Automation

The query mode (hermes chat -q) is designed for scripting and CI pipelines. It reads from stdin or a pipe and returns raw JSON if requested.

Example: Pipe Input

echo "Summarize the following log file:" | hermes chat -q -i log.txt

JSON Output

hermes chat -q "What is the weather in Paris?" --json

Result:

{
  "response": "Paris is currently 18°C with light rain.",
  "model": "gpt-4o",
  "usage": {"prompt_tokens": 12, "completion_tokens": 15}
}

Combine with jq for downstream processing:

hermes chat -q "List all TODO items in the repo." --json | jq '.response'

Companion Guides

For deeper dives into specific topics, consult the following guides:

• Getting Started – Installation, first‑run, and basic concepts.
• Providers – Configuring OpenAI, Anthropic, Azure, and custom endpoints.
• Gateway – Using the Hermes Gateway for multi‑agent orchestration.
• Memory – Persistent context, vector stores, and retrieval augmentation.
• Multi‑Agent – Running several agents in parallel and routing messages.
• Automation – Advanced scripting, webhooks, and CI/CD integration.
• Troubleshooting – Common errors, log locations, and debug tips.

All documentation lives at the official site:

https://hermes-agent.nousresearch.com/docs

Best Practices Checklist

• Pin a model for production scripts (--model gpt-4o-mini) to avoid unexpected behavior.
• Persist sessions when you need reproducibility (hermes resume <id>).
• Leverage slash commands for quick context tweaks without leaving the REPL.
• Run hermes doctor --fix after any plugin installation or configuration change.
• Store reusable prompts as skills; invoke them with /skills <name> for consistency.

By mastering these commands and flags, you’ll unlock the full potential of Hermes Agent—whether you’re chatting interactively, automating workflows, or building sophisticated multi‑agent systems.

HERO_IMAGE_PROMPT: A vibrant, futuristic command center bathed in neon blue light, rows of holographic terminals displaying flowing LLM conversations, a sleek robotic assistant hovering over a glowing console labeled “Hermes CLI”. The scene conveys both technical depth and approachable mastery, with subtle reflections of code snippets on glass surfaces.