Gormes

§ 01 · OPEN SOURCE · MIT LICENSE

One Go Binary. Same Hermes Brain.

A static Go binary that talks to your Hermes backend over HTTP. scp it to Termux, Alpine, a fresh VPS — Gormes adds no runtime of its own on top of what Hermes already needs.

Install View Source
Gormes Gopher

1. INSTALL

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

2. RUN

gormes

Requires Hermes backend at localhost:8642. Install Hermes →

Deeper reference material lives at docs.gormes.ai →

§ 02 · FEATURES

Why a Go layer matters.

Single Static Binary

Zero CGO. ~16.2 MB. scp it to Termux, Alpine, a fresh VPS — it runs.

Boots Like a Tool

No Python warmup. 16 ms render mailbox keeps the TUI responsive under load.

In-Process Tool Loop

Streamed tool_calls execute against a Go-native registry. No bounce through Python.

Survives Dropped Streams

Route-B reconnect treats SSE drops as a resilience problem, not a happy-path omission.

§ 03 · SHIPPING STATE

What ships now, what doesn't.

IN PROGRESS · 2/3

Phase 1 — The Dashboard

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

Phase 2 — The Gateway

  • 2.A Tool Registry
  • 2.B.1 Telegram Scout
  • 2.B.10 Regional + Device Adapter Flood
  • 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.B.6 Signal Adapter
  • 2.B.7 Email + SMS Adapters
  • 2.B.8 Matrix + Mattermost Adapters
  • 2.B.9 Webhook + Trigger Ingress
  • 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.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.G OS-AI Spine: Skills Runtime
IN PROGRESS · 10/13

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
PLANNED · 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
PLANNED · 0/17

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
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

25/67 shipped · Full progress tracker →