Command Overview

All Dorgu CLI commands at a glance

Command tree

dorgu
├── generate [path]         Analyze app and generate K8s manifests
├── init [path]             Initialize dorgu configuration
├── config                  Manage configuration
│   ├── list                List all config values
│   ├── get <key>           Get a single config value
│   ├── set <key> <value>   Set a config value
│   ├── path                Show config file path
│   └── reset               Reset to defaults
├── persona                 Manage ApplicationPersona CRDs
│   ├── generate [path]     Generate persona YAML from local source
│   ├── apply [path]        Apply persona to cluster from local source
│   ├── import              Create personas from Deployments already running
│   ├── status <name>       Check persona status
│   └── list                List personas across namespaces
├── cluster                 Manage ClusterPersona CRDs
│   ├── init                Create a ClusterPersona
│   ├── status [name]       View cluster status
│   ├── setup               Install production-ready stack
│   └── info                Show access details for installed stack components
├── watch                   Real-time streaming (WebSocket)
│   ├── personas            Watch persona updates
│   ├── cluster             Watch cluster updates
│   ├── events              Watch validation events
│   ├── incidents           Watch IncidentMemory updates
│   └── remediations        Watch RemediationAction updates
├── sync                    Query operator state
│   ├── status              Show sync health
│   └── pull                Pull latest persona data
├── health                  Show cluster health summary
├── incidents               Manage and view cluster incidents
│   ├── list                List incidents
│   └── describe <name>     Show incident details
├── remediation             Manage remediation proposals
│   ├── list                List remediation proposals
│   ├── diff <name>         Show the proposed change
│   ├── approve <name>      Approve a pending remediation
│   ├── reject <name>       Reject a remediation proposal
│   └── heal <name>         Apply an approved remediation to the workload
├── platform                Platform management
│   └── serve               Start web UI dashboard
└── version                 Show version info

dorgu incidents has only list and describe — there is no history subcommand.

Command reference

The command tree above is a plain listing. Use these links for the full flag reference on each command group.

Command	Reference	What it does
dorgu generate	generate	Analyze an app and generate Kubernetes manifests
dorgu init	init	Initialize app, workspace, or global configuration
dorgu config	config	Read and write configuration values
dorgu persona	persona	Generate, import, apply, and inspect ApplicationPersona CRDs
dorgu cluster	cluster · cluster setup	Manage the ClusterPersona and bootstrap a cluster stack
dorgu watch	watch	Stream personas, cluster, events, incidents, and remediations
dorgu sync	sync	Query operator state
dorgu health	health	Cluster health summary
dorgu incidents	incidents	List and inspect detected incidents
dorgu remediation	remediation	Review, approve, reject, and apply proposed fixes
dorgu platform	platform	Serve the v0 web dashboard. Deprecated
dorgu version	version	Show version info

Global flags

These flags apply to all commands:

Flag	Description	Default
--config	Path to config file	.dorgu.yaml
--no-color	Disable colored output	false
--json	Output as JSON	false

Path argument

Commands that accept a [path] argument default to the current directory (.) when omitted. The path should point to a directory containing a Dockerfile or docker-compose.yml.

Prerequisites

Every command that touches a cluster shells out to kubectl, so it must be on your PATH and your current context must point at the target cluster. Without it those commands fail with kubectl not found in PATH. Only generate, init, and config work with no cluster at all.

Set DORGU_DEBUG=1 to see kubectl’s raw output in error messages. By default the CLI strips klog noise (the memcache.go:265 "Unhandled Error" lines) so the message that says what went wrong is not buried.

Exit codes

Code	Meaning
0	Success
1	Error: the command could not run. An unreachable cluster, a missing kubeconfig, no kubectl, a failed API call.
2	dorgu health --exit-code only: active critical incidents
3	dorgu health --exit-code only: health could not be judged
4	dorgu remediation approve / heal only: declined by design. Dorgu understood the plan and chose not to write, because something else owns the workload. Nothing failed and nothing changed.

Codes 2 and 3 are opt-in and specific to dorgu health. An unknown subcommand is an error with a non-zero exit, not a help dump.

4 is a decision, not a failure. A wrapper that treats every non-zero exit as breakage will report a successful refusal as an error. Accept 4, or use --no-heal, which records the decision without a workload patch and exits 0. See the ownership model.

Getting help

# General help
dorgu --help

# Command-specific help
dorgu generate --help
dorgu cluster setup --help
dorgu persona import --help