Guides
Task-shaped pages — arm a venue, connect an agent, record a feed, replay a session, stop and liquidate, triage a stuck order. Each one is a thing you came here to do, start to finish.
Nine pages, each named for a task rather than a subject. Where the concepts explain how something works and the tutorials walk a worked example end to end, these answer "I need to do this now" — the steps, the gates in the way, and what it looks like when it went right.
Before anything reaches a real account
Arm one venue for demo
Two gates stand between a credential and a live socket, and the ceiling is the one consulted first.
Stop, liquidate, restart
What a stop leaves at the venue, what the kill switch does and in which order, and what a restarted node does and does not recover.
Triage a stuck order
The confirm-grace ladder, what a venue confirm can return, and which reconciliation divergence you are actually looking at.
Running it
Record a live feed
One TOML profile, one daemon, and a tape of the markets you actually watched — plus the two watchdogs that notice when it goes quiet.
Replay a recorded session
Two different replays: a market tape through the backtest engine, and a command journal through the real core.
Run a sweep on the data service
Ship a profile to the box that holds the history, run the grid next to the data, and get back only the ranked result.
Read a backtest report
Every row of the summary table, what the annualization factor actually is, and why a flat run prints what it prints.
Driving it from somewhere else
Connect an agent
Point an assistant at the MCP server: tools to author strategies, run backtests, watch a live node — and, behind a preview gate, place orders.
Control the daemon from Telegram
A second remote write surface, off at compile time, behind four gates and a mandatory confirmation.
Two of these can move real money
Arming a venue and connecting a write-capable control surface are the two places where a mistake reaches an account rather than a log. Both pages lead with what stops that, and both are worth reading through once before following.
Log volume
Why a long backfill or an open desktop window can write gigabytes of JSON log, and the knobs — VIKE_LOG_FILE_LEVEL, the file-level preference, and retention — that bound it.
Connect an agent
Point Claude at vike-cli mcp — 17 tools to author strategies, run backtests, watch a live node, and (behind a preview gate) trade.