A supervision review for an agent that keeps running

Supervising a persistent agent means reviewing its current authority, exposure, and decision record on a cadence appropriate to the strategy. Closing a browser changes none of those responsibilities. We would make supervision a short repeatable review whose questions lead to specific observations.

The pause and revoke guide explains that an agent continues autonomously and that pausing or revoking leaves existing positions and resting orders for separate management. This review addresses the live Hyperliquid alpha described in public documentation inspected October 3, 2026.

Before leaving it overnight

Illustrative handover: on Friday an owner expects an agent to review BTC and ETH over the weekend. There is one existing BTC position and a temporary event instruction. The owner writes a review note with three questions: what instruction remains active, what exposure already exists, and what the last completed turn actually decided.

The first question points to the saved strategy and confirmed instructions. Does the temporary event direction still apply? Chat discussion by itself does not make a persistent instruction active. Review proposals and saved state, especially after an interrupted conversation.

The exposure question points to account positions and resting orders. Include manually opened positions and other agents using the same account where relevant. The documented open-position cap counts the account's distinct symbols, including manual positions and pending entries, so a second agent's activity can affect what a new opening is permitted to do.

The decision question points to Activity and execution records. A completed no-trade turn and an execution failure need different responses. Read the reason before interpreting a quiet period.

A checklist with consequences

Use four items rather than an unbounded monitoring ritual:

• Confirm the selected account, saved strategy, and active instructions. Resolve contradictions before expecting consistent behavior.
• Review positions and orders against the intended exposure. Manage existing venue exposure separately if you stop future agent activity.
• Inspect recent completed turns and any failures. Follow the actual error to readiness, policy, data, or execution.
• Confirm the next evaluation context and your chosen observation cadence. Adjust supervision when the strategy's event sensitivity changes.

These are owner review choices, rather than a promise that every issue will appear in a particular alert. A missed notification also differs from a missing trading turn.

Review after a material change

If the owner approves a revised strategy, keep the before-and-after records tied to their settings. Our state and memory article explains the importance of current context. Our trace article connects that context to recorded decisions and outcomes.

For the fictional weekend agent, a successful handover is a note that identifies the current exposure, the remaining event instruction, and the response if either becomes inconsistent with the owner's intention. Its value comes from reducing ambiguity. Supervision can reveal a problem early; the review itself establishes no guaranteed maximum loss.