The operator console

The operator console is a native desktop app for driving and observing apomesh. This page launches it, connects it to your stack, and names the surfaces so you know where to look. The console guide is the deep walkthrough.

Prerequisites

• The stack running — see Install & prerequisites.
• bun for the dev app.

Launch it

From the repo root:

cd ui/control-plane
bun run dev:app

This serves the web view, builds the Rust bridge, and opens the native window. The first run compiles the bridge crate and is slow; later runs are incremental. Leave it running — it’s a live dev process.

On launch the console seeds and auto-connects to your local orchestrator (http://127.0.0.1:50051). A connection bar across the top shows the active endpoint and a live pulse while a session runs.

The four modes

A narrow nav rail down the left switches between four modes. Three of them (Execution, Catalog, Infrastructure) need a live connection; Settings is always available.

Execution is where you watch sessions run. It centers on the running session: a timeline of its events, an agent-tree graph showing the parent/child hierarchy as it spawns, and an inspector whose facets break the session down — the event stream (the raw trace), cost, tool calls, memory, conversation turns, HITL prompts, and the synthesized output or report. This is the surface the real-provider session lights up.

Catalog is the agent catalog and the Configure & Launch surface. You browse agents, publish them as fully pre-configured locked shapes, define and pick orchestration-strategy configurations, and launch a published agent by name — the launch form offers only the operational inputs (goal, budget, and a few posture knobs), because the shape itself is fixed at publish time.

Infrastructure is the running plumbing: the workers registered against the orchestrator, the provider profiles and credentials, the model catalog, the tools and MCP servers, the endpoints the console can connect to, and a provider playground for one-off chat requests.

Settings holds the local, connection-independent preferences — appearance, behavior, network timeouts, and an about panel.

What to try first

With a session dispatched (from the real-provider step), open Execution and watch the timeline and agent graph fill in live, then open the inspector’s cost and output facets. Then browse Infrastructure → Workers to see the worker that ran it.

Next

Write your first SDK dispatch.