Loading

← Hermes Agent Operator Track

CLI, TUI, and daily operating rhythm

> Master the terminal interface you’ll use every day before you expose a public bot.

Canonical: https://www.brainyxai.co.za/education/hermes/cli-and-daily-use

Markdown: https://www.brainyxai.co.za/md/education/hermes/cli-and-daily-use.md

Course: Hermes Agent Operator Track

Lesson: 4 of 9

Minutes: 14

Author: Brainyx AI

What you will be able to do

  • Start interactive chat confidently
  • Know CLI vs TUI vs Desktop exist for different UX needs
  • Adopt a daily checklist: intent → tools → review → memory

Interfaces you’ll actually use

  • CLI — classic terminal agent loop ([CLI](https://hermes-agent.nousresearch.com/docs/user-guide/cli))
  • TUI (Ink) — modern mouse-friendly terminal UI ([TUI](https://hermes-agent.nousresearch.com/docs/user-guide/tui))
  • Desktop — installer path for non-terminal-first users ([Desktop](https://hermes-agent.nousresearch.com/docs/user-guide/desktop))

Pick one primary interface for the first week. Context-switching UIs early is how people lose track of which session/profile they’re in.

Daily operating rhythm

1. State the job with constraints (repo path, “don’t push”, “ask before rm”)

2. Let tools run — watch what Hermes executes; interrupt if off-course

3. Review diffs / side effects — especially filesystem and network

4. Capture learning — ask Hermes to save a skill or memory when a pattern worked

5. Close the session intentionally if you use messaging platforms with long-lived sessions

Personality & project context

  • SOUL.md — global voice / personality ([Personality](https://hermes-agent.nousresearch.com/docs/user-guide/features/personality))
  • Context files — project-level instructions that shape every conversation ([Context Files](https://hermes-agent.nousresearch.com/docs/user-guide/features/context-files))

Brainyx AI tip: put non-secret project conventions in context files (stack, deploy rules, “never touch prod”). Keep secrets in Hermes’ secrets mechanisms / env — never in SOUL.md committed to a public repo.

Checkpoints & rollback

Before big refactors, learn [Checkpoints & Rollback](https://hermes-agent.nousresearch.com/docs/user-guide/checkpoints-and-rollback) — shadow git / snapshots for destructive ops. Treat it as a seatbelt, not a substitute for git discipline.

Daily rhythm lab

1. Start hermes chat (or TUI/Desktop) and complete one real micro-task on a disposable folder.

2. Ask Hermes to summarize what tools it used and what it would save as a reusable skill.

3. Skim the CLI docs for three slash/commands or keybindings you’ll actually use this week.

Checkpoints

  • I have a primary interface (CLI, TUI, or Desktop)
  • I review tool side effects before trusting results

The four-beat working rhythm

Operators who get durable value run the same loop every session, and it is short enough to keep in your head.

Intent — say what done looks like before you say what to do. One sentence.

Tools — confirm what it may use for this task. Narrow deliberately when the task does not need reach.

Review — read what it actually did, not the summary of what it did.

Memory — decide explicitly what from this session should persist. Most should not.

The fourth beat is the one people skip, and it is the one that compounds. An agent that remembers the right five things is useful; one that remembers everything becomes noisy and confidently wrong about superseded facts.

Session hygiene

Long-running sessions accumulate context that drifts. When a session starts producing answers anchored to earlier, now-irrelevant work, start a fresh one and carry forward only the decisions.

Keep unrelated work in separate sessions. Mixing a client deliverable and a personal errand in one thread means the context of each degrades the other, and it makes anything you later persist to memory ambiguous.

Choosing your interface

CLI is right for scripting, servers, and piping output into other tools. The interactive TUI is right for sustained conversational work where you want history visible. Desktop is right when you want it ambient and reachable without a terminal.

These are not skill levels. Most operators use two of them for different jobs, and there is no benefit to forcing everything through one.

Solo operator reality

If you run a small South African business, the realistic daily pattern is short bursts between other work — triage in the morning, drafting midday, a review pass before close. Structure sessions to match: define one outcome per session, finish it, persist what matters, and close it.

The failure mode is an always-open session you dip into all day, which by evening holds three unrelated half-finished tasks and a context window full of noise.

Mini-FAQ

A: Short scoped sessions, narrow tool access, and stopping loops that are not converging. Meandering long sessions are the main cost driver.

A: No. Persist decisions and durable facts. Persisting transcripts pollutes future retrieval.

A: Yes — that is the CLI's main advantage. Start with something read-only until you trust the output shape.

Next lesson

Continue to [tools and backends](https://www.brainyxai.co.za/education/hermes/tools-and-backends).

Official reference: https://hermes-agent.nousresearch.com/docs/user-guide/cli

Course hub: https://www.brainyxai.co.za/education/hermes · Previous: https://www.brainyxai.co.za/education/hermes/configuration-home · Next: https://www.brainyxai.co.za/education/hermes/tools-and-backends

Return to the course hub, or explore Brainyx AI services to put the skill into a live system. Markdown: /md/education/hermes/cli-and-daily-use.md

Book a consultation · joshua@brainyxai.co.za · Markdown mirrors