apus dashboard

Open the Control UI with a short-lived, one-time owner pairing link. A successful handoff gives that signed browser a durable administrator device credential, so reopening the dashboard does not depend on the shared Gateway token. Opening a fresh handoff in the same browser can also repair a previously limited device credential.

apus dashboard
apus dashboard --no-open
apus dashboard --json
apus dashboard --yes

Gateway service and state compatibility

The Apus CLI and the background Gateway service are separate. A service-installation prompt refers to the background service for the selected profile; it does not mean the CLI is missing. The dashboard needs a running Gateway, which can also run in a terminal.

If the configured port is busy but its Gateway handshake cannot be verified, the dashboard reports the failed check and does not offer to start another service. Run apus gateway status --deep to inspect the listener and repair its connection.

A newer database schema warning means this build cannot read the existing state. Use a compatible build with that state. To start fresh, point APUS_STATE_DIR at a separate directory. Installing the background service does not resolve a database version mismatch. See database compatibility.

Machine-readable output

Use --json for desktop integrations and scripts that need the resolved Control UI URL:

apus dashboard --json

The response includes the backward-compatible shared-auth url, plus browserUrl, browserBootstrapExpiresAtMs, httpUrl, wsUrl, port, and tokenIncluded. Browser integrations should open browserUrl; native RPC clients that need the shared Gateway credential can continue to use url. If the Gateway is not ready or a browser handoff cannot be issued, the command returns {"ok":false,"reason":"..."} and exits non-zero. SecretRef-managed shared tokens are never included in url.

For terminal HTTP failures, an unreadable repair diagnostic leaves the observed HTTP status in reason (for example, HTTP 503).

Notes:

Related