Dashboard Overview
The dashboard is the operator cockpit for Agirunner.
It is where you move from “the system exists” to “the system is doing useful work and I can see what is happening.”
It is also where operators stay connected to the orchestration layer as it steers workflows toward the best available conclusion. The dashboard is not separate from that loop. It is one of the main places where humans can see, guide, and review it.
That second part matters. Many agent systems provide a pleasant demo and then leave the hard questions unanswered: what is active right now, why did the system make this move, what output was actually produced, and where should a human intervene? The dashboard exists to answer those questions directly.
What Operators Do Here
Section titled “What Operators Do Here”- launch workflows from playbooks
- watch workflow state and work-item progress in Mission Control
- inspect task output, live console activity, deliverables, and history
- respond to approvals, rework, and steering moments
- configure specialists, skills, models, tools, and execution environments
- inspect logs, runtime posture, and live containers
- check the
Versionspopover aboveLogoutto confirm what platform and runtime images are actually running
Navigation Model
Section titled “Navigation Model”The dashboard is organized around the real control-plane surfaces:
- Mission Control for the live workflow rail, board, workbench, and operator actions
- Work Design for playbooks, workspaces, specialists, and shared skills
- Platform for model routing, orchestrator posture, execution environments, and tool policy
- Integrations for MCP servers, webhooks, and other external connections
- Diagnostics for raw logs, summaries, and live container inventory
- Admin for API keys and system-wide settings
This navigation is not arbitrary. It mirrors the actual operating model: define process, launch work, supervise progress, inspect evidence, configure system posture, and integrate with outside systems.
Why This Matters
Section titled “Why This Matters”Agirunner treats the operator surface as part of the product contract, not as a decorative shell around prompts and logs.
The dashboard is where you:
- decide what work to launch
- see how the orchestrator is routing that work
- intervene when a workflow needs review, guidance, or correction
- inspect evidence instead of guessing what the models did
How The Main Sections Connect
Section titled “How The Main Sections Connect”The dashboard is easiest to understand when you read it as one loop rather than as a set of unrelated menu items:
- Playbooks And Authoring and Workspaces define what kind of work the system should run and what context it should run against
- Specialists, Skills, And Models, Tools, MCP Servers, and Environments define who can execute the work and with what capabilities
- Workflows and Workflow Detail show the live state of that work
- Approvals And Needs Action and steering controls are where humans intervene when autonomy should not be the only decision-maker
- Diagnostics, Live Logs, and Live Containers provide the evidence trail that explains what actually happened
- Admin And Settings sets the global operating posture behind all of it
That flow is the product. The menu is just the most convenient way to reach each part of it.
The Best First Tour
Section titled “The Best First Tour”If you are new to the product, spend most of your time in this order:
- Workflows, because it shows the live operating model
- Workflow Detail, because it connects workflow state to evidence
- Playbooks, because it explains how process is authored
- Models and Environments, because they explain how the platform shapes runtime behavior
- Diagnostics, because it shows how execution evidence is exposed