Ekamyth Agent OS docs
Agent OS documentation / Reference

Ekamyth Agent OS reference

Find the command for what you want to do, then every hero command with what it does and whether it changes anything.

Find by task

Each row is a task, the command or page for it, and what you'll see.

Set up and check

I want toUseWhat you'll see
Understand how Agent OS worksHow Agent OS worksYour agent, Agent OS on your machine, your provider, and what you get.
Install Agent OS and connect my agentsGet startedOne pasted line, then three checks.
Check that Agent OS is installed and healthyhero statusEight checks, each ✓ or ✗, and one next step.
Check that each agent is connectedhero setup --checkEach agent's connection to the model gateway.
Upgrade to a new versionThe install line, run againThe new version checked, switched to, and a roll back: line.
Launch my agent so its model calls go through Agent OShero claude, hero codexOne launch line naming the model gateway, then your agent starts.
Use Agent OS from inside my agentCommands inside your agentThe 12 /hero: commands in Claude Code and hero- skills in Codex, one line each.
Find the model gateway's address, or check it's upModel gateway addressThe address your agents use, and /healthz.
Take Agent OS out of my agentshero setup --undoYour agents' settings put back, and this machine's activation dropped.

Stop and control what my agent does

I want toUseWhat you'll see
Stop my agent from doing something my rules forbidA rule in your rules file, then hero init <file>Each rule, and whether it's checked as code. Once enforcement is on, it's refused, on Claude Code and for shell commands on Codex.
Stop one specific action nowYour agent's own permission settings (Claude Code permissions, Codex approval mode)Actions on the always-refused list are refused regardless.
See whether each of my rules is enforcedhero enforceEvery rule Agent OS knows, where it came from, and its state on Claude Code and on Codex.
See what was refused, held or allowedhero governRecent tool-call decisions, as ✗ refused, ⚠ needs approval or allowed. See How to read hero govern output.
Approve or deny an action my agent is waiting onhero inboxThe actions held for your decision. Only you can decide, from your own terminal.
Know the order Agent OS checks a tool call inThe order checks run inThe order of the checks on a tool call, and routing's order.
Stop every model call, or switch part of Agent OS off fastStop or undo Agent OSEach switch, and how to undo it.
See what may leave my machinehero privacyThe declared list, which flows are on, and what was recorded as sent.

Brain and context

I want toUseWhat you'll see
Have Agent OS remember a factA prompt that starts "Remember that ...", or hero brain noteOne line naming where the fact went and the command to undo it.
See what's in my Brainhero brain statusThe sections of your Brain, and when session memory was last given.
Check my Brain for problemshero brain doctorWhat's missing or broken, with the next step.
See which rules a session started withhero memoryWhich registered rules Agent OS gave each session at start.

MCP

I want toUseWhat you'll see
Understand how Agent OS works with my MCP serversHow MCP worksWhat Agent OS sees of your agent's MCP calls, and its limits.
Give my agent Agent OS's own MCP serverhero mcpYou add it to your agent's MCP configuration yourself. hero mcp never edits that configuration.

Routing and cost

I want toUseWhat you'll see
See which model answered each callhero routeWhich model served each call, and which calls moved.
Check which agents route through this installhero route censusEach agent surface, and whether its model calls go through the model gateway.
Turn routing offHERO_ROUTE=0Each call goes to the model your agent asked for.
See tokens by agent and sessionhero usageThe token report.
See what my agents' work costshero efficiencyWhat the work cost, what Agent OS saved, and the levers that would lower it.
See every efficiency leverhero efficiency listEach lever, with what it found.
Use my own rates instead of list pricesHERO_BILLING_RATESCost figures at your rates. Check the file first with hero efficiency billing <path>.

See what happened

I want toUseWhat you'll see
See what my agent did in a sessionhero traceSessions, with those that had problems first. hero trace show <id> replays one.
See policy violationshero trace violationsPolicy violations only, not failed steps.
Get one read of how my agents are doinghero healthFindings, most severe first, each with its fix.
See my agents' activity, cost and checks on one screenhero portal openMonitor in your browser, signed in. See How Monitor works.
See the record of what my agents did, and check ithero attestThe record kept on your machine, and whether it verifies.
See how each job endedhero verdictEach job's end state, judged by a watcher, not by the agent's own report.
Ask a question about what Agent OS recordedhero askAn answer, with the records it came from.
See or change the standing checkshero scheduleThe standing jobs, when each last ran, and its cadence.

