dorgu platform serve

Start the v0 web dashboard. Deprecated, and being replaced.

Deprecated. dorgu platform serve starts the v0 dashboard: a read-only view of ClusterPersona resources, written before the self-healing loop existed. It knows nothing about incidents, remediations, or approvals, which is now most of what Dorgu does.

It is being replaced by a rebuilt dashboard, dorgu-platform-v1, which is not released yet. There is nothing to install and nothing to point you at until it is, and these docs will not describe it before then. Two documented dashboards is worse than one.

The command still ships and still works. Nothing has been removed from the CLI. What has been removed is the eleven pages of documentation that described the v0 dashboard as a product, because they were describing something that is on its way out. This page is what remains, and it is deliberately just the flags.

Everything the loop does is on the CLI, which is the supported surface: dorgu health, dorgu incidents, and dorgu remediation.

Synopsis

dorgu platform serve [flags]

Starts a local web UI that visualizes ClusterPersona resources. The server watches them in the connected cluster and pushes updates to the browser over WebSocket. Once started, the dashboard is at http://localhost:PORT, port 8080 by default.

Flags

Flag	Type	Default	Description
-p, --port	string	8080	HTTP server port
--kubeconfig	string	$KUBECONFIG or ~/.kube/config	Path to kubeconfig file
--context	string	current context	Kubernetes context to use
-v, --verbose	bool	false	Enable verbose logging

Examples

# Default port
dorgu platform serve

# A custom port
dorgu platform serve --port 3000

# A specific kubeconfig and context
dorgu platform serve --kubeconfig ~/.kube/staging.yaml --context staging-cluster

# Verbose logging, for debugging
dorgu platform serve --verbose

What it does not show

Worth stating plainly, because the gap is the reason it is deprecated:

Not in the v0 dashboard	Read it here instead
Incidents and their root-cause diagnoses	dorgu incidents
Proposed remediations, their plans, and their diffs	dorgu remediation diff
Guardrail verdicts on a plan	dorgu remediation diff
Approving or rejecting anything	dorgu remediation approve
Which workloads have no persona and are therefore unwatched	dorgu health

Approval was never in the dashboard and is not a gap to be closed casually. Approving a remediation writes to a running workload with your credentials, so the review surface it happens on has to show the plan, the diff, the owner, and Dorgu’s own guardrail verdicts together. That is what dorgu remediation diff does today.

dorgu health

Cluster health, saturation, and what Dorgu cannot see

dorgu remediation

The supported review and approval surface