Executors on the ticket
The order type dropdown on the ticket has more than Market and Limit: it also lists every executor you've built or forked that targets the current venue.
What an executor looks like on the ticket
When you select an executor in the dropdown, the ticket morphs. Instead of just "side, price, size" you see the executor's own form: whatever knobs the recipe needs (TWAP duration, ladder rungs, iceberg child size, TP/SL pair, etc.). Fill them in, click submit, and the executor runs.
A modal opens showing the executor's progress in real time: each child order, fills as they happen, a running tally of slippage and fees. When it's done, you see a summary of how many children fired, total filled, average price, and total cost. The process exits.
Where executors come from
Three ways an executor ends up in your dropdown:
- You built it. Open a chat, ask for "an executor that ladders into a long over N minutes." Once it's saved, it appears in the dropdown for the venues it supports.
- You forked one from Discover. Browse Discover → Executors, find a recipe you like, click Fork. It now lives in your workspace and shows up in the dropdown.
- Built-in ones. A handful of common shapes (ladder, iceberg, TWAP) come with fxyz out of the box.
Per-venue support
An executor declares which venues it supports. A "ladder into" recipe might work on every venue; a "use HL's bracket orders" recipe only on HL. The dropdown filters automatically, so you only see executors that support the venue you're on.
What's next
- Bots vs Executors: the difference between the two, and why one belongs on the ticket and one doesn't.
- Discover: find executors other people have published.