Skip to content

rune whoami / status / version

Terminal window
rune whoami
rune whoami -o json

Shows 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: prod
Server: runed.example.com:7863
Server Version: v0.0.1-dev.40 (51e7782b)
Default Namespace: prod
Token: 29b******364
Status: Authenticated
Subject ID: fba66da0-98de-48b8-b5d3-ae5111900388
Name: alice
Policies: [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).

A namespace summary — what’s running, what’s degraded.

Terminal window
rune status
rune status -n prod
Services in default:
NAME STATUS SCALE
api Running 3
worker Running 5
echo Failed 1

Useful as a health check from a dashboard or shell prompt.

Terminal window
rune version # client + server
rune version --client # client only (skips the server probe)
rune version -o json # structured output: text | json | yaml
runed --version # the server's own version subcommand
Client:
Version: v0.0.1-dev.40
Commit: 51e7782b
BuildTime: 2026-05-13T03:23:51Z
GoVersion: go1.22.5
Platform: darwin/arm64
Server:
Version: v0.0.1-dev.40
Commit: 51e7782b
BuildTime: 2026-05-13T03:25:18Z
GoVersion: go1.22.5
Platform: linux/amd64

The 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.

A tiny on-call dashboard:

Terminal window
watch -n 5 'rune whoami && echo && rune status'