Fix a problem

I want toUseWhat you'll see
Find out why something isn't workingTroubleshootingSymptoms, causes and fixes, starting with hero status.
Get help from supporthero supportA code to email to support@ekamyth.com, with the output you saw.

All commands

Every command with a page in these docs, in area order. "Changes" means it can change a setting, a file or a decision; see each page for exactly what.

CommandAreaWhat it doesReads or changes
hero setupConnectConnects Claude Code and Codex to Agent OS, after showing you its plan.--check and access read. The rest change your agents' settings.
hero runConnectLaunches your agent with its model calls going through the model gateway. Aliases: hero claude, hero codex.Changes no settings file. Starts the model gateway for the run when it isn't running.
hero proxyConnectStarts and manages the model gateway, which your agents' model calls pass through on your machine.--service-status and --restart-status read. The other forms start, install, restart or remove the model gateway.
hero statusConnectChecks that Agent OS is installed, active and connected to your agents, and names one next step when something's wrong.Reads only.
hero initSecurity and enforcementRegisters the rules in a rules file, and tells you which are checked as code.Changes the rules Agent OS checks. It never edits your rules file.
hero governSecurity and enforcementShows the tool-call decisions Agent OS made: refused, held or allowed.hero govern add changes your policy file. The other subcommands are status, list, check, level, init and test; see its subcommands.
hero enforceSecurity and enforcementLists every rule Agent OS knows, where it came from, and whether it's enforced on Claude Code and on Codex. hero codify still works: use it to turn a rule off or on.Reads only.
hero inboxSecurity and enforcementLists the actions Agent OS is holding for your decision, and approves or denies them.approve and deny decide a hold, only from your own terminal.
hero privacySecurity and enforcementShows what this install may send off your machine, and what it recorded as sent. Alias: hero audit.Reads only. A run may send the usage heartbeat.
hero contractSecurity and enforcementThe written data contract: every outbound flow, what it carries and how to switch it off.Reads only.
hero codify-policySecurity and enforcementYour switch for sending rules out for compilation: off, ask or default.Changes that setting.
hero brainBrain and contextShows, checks and adds to your Brain.status, effective and doctor read. note, undo and init change files.
hero brain threadsBrain and contextThe commands for saving a named checkpoint of work in a workspace, and for loading a saved checkpoint again.list, history and resume read. create and save add to your saved threads.
hero memoryBrain and contextShows which of your registered rules Agent OS gave your agent at session start, and simulates which would fit a budget.Doesn't change your rules or sessions.
hero mcpMCPServes Agent OS to your agent over MCP.See the page.
hero routeRoutingShows which model served each of your agents' model calls, and which calls moved.Reads only.
hero efficiencyEfficiencyShows what your agent work costs, and which levers would cut it. Alias: hero cost.Changes nothing in your work. Can send the usage heartbeat.
hero usageEfficiencyThe token report by agent and session.Reads only.
hero traceObserveShows what each agent session did. hero trace <id> is short for hero trace show <id>.Reads only.
hero attestObserveThe record of decisions kept on your machine, and a check that it's intact.Reads. export writes a file you name.
hero verdictObserveHow each job ended: done, failed or stuck, judged by a watcher, not by the agent's own report.The bare form reads. sweep changes job states.
hero healthObserveGives one read of how your agents are doing, with a fix for each finding.Reads your records. --html writes a report file and opens it.
hero askObserveAnswers a question from what Agent OS recorded, with the records it came from.Reads your records.
hero scheduleObserveLists the standing jobs Agent OS runs for you on a cadence, and lets you change a job's cadence or switch it on or off.list and --service-status read. The other forms change something.

Interface: hero portal opens the Portal, whose main screen is Monitor.

Other surfaces

The customer surfaces are the hero commands, the model gateway's local HTTP endpoints, the hooks hero setup installs, MCP, configuration and data files, skills and customer settings. Ekamyth's own server endpoints and the Portal's HTTP routes are not a supported API.

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