gormes-agent

Hermes-class agents from one Go binary.
Gormes is a Go-native runtime for Hermes-compatible agents: providers, tools, skills, local SQLite memory, sessions, and gateways in one static binary. It carries the 30 most-used Hermes skills to Termux, Windows-without-Python, and locked-down corp Linux — no pip, no venv, no Docker daemon.

Gormes is not a micro-agent. It keeps the broad Hermes agent architecture and makes it portable, inspectable, and cheap to operate from a normal terminal.

At A Glance

Quick Install

Linux, macOS, WSL2:

curl -fsSL https://github.com/TrebuchetDynamics/gormes-agent/releases/latest/download/install.sh | sh

Windows (native PowerShell):

irm https://raw.githubusercontent.com/TrebuchetDynamics/gormes-agent/main/scripts/install.ps1 | iex

Inspect first: download the script, read it, then run it. Both installers are user-scoped — no root or admin paths.

After installation:

gormes doctor --offline
gormes setup
gormes chat

That is the shortest path: prove the runtime locally, configure provider/model, then open a provider-backed terminal chat.

First Setup

gormes setup                 # guided setup for provider, model, terminal, gateway, tools
gormes setup provider        # direct provider setup shortcut
gormes chat                  # provider-backed terminal chat
gormes doctor --offline      # local runtime, TUI, gateway, memory — no credentials needed
gormes --offline             # native TUI, no network

If gormes chat opens, the TUI and gateway have a model to use.

Built For

• Developers who want a real agent runtime without Python environment drift.
• Operators who need offline diagnostics before adding provider credentials.
• Small servers, Termux/Android, WSL2, and locked-down Linux hosts where Docker or venv repair is friction.
• Termux can be the controller while a remote SSH host handles Docker, browser automation, GPU/local models, and large builds.
• Long-running personal or team agents that need local sessions, memory, tools, and chat gateways.

Not yet for teams that require signed enterprise releases, full Hermes parity, voice/TTS parity, or broad channel parity on day one.

What Works Today

Full Hermes-parity status by phase lives in the roadmap.

Why People Switch

How It Works

Gormes follows the Hermes agent shape, but moves the operational surface into Go:

1. cmd/gormes owns the CLI, setup, TUI entry point, dashboard, and gateway commands.
2. internal/kernel runs the turn loop shared by the TUI, one-shot chat, and channel gateway.
3. internal/provider and internal/hermes adapt OpenAI-compatible, Anthropic, DeepSeek, Groq, Ollama, Codex, OpenCode, and custom endpoints.
4. internal/tools and internal/skills expose the tool and skill registry without a Python sidecar.
5. internal/goncho, internal/memory, and internal/session keep local memory and session state inspectable in SQLite.

Daily Use

gormes                          # open the native TUI
gormes setup                    # guided setup and reconfiguration
gormes setup --quick            # fill missing setup items only
gormes dashboard                # web UI at http://127.0.0.1:43827/dashboard
gormes config show              # inspect config with secrets redacted
gormes profile use <name>       # switch isolated profile homes
gormes gateway                  # run the configured messaging gateway
gormes gateway status --json    # inspect gateway runtime state
gormes logs                     # read recent gateway logs

CLI vs Gateway

Migrating From Hermes Or OpenClaw

Always dry-run first and review the redacted manifest before applying.

gormes migrate hermes   --dry-run --source ~/.hermes
gormes migrate hermes   --yes     --source ~/.hermes

gormes migrate openclaw --dry-run --source ~/.openclaw
gormes migrate openclaw --yes     --source ~/.openclaw
gormes migrate openclaw --yes --secrets --source ~/.openclaw

OpenClaw cleanup archives old directories rather than deleting them:

gormes migrate openclaw cleanup --dry-run
gormes migrate openclaw cleanup --yes

Build From Source

git clone https://github.com/TrebuchetDynamics/gormes-agent.git
cd gormes-agent
make build
export PATH="$PWD/bin:$PATH"
gormes doctor --offline

Docs

Security & Trust

• gormes doctor --offline and gormes --offline prove local readiness before any token spend.
• Provider secrets stay local under ~/.gormes/.env; config under ~/.gormes/config.toml.
• Tagged releases publish a single static binary per target plus SHA-256 checksums and SBOMs (release signing and package-manager lanes are still hardening).
• The curl … | sh install path is validated by an end-to-end suite (tests/install/e2e.sh) covering API outage with redirect fallback, SHA-256 mismatch abort, SSH-origin update fallback to public HTTPS, hosts without Go/curl/wget/systemd, Termux detection, sudo'd root install, and --uninstall --dry-run preview. Runnable locally or via the install-e2e workflow on demand.

How It's Built

Gormes is the artifact of an autonomous-porting methodology — a validation-gated planner → builder → TDD-slice loop that ports Hermes to Go one bounded vertical at a time. The runtime is the product; the methodology is the supporting evidence.

• Strategy: Gormes Success Plan
• Engineering blog: TrebuchetDynamics Engineering (RSS)
• Differentiator: v1.0 differentiator
• Toolkit extraction (agentic-porting-kit): tracked as a Phase 8 row; until that public repo exists, the repo-local development skills are the inspectable placeholder.

Hermes-Agent, with upstream Git history preserved for attribution, remains the parity oracle.

Status

Latest public release: v0.2.12.

CI runs go test ./... -count=1, go run ./cmd/progress validate, and git diff --check. The single static binary ships for Linux, macOS, Windows, and Termux/Android. The current Linux build measures ~45.8 MB (benchmarks.json). WASI Whisper tiny.en runs at 3.78x realtime (benchmarks.json, 2026-05-10). Offline doctor peaks at ~25.6 MB RSS (benchmarks.json, 2026-05-16).

See CHANGELOG.md and SECURITY.md.

Built by Trebuchet Dynamics.
Hermes Agent lineage by Nous Research.
MIT license.