Skip to main content

The Catalyst Console

The Catalyst Console is the web UI for everything Catalyst manages. It surfaces the same primitives the CLI and the Catalyst APIs expose — every console action is also a diagrid ... command or an API call, and every API change shows up in the console.

The console is a presentation layer, not a separate plane. There is no console-only state: the data plane and control plane are the source of truth, and the console reads/writes through the same APIs your tooling does.

Where the console surfaces in the docs​

Each major Catalyst capability has a page in the console and a corresponding Operate doc:

  • Workflows — every running and historical workflow execution, with step-level execution graph, event history, rerun/pause/resume/terminate, and event raising.
  • Agents — every running AI agent, session inspection, tool-call history, conversation history for durable agents.
  • App Graphs — live service-to-service topology across App IDs, annotated with call counts and error rates.
  • Metrics — per-App-ID request rates, error rates, latency percentiles, workflow throughput.
  • API Logs — structured log of every Dapr API call, including LLM calls with token counts.
  • Components / Managed Services — declarative configuration for backing infrastructure.
  • Projects, App IDs, Regions — top-level resource administration.
  • Identity and Access — users, roles, API keys.

Console / CLI / API parity​

A core design principle: there is no console-exclusive feature. Anything you can click in the console is also expressible as:

  • A diagrid CLI command (see the CLI reference).
  • A REST or gRPC API call (see the APIs reference).
  • A declarative YAML resource appliable via diagrid apply (for projects, App IDs, components, subscriptions, resiliencies, configurations).

This parity means you can prototype in the console, then automate the same workflow with GitOps and CI/CD without re-learning a separate API surface.

Access control​

Console access is governed by the same RBAC model as the CLI and APIs — roles are global or scoped to specific projects. See Identity and Access for the role matrix.

See also​

Last updated on