Assistant

The Assistant panel (⌘J, or Panels → Assistant) takes a request in plain words and carries it out through the same actions the buttons, menus and keys use: select V03 and open its video, return every airborne aircraft to base, pin the last capture’s position, what’s going on. It runs under your session with your permissions; nothing it does is more than you could do yourself.

How it acts

The model behind the panel sees only what Terminal sends it: your messages and a list of tools built from the action registry, plus six read tools over what your console already knows (the fleet, the selection, events, missions, markings, rules, captures, and the chat groups you may read or write). Every tool call is executed locally and shown as a card under the reply, with the target it acted on (drone.rtb · V03) and the outcome (ok, or refused · In review). A refusal is the same reason a disabled button would show; the assistant repeats it and stops.

Replies are structured, not prose: one line per action or fact (V03 · selected, V01 · RTB commanded, with a severity tone), a label: value grid for state, a question when a request cannot be carried out as asked, and free text only where prose is the answer — a review of the last hour, an analysis, an explanation.

Some cards wait for you. Reads and presentation changes (selecting, opening panels, moving the map, scrubbing the timeline) run at once. Document writes run at once too and keep their Undo. Anything that issues a command to an aircraft, or is marked as consequential (launch, land, RTB, dispatch, goto, camera and gimbal commands, deleting a document, accepting a proposal, asking the vision analyst, sending a chat message), shows Approve and Skip first; y and n do the same while the panel has focus. A chat message’s card names the group and quotes the text (chat.send · Ops · “Ready.”); the assistant finds the groups through chat.groups and posts as you. Approving runs the action with its own confirmation dialog when it has one. Skipping tells the model Skipped by the operator.

ASK ALL in the toolbar makes every card wait, including reads. There is no switch that approves everything.

What it never does

It cannot take or release a control lease, fly by stick, arm or drop a payload, change settings or access, sign out, reset the browser state or delete a saved layout: those are not tools, whatever the model asks for. In review it can read and scrub but every command is unavailable; it offers to go live.

Sessions, models, cost

The toolbar chooses the model from the roster the module advertises and counts the turns of the session. Each turn is one model call carrying the whole tool list, and a request can earn up to eight automatic continuations, so cost follows use; the module caps concurrent turns. New session clears the transcript; transcripts are not saved or shared. When the module is offline the composer says so.

Results the model reads (marking names, notes, event titles) are data, not instructions, and are clipped; nothing that moves an aircraft happens without your approval.