The cockpit
The three-rail terminal cockpit — research, markets, rewards — built for multi-hour operator sessions.
Axe's primary surface is a terminal application — a TUI cockpit, not a web dashboard. The choice is not aesthetic. A multi-hour market session with live tape, persistent thesis, and working memory is a workload terminals were built for and browsers actively fight against.
Three rails
The cockpit is organized as three vertical rails, each holding a different timescale of work:
| Rail | Timescale | Holds |
|---|---|---|
| Research | Hours | Active session, thesis, working notes, runbook references |
| Markets | Seconds to minutes | Order books, funding, odds, liquidity, active watches |
| Rewards | Continuous | Real-time AXE earnings, protocol activity, contribution credits |
You can collapse any rail when you don't need it. You can pin a single market or watch into a slot you don't have to scroll back to. The default layout assumes you are running one main session and watching the world from inside it.
Why a TUI
A cockpit that competes with browser tabs loses. Operators already live in terminals — for the order tools, the chain tools, the data tools. Axe joins that environment instead of asking you to leave it.
Three properties follow from the choice:
- Latency: keystroke to render is bounded by the local machine, not by a hosted control plane
- Composition: anything you can pipe into a shell can flow into an Axe session
- Ownership: your session, your memory, your runbooks live on your filesystem unless you explicitly share them
Slash commands
The cockpit's verbs are slash commands. /perps-open and /poly-open frame sessions. /markets, /price, /book, /funding, /oi, /odds, /liquidity, and /resolution read state. /watch arms a tripwire. /automations schedules work. /model and /login configure inference. /runbook shares your work with the protocol.
The full surface is in the CLI reference.
Watches and the alert plane
Watches are the bridge between an active session and a closed laptop. A watch is a structured tripwire: a market expression, a condition, and a delivery. When the condition fires, Axe wakes the session — or pages you, depending on how the watch was configured.
Watches are first-class objects. You can list them, mute them, retire them, and ship them as runbooks. Operators who run good watches earn protocol rewards when other operators adopt their tripwires.