Data And Control Surfaces
Agirunner exposes several distinct surfaces, and they are not all meant for the same audience.
Some are operator-facing. Some are integrator-facing. Some are internal execution surfaces that the rest of the product depends on. Knowing which surface you are looking at makes the rest of the system much easier to understand.
Dashboard
Section titled “Dashboard”The operator UI for launching work, inspecting workflows, reviewing outputs, and intervening when needed.
This is where human judgment lives. It is the place for launches, approvals, workflow inspection, logs, settings, and review.
Platform API
Section titled “Platform API”The control-plane API for workflows, tasks, playbooks, logs, artifacts, workers, runtime settings, and integrations.
If another system needs to create work, read workflow state, or monitor execution through a durable contract, this is the surface it should use.
Runtime
Section titled “Runtime”The execution plane that consumes platform-issued contracts and performs the work.
The runtime is usually not the primary integration surface for product consumers. It is the execution system behind the control plane.
Artifacts And Logs
Section titled “Artifacts And Logs”The evidence layer for understanding what happened during execution.
These surfaces matter because a workflow system becomes hard to trust if it cannot show what actually happened, what files were produced, and where a decision came from.
External Protocols
Section titled “External Protocols”Agirunner also exposes protocol surfaces such as A2A and ACP, and supports remote MCP integration in the platform and runtime stack.
Those protocol surfaces matter when Agirunner participates in a larger tooling ecosystem instead of acting as a closed dashboard-only product.