intropy dashboard

Authoritative reference for intropy dashboard: the local integration dashboard.

The dashboard is a local web view over the same records and commands the CLI exposes: the integrations and Systems scaffolded under a directory, and their deployment state via deploy status. It is served from the CLI itself, starts no integration processes, and reads nothing it could not read from the terminal. Running a System locally is the System host’s job (dotnet run), not the dashboard’s.

The surface

intropy dashboard [dir] [flags]

intropy dashboard

Start a local web dashboard that visualizes the integrations and Systems scaffolded under dir (default: the current directory): their template, pinned source, version, scaffold values and System topology. The dashboard opens in your browser; press Ctrl+C to stop.

Flag	Description
-p, --port <port>	Port to bind. Default 8730; 0 picks a free port.
--no-browser	Do not open the dashboard in a browser.
--template-version <tag>	Template release tag. Defaults to the latest release.

intropy dashboard ./integrations

Deployment state

Selecting an integration runs deploy status for it and renders the environments as a ladder, in the same promotion order and with the same consistency sentence beneath them. It is the command’s own output, decoded rather than recomputed, so the two cannot disagree about the same overlays.

Two consequences of that being a command rather than a file read:

• State is read on selection, not on page load. Reading deployment state refreshes the cached GitOps checkout under the same exclusive lock deploy takes, so the dashboard asks for one integration at a time, reuses the answer, and re-runs only on Refresh. Nothing polls in the background.
• Every refusal reaches you verbatim. An unconfigured gitopsRepo, an ambiguous component name, a checkout another deploy is using — each is shown as the command worded it, never rendered as an empty ladder (which would read as “not deployed”).

Sync and health are the only columns that come from ArgoCD. Without a usable token they are left out entirely and the panel says why: not being able to reach the cluster says nothing about what the overlays pin.