Ekamyth Agent OS docs
Help / Stop or undo

Stop or undo Ekamyth Agent OS

The switches that stop model calls, turn parts of Agent OS off, or take it out of your agents, and how to undo each one.

Stop or undo Agent OS at a glance

ToRun or setTo undo
Stop every model call through the model gatewayHERO_KILL=1 for the model gateway, then restart itUnset it and restart
Cap model callsHERO_MAX_CALLS=<n> for the model gateway, then restart itUnset it and restart
Turn one rule offhero codify off <rule>hero codify on <rule>
Stop all your rules from refusing, once enforcement is onhero codify enforce off, or HERO_CODIFY_ENFORCE=0hero codify enforce on, or unset it
Turn routing offHERO_ROUTE=0Unset it
Turn session memory offHERO_BRAIN_SESSION_MEMORY=offUnset it
Take Agent OS out of your agentshero setup --undohero setup, with a new install command from your account page

Run each one in your own terminal. For a variable the background services read, see How to set a variable.

Stop every model call

With HERO_KILL set to 1, true or yes, the model gateway refuses every model call before it reaches your provider. Your agent gets HTTP 403 with an empty body. Agent OS records the reason as blast_radius_deny: rate / quota / kill-switch limit. The model gateway reads the variable when it starts, so restart it after you set or unset it.

Tool calls your agent makes through its own tools are still checked by the hooks; this switch covers model calls.

Cap model calls

HERO_MAX_CALLS=<n> lets through at most n model calls of each kind of work, counted from when the model gateway started. A call over the cap gets the same 403 as above. The count starts again when the model gateway restarts. With the cap set, the model gateway also stops a kind of call that keeps failing: 5 provider failures in a row pause that kind of call, and a success resets the count.

Turn your rules off

The always-refused list stays on whichever you use. See How Governance works.

Turn routing off

HERO_ROUTE=0 (or false, no, off) turns routing off, over the choice stored on this machine: each call goes to the model your agent asked for, unless a saved model pin applies. See How routing works.

A saved model pin is the model chosen under Pinned in the Portal's Control › You › Models & subscriptions. Control is view-only, so you can't save a pin there. If a saved pin exists, then with routing off Agent OS serves it in place of the model your agent asked for, as long as it's a registered model from the same provider that your allowed models and policy permit. If the saved pin can't be read, the call is refused.

Turn session memory or capture off

HERO_BRAIN_SESSION_MEMORY=off stops session memory at session start. HERO_BRAIN_CAPTURE_OFF=1 stops saving facts from prompts that start "Remember that". See How the Brain works.

Take Agent OS out of your agents

This command will:

  • Remove the model address, the hook entries and the Agent OS commands setup put in your agents, and put back any value setup replaced.
  • Drop this machine's activation, so a later setup needs a new install command from your account page.
  • Leave the rest of your Agent OS data in place.
hero setup --undo

To remove Agent OS completely, see Remove Agent OS.

Your agent can't pull these switches

When your agent runs hero setup --undo, hero codify off or another command that switches off your rules, the hooks refuse it: only you can, from your own terminal. Your agent also can't make a lasting change to HERO_CODIFY_ENFORCE or the other variables that switch rules off, and setting one inside a tool call doesn't affect the hooks. See What your agent can't change.

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