Lesson 571 of 2116
Build a Terminal Command Surface Like Hermes
Design a CLI that starts sessions, routes profiles, loads safe config, and gives a human a precise way to steer an agent.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What the local Hermes build teaches
- 2CLI
- 3command surface
- 4profile flag
Concept cluster
Terms to connect while reading
Section 1
What the local Hermes build teaches
This build lab focuses on the terminal command surface that turns an agent into a dependable developer tool. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.
A serious agent CLI separates commands, global flags, profile selection, environment loading, and noninteractive safety checks.
Compare the options
| Hermes pattern | Student build | Risk to handle |
|---|---|---|
| Name the boundary | a command tree for a small agent CLI with run, chat, config, skills, jobs, and gateway commands | letting every command inherit the same permissive environment and silently run privileged actions |
| Keep the interface small | Start with one happy path and one failure path | Avoid a demo that only works when everything is perfect |
| Make the system observable | Log decisions, status, and errors in plain language | Do not log private data or secrets |
Build the small version
- 1Draw or write a command tree for a small agent CLI with run, chat, config, skills, jobs, and gateway commands.
- 2Mark which parts are user-facing, which parts are internal, and which parts require approval.
- 3Choose one low-risk workflow and implement only that workflow first.
- 4Add one failure case before adding a second feature.
- 5Write a short operator note: what the agent may do, what it must ask about, and what it must never do.
A classroom-safe skeleton inspired by the local Hermes architecture scan.
agent-cli
chat # start an interactive session
run <prompt> # run one task and exit
config doctor # show safe config checks
skills list # list installed skills
jobs status # inspect background work
gateway start # connect messaging adapters
Global flags:
--profile school-demo
--model local-hermes
--dry-run
--jsonKey terms in this lesson
The big idea: command surface is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Build a Terminal Command Surface Like Hermes”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 48 min
Computer Use API: Letting AI Click Through GUIs
Computer Use lets Claude see your screen and use it — mouse, keyboard, apps. The capability is real, the gotchas are real. A hands-on look at what works in 2026.
Creators · 45 min
Browser Agents: Capabilities and Pitfalls
Browser agents — Operator, Atlas, Browser Use, MultiOn — are the most visible agent category. The capability is genuine, the failure modes are specific. Build with eyes open.
Creators · 75 min
Capstone: Build and Ship a Real Agent
Everything comes together. Design, code, test, secure, and ship a production-quality agent with open-source code you can fork today.