Orchestrator Legacy
The Orchestrator panel is a single-box chat that hands your message to a backend orchestration run and streams the run’s output back into the panel. When the run identifies a set of points, it sends them back as a bag, which the panel creates and selects on the map.
Heads up
The Orchestrator predates the Composer and has a much smaller feature set: no mode selector, no attachments, no tool policy, no memories. Use the Composer unless you specifically want this panel’s orchestration graph and its run logs in the Narrator panel.
Where to find it
View > Agents > Orchestrator. It is also part of the Rich and Visual Brainstorming layout presets.
What it shows
The panel is a transcript above a text box. The transcript renders:
- Your message, then the run’s reply, streamed in as it arrives.
- Collapsible thinking and tool_use blocks when the run is executed by an agent runtime that emits them.
- A short badge when a bag comes back, giving the bag name, its point count, and the main concepts found across its points.
- A floating status pill above the input, showing the backend’s current status line while a run is in progress.
Controls
The whole interface is four things:
- The text box. Disabled and showing the placeholder Connecting to Orchestrator… until the WebSocket is open, then Ask the Agent anything….↵ sends, ⇧+↵ inserts anewline.
- The connection dot and label. Green Active when connected and idle, blue Orchestrating… while a run is streaming, orange Reconnecting… while it retries, red Offline otherwise.
- Narrator. Opens the Narrator panel, which shows the execution graph and per-step logs for the current run.
- Send. Same as pressing ↵. Disabled while disconnected or while the box is empty.
Earlier versions of this page documented a Narrator / Agent / Simple Coder mode dropdown and Clear Context Points, Visual Brainstorming, and Add Context buttons. Those belong to other panels; the Orchestrator has none of them.
How to use it
- Open the panel and wait for the dot to turn green. The text box stays disabled until the socket connects. If it stays red, the backend WebSocket is unreachable, and nothing you type will be sent.
- Type a request and press ↵. Every submit first clears the context points on every open map, so the map starts from a clean state.
- Watch the run. The status pill and the connection label report progress. Click Narrator to see which phase is running and what each step returned.
- Use the bag. If the run returns points, a bag is created on the map with the name the backend chose (or Analysis Result), its points are selected, and its badge appears in the transcript. Rename or clear it from the Bags panel like any other bag.
How the message reaches the backend
The panel opens a WebSocket to /ws/raw-chat/ on the backend host, derived from NEXT_PUBLIC_BACKEND_URL, then NEXT_PUBLIC_WS_URL, then the page’s own host. Each submit sends your user id, the space id, the map id, a fresh run id, and your text. The run itself is a Celery task whose progress is bridged back over Kafka, so a run that hangs is a backend worker or bridge problem, not a stuck browser.
If a bag comes back without a map id, the panel applies it to every map currently open in the space, not just the active one.
Limits
- Your selection is not attached. Only the text you type, plus the space and map ids, are sent. Points you have selected, bags you have highlighted, and documents you have open are not included in the request.
- Sending cancels the run in progress. A new message revokes the previous Celery task, so the earlier answer stops mid-stream.
- Turns are not linked. The panel sends a parent run id under a field name the backend does not read, so nothing in the payload ties one message to the previous one.
- No citation markers. The
[2:doc_id]citation format described in older documentation belongs to a different, disconnected socket. The live citation format is the Composer’s, rendered as numbered footnotes. - No file upload, no export, no message editing, no history reload. The transcript lives in memory for the session.