Agent settings
Review the card before launch and the saved settings whenever you change an active agent.
Identity and evaluation
Section titled “Identity and evaluation”| Setting | Meaning |
|---|---|
| Name | How you identify the agent in the workspace. |
| Account | The Hyperliquid execution account the agent trades. |
| Model | The reasoning model selected from the app’s available models. |
| Strategy | The agent’s written objectives and decision criteria. |
| Schedule | The regular evaluation interval. The current builder accepts 30 minutes to 4 hours. |
| Schedule instructions | Additional context for scheduled evaluations. |
| Status | Whether the saved agent is Active or Paused. |
A schedule is an evaluation interval, not a promise to place an order at each interval. Triggers can also initiate agent evaluations when supported market conditions are met.
Market access
Section titled “Market access”Market scope controls which parts of Hyperliquid’s market universe the agent may use: core markets, HIP-3 markets, or a selected HIP-3 DEX where available.
Within that scope, the symbol policy can allow all supported symbols, allow only listed symbols, or block listed symbols. The editor accepts one of these modes at a time. Use the market selector’s supported symbols rather than guessing names.
Trading limits
Section titled “Trading limits”In Agent settings, choose Edit and find Risk Limits. Save your changes to apply them.
| UI field | Controls |
|---|---|
| Max Entry Notional | The maximum notional value of an individual opening trade. |
| Max Position Notional per Symbol | The projected position notional allowed for a symbol when opening exposure. |
| Max open positions | The maximum number of distinct open symbols on the selected account, including manual positions and pending entries. |
| Re-entry cooldown (minutes) | How long to wait after a full close before opening the same symbol again on the selected account. |
| Total Entries per 24h | The opening-trade count allowed over a rolling 24-hour window. |
| Total Entry Notional per 24h | The opening-trade notional allowed over a rolling 24-hour window. |
Notional is the size of the exposure in USD terms. It is not the same as the margin committed or the maximum amount you can lose. Rolling limits are not calendar-day allowances.
Max open positions
Section titled “Max open positions”Enter a positive whole number, or leave the field blank for no limit. The cap counts distinct symbols across open positions and pending entries, including resting limit orders that have not filled. Adding an entry on an already-counted symbol does not use another slot. Reduce-only closing orders, stop losses, and take profits do not consume additional slots. Reducing or closing a position remains allowed by this limit. Lowering the cap below the current count does not force positions to close.
For example, with a cap of 1 and a BTC position already open or a BTC limit entry resting, the agent cannot open ETH or place an ETH limit entry. If BTC is already held, it can still increase, reduce, or close that position, subject to other policies. See Orders for order behavior. This is separate from the rolling 24-hour entry limit, which counts opening and increasing orders.
Re-entry cooldown
Section titled “Re-entry cooldown”Enter a positive whole number of minutes, or leave the field blank to turn the rule off. For example, 60 means one hour.
Any confirmed full close starts the timer, including a profitable exit, stop, manual close, or liquidation. During that period, the agent cannot open a new long or short position in the same symbol on that account. Other symbols are unaffected.
Partial closes do not start the timer. The rule permits increasing, reducing, and closing already-open positions, subject to other policies. The timer starts from the closing fill’s execution time; activity outside the app is recognized when its fills are received. Changing the duration applies to the last recorded full close immediately.
Configured policy fields and strategy text have different roles. The strategy guides the model; the policy checks constrain execution. Review the actual saved fields rather than relying on an instruction in chat.