Tyr

InternalStage 1-3

The operator console for an autonomous coding harness built on the Hermes agent.

Fig 1 / 3A run: every tool call is a card with its status, command and duration
Per-turn context floor
−31%
Targets under 24 px
218 → 0
Browser-held keys
0

Internal system at Boost Capital, not public.

  • TypeScript
  • React 19
  • Tailwind CSS v4
  • TanStack Query
  • SSE
  • node:sqlite
  • Hermes Agent
  • Nx

About

Hermes supplies the agent loop, tools and API. Tyr is what a person needs to supervise it on real ticketed work: a live transcript with tool-call cards, an approval gate that ranks and explains risky commands, and pages for the agent's capabilities, memory, artifacts and scheduled jobs.

Highlights

  • Approval gate that ranks each request: independent detectors must agree before low and medium signals escalate, while trusted rules can fire alone, so no model can talk a dangerous command down.
  • The gateway key authorises a shell-capable agent, so it lives only in a dev-server proxy; checked with curl, 401 direct and 200 through the proxy.
  • Tool cards expand to the real command output, read from the agent's SQLite store opened read-only.
1 more
  • Typed Hermes client library; every error is mapped to a cause and a remedy, with retry per panel.

How it flows

From start to goal, the path the data takes

Request path

  1. Browser · holds no key
  2. Proxy · adds the key
  3. Hermes gateway
  4. Agent core
  5. Model

Approval

  1. Risky tool call
  2. Detectors agree
  3. Operator allows or refuses

Chat titles and ticket names are masked in these figures.