Overview
An agent consists of five components:Instructions
The rules that define when and how your agent trades
Goal
Your strategic objective and risk parameters
Trigger
The schedule or signal that tells your agent when to run
Memory
Learning edge that tracks past trades and patterns to improve future
decisions
Wallet
A dedicated Hyperliquid wallet for the agent to trade with
How agents work
Execution cycle
Every time your agent’s trigger fires, it follows this sequence:- Query current state: Retrieve wallet balance, open positions, and recent performance
- Consult memory: Review past trades under similar conditions from the Learnings database
- Analyze market conditions: Pull macro, microstructure, price action, fundamentals, and sentiment data as needed
- Evaluate instructions: Determine whether entry, exit, or risk management criteria are satisfied, informed by both current analysis and historical outcomes
- Execute actions: Place orders, modify positions, or do nothing based on evaluation
- Record outcome: Log the reasoning, actions taken, and market state to the Learnings database for future reference
Dedicated wallets
Each agent gets its own Hyperliquid wallet. This keeps your agents isolated from each other and from your personal funds. The flow is:- Create your agent
- Generate a wallet for the agent
- Fund the wallet with USDC
- Activate the wallet
- Enable the agent
Memory and decision making
Unlike traditional bots that treat every market condition the same way, Gigabrain Agents build institutional knowledge from every trade. Before executing, your Agent reviews past trades under similar conditions, checking what worked, what didn’t, and why. What gets recorded:- Trade outcomes relative to initial analysis
- Market conditions when trades succeeded or failed
- Patterns in profitable vs. unprofitable setups
- Strategy adjustments made over time
Configuration
Instructions
Define your trading logic using natural language. Be explicit about entry criteria, position sizing, exit rules, and risk limits.View example instructions
View example instructions
Instructions are interpreted by the agent’s language model. Ambiguous phrasing may lead to unexpected behavior. Test new instructions with small position sizes.
Triggers
Choose how your agent decides when to run:| Type | How it works | Best for |
|---|---|---|
| Every 5 minutes | Runs on a fixed schedule | Scalping strategies |
| Every 15 minutes | Runs on a fixed schedule | Intraday momentum trading |
| Hourly | Runs on a fixed schedule | Swing trading setups |
| Every 4 hours | Runs on a fixed schedule | Position trading |
| Daily | Runs on a fixed schedule | Fundamental-based strategies |
| Alpha trigger | Runs when a matching signal is detected by the Alpha engine | Event-driven and signal-based strategies |
Monitoring
- Reasoning
- Learnings
- Changelog
Each agent run generates a trace showing:
- Current wallet state (balance, open positions, P&L)
- Market analysis across relevant domains
- Evaluation of entry/exit criteria
- Actions taken or reasons for inaction
Example strategies
Momentum breakout
Momentum breakout
Objective: Identify and ride explosive moves across any asset.
- Trigger: Every 15 minutes
- Analysis: Market State, Trenches, Price Movement
- Entry: High-conviction Alpha signal (>75% confidence)
- Position sizing: 5% of wallet per trade, 5x leverage
- Exit: Trailing stop at 2% below peak, manual review after 24h
- Risk limit: Maximum 3 concurrent positions
Macro-aligned swing trading
Macro-aligned swing trading
Objective: Take directional positions when technical and macro factors align.
- Trigger: Every 4 hours
- Analysis: Macro, Market State, Price Movement
- Entry: 4H chart setup + favorable risk regime + positive BTC correlation
- Position sizing: 10% of wallet, 3x leverage
- Exit: TP at +8%, SL at -4%
- Risk limit: No new entries during risk-off regimes
Protocol fundamentals
Protocol fundamentals
Objective: Trade based on on-chain metrics and protocol health.
- Trigger: Daily at 00:00 UTC
- Analysis: Fundamentals, Market State
- Entry: Daily protocol fees >$3M, TVL increasing week-over-week
- Position sizing: 10% of wallet, 2x leverage
- Exit: Hold until fundamentals deteriorate or -10% SL
- Risk limit: Maximum 2 protocol-based positions
Best practices
Start conservative
Use small position sizes (1-5%), set tight stops, and monitor the first 10-20 reasoning traces closely before scaling up.
Iterate based on learnings
Review the Learnings tab weekly to identify failure modes, optimal conditions, and opportunities to refine entry criteria.
Use daily caps
Set profit caps at 2-5% of wallet value to prevent overtrading and lock in gains.
Monitor macro regime
Reduce position sizes during high VIX, avoid mean-reversion in trending Fed policy, pause during major geopolitical events.
Export keys regularly
Back up your agent wallet’s private keys. If you ever need to delete an agent, you’ll need the keys to recover funds.
Review reasoning traces
Regularly check traces to verify correct interpretation and identify edge cases in your strategy logic.
Troubleshooting
Agent not executing trades
Agent not executing trades
Possible causes:
- Agent is not enabled (check agent state is “Online”)
- Wallet is not activated or funded
- Entry criteria are not being met (review reasoning traces)
- Daily cap has been reached (check recent P&L)
- Risk limit has been triggered (check wallet balance vs. floor)
Unexpected trade execution
Unexpected trade execution
Possible causes:
- Instructions are ambiguous (refine phrasing and test again)
- Market conditions changed rapidly between trigger intervals
- Market data was stale or delayed
- Edge case not covered in your instructions
Performance degradation
Performance degradation
Possible causes:
- Market regime has shifted (e.g., trending to range-bound)
- Strategy has attracted attention (edge degradation)
- Position sizing is too large for current volatility
- Stop losses are too tight for current ATR
Limitations
Execution latency
Execution latency
Agent actions are subject to trigger interval (minimum 5 minutes), API latency to Hyperliquid, order processing time, and network conditions. Do not use agents for strategies requiring sub-minute execution.
Market conditions
Market conditions
Agents cannot predict unexpected events (exchange outages, liquidity crises), guarantee fills at expected prices during volatile markets, or prevent slippage on large orders in illiquid markets.
Model limitations
Model limitations
The language model may misinterpret ambiguous phrasing, cannot execute logic requiring external data not available through its tools, and has a knowledge cutoff. Review reasoning traces to verify correct interpretation.