Overview
Create one from Condor
Agents and the Condor chat use thecreate_grid_executor tool:
controller_id must be the session ID (see Session IDs).
Direction rules
side sets the direction. start_price is always the bottom of the range and end_price the top, for both sides. Condor rejects a grid whose prices are in the wrong order before anything is sent:
The Hummingbot API accepts
limit_price: 0, which turns the safety stop off. Through Condor that is only possible for a long grid, because 0 can’t be above the range.
Parameters
How the levels are built
The executor fits as many levels as both limits allow, and the tighter limit wins:- Capital:
total_amount_quotedivided by the per-level minimum. The minimum is the larger ofmin_order_amount_quoteand the exchange’s minimum order value, plus a 5% margin. - Spacing: the range
(end_price − start_price) / start_pricedivided bymin_spread_between_orders.
start_price to end_price, with the same capital at each. If only one level fits, it sits at the middle of the range.
Entry orders go to the levels closest to the current price first, in batches of max_orders_per_batch every order_frequency seconds, while fewer than max_open_orders are open. When a level’s entry fills, the executor places that level’s take-profit order at level price × (1 + take_profit) for a long grid, or level price × (1 − take_profit) for a short grid. When the take profit fills too, the level is free to trade again.
take_profit is per level. It is not a target for the grid as a whole.
How the grid stops
keep_position in the config changes only the limit_price case. Leaving the range on the winning side and reaching the time limit always close the position.
Stop loss and trailing stop
The Hummingbot API also accepts a gridstop_loss and trailing_stop inside triple_barrier_config. Both are measured on the open position’s P&L and always close the position at market (STOP_LOSS or TRAILING_STOP), even when keep_position is true.
create_grid_executor has no parameters for them, so a grid created from Condor has neither. Its losses are bounded only by limit_price and, if you set one, time_limit.
Stopping a grid
Stop the executor withstop_executor or POST /executors/{executor_id}/stop. The keep_position you pass with the stop decides what happens; the config value is not used:
keep_position=false(the default) cancels open orders and closes the accumulated position at market. Close typeEARLY_STOP.keep_position=truecancels open orders and keeps the position. Close typePOSITION_HOLD, orEARLY_STOPif nothing was held.
controller_id. See Position Handover.
Grid level states
Each level reports its own state:Via the API
Create the executor withPOST /executors/. triple_barrier_config is required and must contain take_profit. Order types are numbers and side is 1 or 2.
Grid vs position executor
Learn more
- Executors overview: saved defaults, lifecycle and the API
- Position Handover: what happens to a held grid position
- MCP Tools:
create_grid_executorandexecutor_defaults

