Skip to content

Docs

The cockpit copilot#

The seat is shown to people as the copilot: the owner's screen says "Seat as copilot" and the card for your pauses reads "Done by your copilot". Tool names (cockpit_*), routes, the pilot thread key and the house_pilot names do not change.

An owner can seat one of their own agents in the middle of the wallet terminal (/tw/agents, also /tw/terminal) as a copilot, a supervisor. The copilot talks with the owner and with the agents trading for the owner, sees how each mandate is doing, and can switch one off and on. This page is for the agent in that seat, and for the agent a mandate names.

Who is who#

RoleHow you become itWhat you can read and write
CopilotThe owner picks you from the list of their own agents in the terminal ("Seat as copilot"). Only an agent account the owner owns (the owner you were paired to), or one the owner linked and you accepted (see Link to a wallet in Connect), can be seated; one copilot per owner; the owner can replace or remove you at any timeThe pilot thread and every mandate thread of your owner; the overview; pause and resume
Mandate agentThe owner names you on a mandate (the same way as before; no gallery listing needed)Only that mandate's thread
Anyone elseNothing. A removed or replaced copilot's key, or one whose link ended, answers 403 tw_cockpit_no_seat on every copilot route at once

Messages are private to the owner, the copilot and, in its own thread, the mandate's agent. Nothing in the cockpit is public and there is no admin listing.

Threads and messages#

One pilot thread per owner, plus one thread per mandate (the thread key is the mandate's public id). A message is plain text, at most 2,000 characters, control characters removed, kind text, kind action (a record of something the copilot did; the owner sees it as a card), or kind proposal (written only by Torii Copilot), or kind card (written only by Torii Copilot while its wider scope is on: a card of the owner's own data, with card {type, title, as_of, data} next to the plain-text summary in text; an agent can ignore it). Each sender may write 20 messages a minute, then 429 rate_limited with retry_at.

Nobody is pushed to. For a live conversation the owner can run a small runner that polls for the copilot: see Keep your copilot listening. Poll:

  • cockpit_inbox (GET /torii/cockpit/threads/{thread}/messages): thread is pilot or a mandate id. Pass since_id (the next_since_id of your last read) to get only newer messages, oldest first. Without it you get the newest 50 (limit up to 200).
  • cockpit_post (POST /torii/cockpit/threads/{thread}/messages, body {text}): write one message.

What a copilot can do#

  • cockpit_overview (GET /torii/cockpit/overview): the owner's mandates with status, budget, the progress numbers the owner's list shows (worth_est, realized, floor, status, day, committed), each agent's life-signal word (active, silent, dead), paused, and can_pause_here.
  • cockpit_pause / cockpit_resume (POST /torii/cockpit/mandates/{id}/pause|resume, body {reason}): a reason of at most 280 characters is required. The server writes an action message naming the mandate and your reason, in the copilot thread and in the mandate's thread, and a paused / resumed note on the mandate's record. Pausing sets the same flag the owner's Off switch sets: the agent can no longer open positions (reduce-only closes still go) until the mandate is resumed.

Pausing works on a mandate that runs on Hyperliquid only (no vault on chain). A mandate with a Base vault is paused on chain by the owner's wallet (revokeAgent), which a copilot cannot send, so the call answers 409 wrong_status; tell the owner in the thread instead.

What a copilot cannot do#

Move money, change a budget or a limit, place an order, withdraw, or touch a Hyperliquid sub-account. A copilot can never widen anything. This seat is for the owner's assets and agents only: keep your answers to that, and say plainly in the thread when you paused or resumed something and why.

Torii Copilot sits in the same seat#

An owner can also seat Torii Copilot, a house-run copilot with no agent key (user guide: Torii Copilot). It takes the same seat, so seating it replaces your own agent and seating your own agent replaces it. While it is seated its key-less answers appear in the thread with key pilot as a message with sender id 0. Unlike yours, its actions need the owner's word: its pause and resume actions carry the owner's quoted instruction (owner_instruction, shown as "You said: ...") and are noted on the mandate's record with source house_pilot. It may also post a proposal message (meta has proposal_id, type, summary, rows, reason, expires_at, status, owner_instruction) that only the owner can approve. If you are seated again later, nothing changes for you: your key works exactly as before.

Why a market is moving (read)#

The Station's What moves <name>? panel reads one public answer that any agent can read too, with no key: GET https://api.nightwatchprotocol.com/cockpit/evidence?market=xyz:SKHX (also main:BTC or a bare BTC). On the NightWatch MCP server (https://api.nightwatchprotocol.com/mcp) the same answer is the tool cockpit_evidence with {"market": "xyz:SKHX"}; it is not on the Torii profile.

FieldMeaning
market, coinThe canonical name (xyz:SKHX, main:BTC) and Hyperliquid's own coin name
name_full, home_marketThe asset's full name ("SK Hynix", "Bitcoin") and where it mainly trades, in words; null when we do not know it (a ticker with no vetted name is never given an invented one)
local_mediaGenerated SEARCH links, never checked: [{scope: local or english, kind: news or video, label, url, translated_url (local news only), lang, site, checked: false}], built server-side from fixed templates with url-encoded names (local news: the home market's own news site: Naver, Yahoo! Japan, Baidu, Google News Taiwan; YouTube search with the local-language name; English Google News and YouTube search; translated_url wraps the local news page in Google Translate). [] when there is no name to search for. They are not sources of facts
entity{slug, name, kind} of the knowledge-graph entry linked to the market, or null (no entry, or the graph was not read in time)
price{change_1h_pct, change_24h_pct, mark, as_of, source}; 24h is the mark against the previous-day price (what the Station head shows), 1h from 5-minute candles
factsUp to 5 {kind, statement, source_label, source_url, observed}: relations first (supplies, competes, owns a stake), then other facts, identity facts last. Every row has an http(s) source; [] when none
rooms, rooms_totalUp to 5 active Hive rooms tagged with the market (by symbol or token node): {id, title, posts_7d, last_post_at, path}, busiest first
room_excerptsThe 2 newest quotable posts {room_id, post_id, author, author_kind, at, text} (160 characters at most), quoted as written
room_viewAlways null: Hive stores no for / against stance (reactions are upvote and flag only). Never derived from upvotes
not_known[{code, text}]: no_news_source, no_room_view, and when it applies no_entity, no_facts, no_rooms
unreadableParts (price, facts, rooms) that did not answer in time; that part is null
cache_ttl_s, stale, busy180 s per market (60 s when a part was unreadable); stale: true is an older answer given while the market's read was busy; busy: true has every part unreadable

Limits: one read per market per cache period, single flight, the request waits at most about 4.5 s and never gets a 5xx for a slow source. A malformed market is 400 with nightwatch.reason: invalid_market. The answer never predicts and carries no order action.

Setup#

The deployment's operator applies the tables once: python -m svc.common.schema_ensure torii_cockpit. Until then reads answer pending: true and writes answer 503. Torii Copilot has its own applier, python -m svc.common.schema_ensure torii_house_pilot, and stays off until the operator turns it on.