← All projectsAI & agents / 09

Agent tooling

Hermes Operator Controls

Give an agent boundaries you can inspect.

PythonHermes plugin hooksJSONLVerification records
Hermes Operator Controls system architectureSYSTEM ARCHITECTURE

THE PROJECT

Plugin patterns for tool budgets, metadata telemetry and typed verification records.

Agent control is easier to reason about when limits and evidence are represented as explicit records. These plugin patterns count tool activity, check the next tool boundary and record verification results. Metadata-focused telemetry can describe behavior without copying full prompt or response content into the log.

  • Tool-budget checks at the next boundary
  • Hash-linked metadata event records
  • Typed verification and PASS gates

Original plugin work for the upstream Hermes agent. Tool limits do not claim to interrupt inference already in progress.

IN MOTION

Watch the project.

Give an agent boundaries you can inspect.Hermes Operator Controls: budgets, telemetry and verification records.Text animation for the Hermes Operator Controls project: its tagline, then a numbered list of the six parts of the system, from hermes plugin hooks to operator gate, then the FutureInvoked end card with a one-line summary.

UNDER THE SURFACE

How it fits together.

Plugin hooks observe tool events. The budget controller gates subsequent tool actions, while telemetry and verification records support operator review.

Swipe or scroll the diagram to inspect it. The components are also listed below.

Hermes Operator Controls simplified architecture: Hermes plugin hooks; Budget controller; Tool boundary; Metadata events; Verification record; Operator gate
  1. 01
    Hermes plugin hooks

    Tool lifecycle events

  2. 02
    Budget controller

    Counts and configured limits

  3. 03
    Tool boundary

    Allow or halt next action

  4. 04
    Metadata events

    Hash-linked JSONL

  5. 05
    Verification record

    Typed result and evidence

  6. 06
    Operator gate

    Reviewable PASS decision

START WITH ONE EMAIL

Need something
like this?

Tell us what you would use it for. The four lines on the right are enough to start.
There is no form to fill in and nothing to sign up for.

Email the studiofutureinvoked@proton.me

WHAT TO PUT IN IT

  1. The taskWhat is done by hand today, and how often.
  2. The toolsWhere the data lives: files, sheets, apps.
  3. The resultWhat a good outcome looks like for you.
  4. The timingWhen you need it.
Write the email

The button opens your email app with the four questions already in the message. Examples: how to write a software brief.

Pricing on requestA quote is agreed before work beginsBased in CzechiaRegistered business: details on the imprint page →