operator surface
HERMES / GO OPERATOR SHELL
Run Hermes Through a Go Operator Console.
Stop waiting for the clean-room rewrite. Gormes already ships a Go shell, a Go-native tool loop, Route-B resilience, and a Telegram adapter.
Boot it locally. Judge the surface yourself. Keep the promises honest.
Current boundary: the Go shell ships now. Transcript memory stays on the later cutover path.
Proof Rail
messaging edge
Telegram adapter
deployment
Zero-CGO
verification
Wire Doctor
phase
2 ships now
Install Hermes fast. Then boot Gormes.
Bootstrap Hermes first, reload your shell, then install the Go operator console. No fake checklist. No hidden backend dance.
01 / INSTALL HERMES
Works on Linux, macOS, WSL2, and Android via Termux. The installer handles the platform-specific setup for you. Android / Termux: The tested manual path is documented in the Termux guide. On Termux, Hermes installs a curated .[termux] extra because the full .[all] extra currently pulls Android-incompatible voice dependencies. Windows: Native Windows is not supported. Please install WSL2 and run the command above.
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
02 / ACTIVATE HERMES
Reload your shell profile so the freshly installed Hermes binary is on PATH, then let Hermes complete first-run bootstrap.
source ~/.bashrc # reload shell (or: source ~/.zshrc)
hermes
03 / BOOT GORMES
Today the Gormes installer shells out to Go itself. Keep Go 1.25+ on PATH until release artifacts exist. It installs `gormes` into your Go bin. If the installer prints an export PATH line, run it in this shell before launching gormes. If you want a local `./bin/gormes`, use the source-build path below.
curl -fsSL https://gormes.ai/install.sh | sh
# if the installer printed an export PATH line, run it in this shell now
gormes doctor --offline
gormes
# or build a local ./bin/gormes:
git clone https://github.com/TrebuchetDynamics/gormes-agent
cd gormes-agent/gormes && make build
./bin/gormes doctor --offline
./bin/gormes
Why Hermes users switch
Gormes is not a reskin. It is the hardened shell around the workflows you already trust.
RESPONSIVENESS
Cut startup tax
Use the Go shell that boots like a tool, not a ceremony.
TOOLS
Keep the loop typed
Run the Go-native tool surface in-process and verify it before you spend more tokens.
ISOLATION
Fence the blast radius
Keep the Telegram adapter behind its own subcommand edge so failures stay local.
HONESTY
Ship the boundary you have
The shell is real now. Transcript memory and the brain cutover are still later work.
Shipping State, Not Wishcasting
This ledger separates what already ships on trunk from the next real handoff lines.
SHIPPED
Phase 1 — Dashboard
The Bubble Tea shell and operator surface are already real.
SHIPPED
Phase 2 — Gateway
Tool registry, Telegram scout, and thin session resume already live on trunk.
NEXT
Phase 3 — Memory
SQLite + FTS5 transcript memory still marks the real handoff line.
LATER
Phase 4 — Brain
Prompt building and native agent orchestration move after memory is real.
Inspect the Machine
Read the architecture, inspect the source, and keep the install story honest with the upstream docs close at hand.