Status

rensei status is a single command that aggregates the four health signals most relevant to an operator: authentication, local daemon reachability, platform visibility of this host, and org-level capacity. It is the recommended first diagnostic step when something isn't working.

Usage

rensei status
rensei status --json

What it checks

rensei status runs four checks in sequence:

Auth + WhoAmI - Verifies your active context has a valid token and can reach the platform API. Calls the /api/cli/whoami endpoint.

Local daemon reachability - Attempts to connect to the daemon on 127.0.0.1:7734. Reports the daemon version, uptime, and current session count if reachable.

Platform host visibility - Calls /api/cli/capacity to confirm this machine is registered and visible to the platform. A daemon that is running locally but not visible to the platform usually means the registration token has expired or the daemon hasn't checked in recently.

Org capacity summary - Retrieves aggregate capacity across all registered hosts in your org: total hosts, total concurrent session slots, and on-demand provider availability.

Example output

Healthy:

Auth          ✓  mark@acme.com (user context, acme-corp)
Daemon        ✓  127.0.0.1:7734  v0.8.3  idle  2 sessions available
Platform      ✓  host visible  pool: local-acme-corp
Capacity      ✓  4 hosts  ·  12 total slots  ·  on-demand: e2b (available)

No issues found.

Daemon not running:

Auth          ✓  mark@acme.com (user context, acme-corp)
Daemon        ✗  connection refused on 127.0.0.1:7734
Platform      ✗  host not visible (last seen: 4h ago)
Capacity      ✓  3 other hosts  ·  8 total slots

Issues:
  • Daemon is not running. Run it with: rensei host run (or via launchctl/systemctl)
  • This host is not visible to the platform. Run: rensei host install

Auth failure:

Auth          ✗  token expired or invalid
Daemon        -  (skipped - auth required)
Platform      -  (skipped - auth required)
Capacity      -  (skipped - auth required)

Issues:
  • Re-authenticate: rensei auth add --user

JSON output

Use --json for machine-readable output suitable for monitoring scripts:

rensei status --json

{
  "auth": {
    "ok": true,
    "email": "mark@acme.com",
    "kind": "user",
    "org": "acme-corp"
  },
  "daemon": {
    "ok": true,
    "addr": "127.0.0.1:7734",
    "version": "0.8.3",
    "sessions": {
      "active": 0,
      "available": 2,
      "max": 2
    }
  },
  "platform": {
    "ok": true,
    "hostVisible": true,
    "pool": "local-acme-corp"
  },
  "capacity": {
    "ok": true,
    "hosts": 4,
    "totalSlots": 12,
    "onDemandProviders": ["e2b"]
  },
  "issues": []
}

Exit code is 0 if all checks pass, 1 if any check fails - useful for CI health gates:

rensei status --json || echo "Rensei environment is unhealthy"

Diagnosing specific problems

Symptom	Likely cause	Next step
Daemon check fails	Service not running	`rensei host run` (foreground) or start via `launchctl`/`systemctl`
Platform check fails with "not visible"	JWT expired, daemon offline `>` platform heartbeat window	`rensei host install` to re-provision token
Auth check fails after upgrade	Token cache stale	`rensei auth remove <name>` then `rensei auth add --user`
Capacity shows 0 slots	`maxConcurrentSessions` is 0 in daemon config	`rensei host capacity set capacity.maxConcurrentSessions 2`

For deeper daemon diagnostics, use:

rensei host doctor
rensei host logs --follow

Host daemon - daemon install, start, doctor, and logs
Fleet - view all hosts in your org
Global flags - --json, --org, --auth

Usage

What it checks

Example output

JSON output

Diagnosing specific problems

Related

On this page