# CLI: run bounded tasks and inspect the working environment

> Use the terminal interface for interactive work, bounded single queries, explicit tool selection, and resumable sessions.

Canonical: https://hermeswatcher.com/tools/cli  
Kind: Surface · Development & operations  
Last reviewed: Oct 19, 2026  
Basis: Explained from the official Hermes Agent docs and repository (Nous Research). Steps follow the linked official sources.

## What it is for

The CLI is useful when a workflow already involves files, repositories, or scripts and you want to see the agent's tool activity. Official documentation covers interactive sessions, single-query mode, session continuation, and toolset selection. Start from the correct directory and profile so the agent sees the intended project context. For repeatable work, preserve the prompt and input boundaries rather than relying on a long conversation to supply hidden requirements.

## What you need

- A supported Hermes installation available to the shell and a configured model route.
- The intended working directory, profile, project instructions, and permissions for the tools being requested.

## Setting it up

1. Check the installed CLI's help and current environment before adapting a command from another release or operating system.
2. Run a small read-only task with explicit inputs and output expectations. Use a prompt file for lengthy instructions where supported, and retain the command and resulting artifact together.

## How to check it works

- Inspect the actual saved file or retrieved record, and confirm which model, profile, and working directory were used.
- When resuming, check the project context and outstanding task before allowing further changes.

## Limits

- A completed terminal process can still produce an incomplete answer or fail to deliver an artifact.
- Non-interactive work needs explicit failure behavior because nobody may be present to answer prompts. Shell quoting and platform-specific paths require care.

## Related workflows

- [Carry project knowledge into the next session](https://hermeswatcher.com/workflows/project-knowledge.md)
- [Build a useful GitHub issue review](https://hermeswatcher.com/workflows/github-issue-review.md)
- [Know whether an automation actually worked](https://hermeswatcher.com/workflows/reliable-recurring-automation.md)

## Sources

- [Official CLI interface](https://hermes-agent.nousresearch.com/docs/user-guide/cli)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt
