rune whoami / status / version
rune whoami
Section titled “rune whoami”rune whoamirune whoami -o jsonShows the active context, the server, the configured namespace, the (masked) token, whether the connection works, the server’s version, and — if authenticated — the subject ID and attached policies.
Current Context: prodServer: runed.example.com:7863Server Version: v0.0.1-dev.40 (51e7782b)Default Namespace: prodToken: 29b******364Status: AuthenticatedSubject ID: fba66da0-98de-48b8-b5d3-ae5111900388Name: alicePolicies: [readwrite]If Status: Not connected to server, run rune login again or check that the server is reachable. The Server Version line is omitted on older servers that don’t expose HealthService.GetServerVersion (added in v0.0.1-dev.38).
rune status
Section titled “rune status”A namespace summary — what’s running, what’s degraded.
rune statusrune status -n prodServices in default:NAME STATUS SCALEapi Running 3worker Running 5echo Failed 1Useful as a health check from a dashboard or shell prompt.
rune version
Section titled “rune version”rune version # client + serverrune version --client # client only (skips the server probe)rune version -o json # structured output: text | json | yamlruned --version # the server's own version subcommandClient: Version: v0.0.1-dev.40 Commit: 51e7782b BuildTime: 2026-05-13T03:23:51Z GoVersion: go1.22.5 Platform: darwin/arm64Server: Version: v0.0.1-dev.40 Commit: 51e7782b BuildTime: 2026-05-13T03:25:18Z GoVersion: go1.22.5 Platform: linux/amd64The build is tagged with the git commit and build timestamp. If you see -dirty in the version, the binary was built from uncommitted changes.
The server probe uses the unauthenticated HealthService.GetServerVersion RPC (added in v0.0.1-dev.38) so it works before rune login. Against older servers, or without a configured context, you’ll see a one-line note instead of the Server: block; use --client to skip the probe entirely.
Combining
Section titled “Combining”A tiny on-call dashboard:
watch -n 5 'rune whoami && echo && rune status'