The agent model

Every vault trades through a protocol-set agent wallet driven by a thin, order-only gate:

• The gate accepts typed order parameters only. Raw signed payloads are rejected — there is no way to smuggle a value-moving action through it.
• The gate's whole action surface is: place order, trigger order, cancel, modify, TWAP start/cancel, leverage, isolated margin, scheduled cancel. Nothing else exists.
• The gate checks your manager standing on-chain on every request. If the vault rotates managers or the protocol blocks a manager, access ends on the next request.

Two channels appear throughout the UI:

• ⚡ via agent — instant, gate-signed trading actions.
• ⛓ on-chain — wallet-signed transactions you approve yourself (capital moves, watchlist registration, vault admin).

If the gate is ever unreachable, both the trade page and the cockpit's On-chain panel (Manage → Trade → On-chain) fall back to a direct, wallet-signed order path (managerTrade) — so you can always close or cancel, gate or no gate.

Setting and stopping the agent

The agent is protocol-set: provisioned once for your vault, not something you hold or rotate by hand (the Agent tab's Provision button asks the protocol to register it if creation didn't). Because it is order-only, a leaked agent key still can't move funds. Stopping one for good is an off-chain step — pause the vault and rotate the key at Hyperliquid; an on-chain "revoke" only clears the vault's record, since HyperCore has no deregister action.