Strategies
A strategy is whatever the chat writes for you that ends up running. It might be a market maker that quotes both sides of HYPE, a funding watcher that posts when a rate flips, or a one-line "go long BTC with a TP and SL." Same chat box, same flow; the shape of the thing you get depends on what you asked for.
What you actually do
- Open a chat. Describe the thing in plain English.
- fxyz writes the file, asks any clarifying questions, and shows it to you in the right pane.
- Read it (or don't — your call). Push back on anything you'd want different.
- Click Run.
That's the whole loop. There's no project to create, no entry point to configure, no environment to wire up. The chat is the project.
What gets written
Every chat has its own folder of files. The main one is usually called something like index.ts — that's the entry point. There may be a helpers.ts next to it if the chat decided to split things up, or extra data files if the strategy needs them.
You can:
- Read every file in the right pane.
- Ask for changes in plain English ("make the size 100 instead of 10", "log every fill", "exit at -1% drawdown").
- Edit them yourself if you want — the chat will pick up your edits next turn.
Knobs
Most strategies expose knobs at the top — named, typed parameters like coin, size, bps, maxLeverage. The chat will surface them as a form so you can tweak values without re-running a chat turn. Changing a knob and re-running uses the new value immediately.
A knob that asks for a coin will be pre-populated from the actual market list at the venue — no stale lists, no typos. A knob that asks for a price will pin its decimal places to the venue's allowed precision so the venue doesn't reject your order.
Logging and debug output
When a strategy runs, three streams come back to the UI:
- Plain log — what the strategy chose to tell you ("placed buy 0.5 BTC at 95000"). This is the main timeline.
- Errors — what went wrong. Visible in red, persisted alongside the log.
- Debug — verbose structured detail the chat itself can read back later when you ask "why did it stop?" You don't normally need to read this, but it's there.
If you ask the chat "what happened?" mid-run, it'll read the recent debug stream and explain.
What's next
- Bots vs Executors — which shape your idea fits.
- Running code — what happens when you click Run.
- Paper trading — test before you fire real orders.
- Dashboards — same chat box, used to build a live view instead of a trader.