07 · Self Mode
Self mode manages the user's own Hyperliquid portfolio through the same deterministic execution boundary, without match custody, opponent state or settlement.
Readiness is explicit
- Authenticated Privy DID maps to the selected master wallet/account.
- Network, funds, account mode and agent registration are verified.
- Market metadata and portfolio snapshots are fresh.
- Risk policy and allowed instruments are visible; the player consents to the session behavior.
- No wager commitment or match record is created.
Observe → decide → gate → execute → reconcile
The scheduler—not the model—chooses cadence. Each turn references the context snapshot and policy version it used.
Two human inputs, one risk boundary
Steering text influences the next model context. Direct commands (bounded long/short where enabled, cancel, close, pause, Exit All) create auditable human intents and pass through policy. Pause suppresses new model risk; Exit All remains available and runs the deterministic flatten coordinator.
The server owns the session; the UI restores a snapshot
A client disconnect never becomes portfolio truth. The server records session mode/policy, current agent turn, open effects and last reconciled portfolio. Reconnect returns that snapshot plus subsequent events. If the agent runtime or platform restarts, it reloads persisted session state, reconciles exchange truth and only then resumes according to the user's persistence policy.
Stop, verify, report
- Stop scheduling new model turns and reject late outputs.
- Choose “stop managing” or explicit “Exit All” based on the user's command; do not silently flatten persistent portfolios.
- If Exit All: cancel opens, fetch fresh positions, submit reduce-only closes, reconcile until verified or escalate.
- Record the terminal session state, residual orders/exposure, latest equity and recovery actions.