Gormes

§ 01 · OPEN SOURCE · MIT LICENSE · UNDER CONSTRUCTION

One Go Binary. No Python. No Drift.

Gormes is a Go-native runtime for AI agents.

Built to solve the operations problem — not the AI problem.

One static binary. No virtualenvs. No dependency hell.

Early-stage. Reliability-first runtime for developers who ship agents, not demos.
Install View Source

INSTALL

Source-backed installers. One managed checkout.

1. UNIX / MACOS / TERMUX

curl -fsSL https://gormes.ai/install.sh | sh

2. WINDOWS POWERSHELL

irm https://gormes.ai/install.ps1 | iex

3. RUN

gormes

Source-backed for now. Installers manage a checkout while binary releases settle. Read the installer source →

§ 02 · WHY GORMES

Why Hermes breaks in production — and how Gormes fixes it.

Hermes breaks in production because:

  • environments drift
  • installs fail
  • agents crash mid-run
  • streams drop and lose work

Single Static Binary

Zero CGO. ~17.7 MB. scp it to Termux, Alpine, a fresh VPS — it runs. No Python, no virtualenv, no Nix.

No Runtime Drift

Pure Go. No pip, no npm, no env activation. The binary you tested is the binary that deploys.

Streams That Don't Drop

Route-B reconnect treats SSE drops as recoverable, not fatal. Your agent doesn't lose work to a flaky network.

Local Validation

gormes doctor --offline checks tool schemas before you burn tokens. Catch bad wiring before a model round-trip.

§ 04 · BUILD STATE

What works today, and what's still being wired up.

Current focus

  • Gateway stability
  • Memory system

Next milestone

Full Go-native runtime, no Hermes

View full phase-by-phase checklist
SHIPPED · 3/3

Phase 1 — The Dashboard

  • 1.A Core TUI
  • 1.B Wire Doctor
  • 1.C Automation Reliability
IN PROGRESS · 12/19

Phase 2 — The Gateway

  • 2.A Tool Registry
  • 2.B.1 Telegram Scout
  • 2.B.10 WeChat Adapter
  • 2.B.11 Discord Forum Channels
  • 2.B.2 Gateway Chassis + Discord
  • 2.B.3 Slack on Shared Chassis
  • 2.B.4 WhatsApp Adapter
  • 2.B.5 Session Context + Delivery Routing
  • 2.C Thin Mapping Persistence
  • 2.D Cron / Scheduled Automations
  • 2.E.0 OS-AI Spine: Deterministic Subagent Runtime
  • 2.E.1 OS-AI Spine: Delegation Policy + Child Execution
  • 2.E.2 OS-AI Spine: Concurrent-Tool Cancellation
  • 2.F.1 Slash Command Registry + Gateway Dispatch
  • 2.F.2 Hook Registry + BOOT.md
  • 2.F.3 Restart / Pairing / Status
  • 2.F.4 Home Channel + Operator Surfaces
  • 2.F.5 Gateway Mid-Run Steering + Active-Turn Policy
  • 2.G OS-AI Spine: Skills Runtime
IN PROGRESS · 12/14

Phase 3 — The Black Box (Memory)

  • 3.A SQLite + FTS5 Lattice
  • 3.B Ontological Graph + LLM Extractor
  • 3.C Neural Recall + Context Injection
  • 3.D Semantic Fusion + Local Embeddings
  • 3.D.5 Memory Mirror (USER.md sync)
  • 3.E.1 Session Index Mirror
  • 3.E.2 Tool Execution Audit Log
  • 3.E.3 Transcript Export Command
  • 3.E.4 Extraction State Visibility
  • 3.E.5 Insights Audit Log
  • 3.E.6 Memory Decay
  • 3.E.7 Cross-Chat Synthesis
  • 3.E.8 Session Lineage + Cross-Source Search
  • 3.F Goncho Honcho Memory Parity
IN PROGRESS · 0/8

Phase 4 — The Brain Transplant

  • 4.A Provider Adapters
  • 4.B Context Engine + Compression
  • 4.C Native Prompt Builder
  • 4.D Smart Model Routing
  • 4.E Trajectory + Insights
  • 4.F Title Generation
  • 4.G Credentials + OAuth
  • 4.H Rate / Retry / Caching
IN PROGRESS · 1/18

Phase 5 — The Final Purge

  • 5.A Tool Surface Port
  • 5.B Sandboxing Backends
  • 5.C Browser Automation
  • 5.D Vision + Image Generation
  • 5.E TTS / Voice / Transcription
  • 5.F Skills System (Remaining)
  • 5.G MCP Integration
  • 5.H ACP Integration
  • 5.I Plugins Architecture
  • 5.J Approval / Security Guards
  • 5.K Code Execution
  • 5.L File Ops + Patches
  • 5.M Mixture of Agents
  • 5.N Misc Operator Tools
  • 5.O Hermes CLI Parity
  • 5.P Docker / Packaging
  • 5.Q API Server + TUI Gateway Streaming
  • 5.R Code Execution Mode Policy
PLANNED · 0/6

Phase 6 — The Learning Loop (Soul)

  • 6.A Complexity Detector
  • 6.B Skill Extractor
  • 6.C Skill Storage Format
  • 6.D Skill Retrieval + Matching
  • 6.E Feedback Loop
  • 6.F Skill Surface
IN PROGRESS · 2/5

Phase 7 — Paused Channel Backlog

  • 7.A Signal Adapter
  • 7.B Email + SMS Adapters
  • 7.C Matrix + Mattermost Adapters
  • 7.D Webhook + Trigger Ingress
  • 7.E Regional + Device Adapter Backlog

30/73 shipped · Full progress tracker →