Ekamyth Agent OS docs
Standard OS / Processes

How Monitor works

Monitor is the Portal's main screen. It shows what your agents did, what their work cost, and how Ekamyth Agent OS's checks are doing, from the records Agent OS keeps on your machine.

How does Monitor work?

Monitor is one screen in your browser that reads the records Agent OS keeps on your machine: model calls through the model gateway, tool-call decisions from the hooks, sessions and checks. You open it with hero portal open, pick a tab, and click into any figure to see what's behind it. It shows only your own activity.

Monitor concepts

How you use Monitor, step by step

  1. Open it. Run hero portal open on the machine where Agent OS runs. Your browser opens the Portal, signed in.
  2. Start on Overview. Monitor opens on the Overview tab unless the address names another tab.
  3. Pick a tab for the question you have. See The tabs.
  4. Drill into a figure to see the records it was built from. The detail view has its own tabs: Usage, Routing, Reliability, Outcomes, Evidence, Governance and Traces.
  5. Choose a time window. Overview offers 24h, 7d and 30d. Telemetry offers Live snapshot, This week, Last week and Last month.

The tabs on Monitor

TabWhat it answersWhat it shows
OverviewMaturity, value and attentionYour use against your allowance, and what was saved and could still be saved.
HealthIs each capability working right nowOne tile per capability.
TelemetryWhat your agents' jobs didSearch everything, and a list of jobs. Each row: a readable title, who and which session, how it ended, and how it was routed. Below it are the detail views: Usage, Routing, Reliability, Outcomes, Evidence, Governance and Traces.

What Monitor shows, and what it leaves out

Monitor data, and what leaves your machine

Monitor reads the records Agent OS already keeps on your machine; see Data files. It runs at 127.0.0.1, so it's reachable only from this machine. Monitor's own tabs only read those records. Other Portal features can send data: a chat in the Portal passes your messages and system context through the model gateway to the model you picked, and testing a provider key contacts that provider. For what Agent OS as a whole sends, see How Privacy works.

When part of Monitor fails

What failsWhat you seeWhat to do
The Portal isn't runninghero portal open: no running portal to open — start it: hero portalRun hero portal, or hero portal --install-service.
The Portal's files are missinghero portal exits 3 and says to reinstall.Reinstall Agent OS.

What you can change in Monitor

SettingDefaultWhere
The Portal's port7878hero portal --port or HERO_PORTAL_PORT
Keep the Portal running after a restartOn, from the installerhero portal --install-service
The time window7d on Overview, and This week on TelemetryOn the screen

See Monitor for yourself

hero portal --service-status
hero portal open

Monitor limits and next steps

LimitBehaviourCan you change it?What to do
Outcomes and EvidenceA note, not figures.NoUse hero trace for what each session did.
Whose activityOnly your own.NoNone.
Where you can open itOnly on this machine.NoNone.
Counts that differ from the commandsRule coverage can show 0 while hero enforce lists your rules. The pending-approvals count can differ from hero inbox. Governance decision tiles and block counts can differ from the CLI. The Enforce table can show 0 for a rule that has already stopped calls. Monitor can say nothing is enforcing your budget while Control says Enforced.NoTrust the command: hero inbox for approvals, hero attest rules for block counts, hero govern status for enforcement, and Control for your budget.
✓ governed in Recent receiptsThe tick means Agent OS allowed the call, not that it succeeded. A call the provider rejected, for example at a rate limit, can still show it.NoTrace and Telemetry show the call as failed.
Open traceMonitor's Open trace can show no steps while hero trace shows them.NoUse hero trace show <session>.

Checked against Agent OS 0.1.36rc14 (build 599c5e120c18) on 17 Nov 2026.