AI Agent OSGuarded mainnet beta. .rama identity, smart wallets, sponsored gas, permissions and scheduling are available for controlled testing.Open Agent OS
Learning center

AI Agent OS

Human-in-the-Loop Onchain Automation

Use human review where risk, value or ambiguity makes fully autonomous execution inappropriate.

In this guide

Practical outcomes

  • Classify risky actions
  • Insert review points
  • Measure automation safely

How this works in practice

Use human review where risk, value or ambiguity makes fully autonomous execution inappropriate.

A controlled agent separates the controller from the runtime. The controller owns the agent identity and defines policy, while a smart wallet, permission rules, quotas, relayer and scheduler constrain what the runtime can actually execute.

Implementation sequence

Turn the topic into a controlled implementation rather than a one-off transaction. Each step below should leave evidence a teammate, user or auditor can independently review.

  1. 01. Classify risky actions. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  2. 02. Insert review points. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  3. 03. Measure automation safely. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.

Evidence to retain

Record the .rama identity, controller, wallet, policy version, approval event, task identifier and resulting transaction hash. This makes a decision traceable without giving the agent unrestricted custody.

Control point

Start with small allocations, explicit recipient and contract allowlists, bounded session keys and a tested pause path. An automated workflow must never be the only place where authority or recovery knowledge exists.

Related guides