Skip to main content
infercrane ui opens an interactive operations workspace backed by the same authenticated control-plane API and durable operations as the scriptable CLI.
The workspace complements commands and JSON output. Use it for investigation and deliberate operator actions; use normal commands in automation, CI, redirected output, and agent workflows.

​
Product views

Use ← and → to change views, or press 1–7 to jump directly. Navigation uses compact labels on narrow terminals and adds a contextual workspace column on ultrawide terminals. On the Events view, use j and k to inspect full historical details. Old events remain visible but are separated from live health so historical failures do not look like current incidents.

​
Safe actions

Press Ctrl-K or : to open the action palette. InferCrane only shows actions applicable to the selected deployment and persisted state. Direct guarded actions include:
  • cooperatively cancel an active durable operation
  • evaluate Release Guard for the current candidate
  • promote only when the current candidate has a persisted accepting Guard decision
Every mutation shows its impact, requires a second confirmation, uses an idempotency key, and queues a durable control-plane operation. Release Guard evaluation explicitly warns that measured candidate traffic may incur provider cost. Closing the terminal never cancels queued work. Complex authoring remains a CLI handoff. The palette copies exact commands for test requests, reproducible benchmarks, and semantic capacity plans. Candidate creation, rollback, rejection reasons, deletion plans, and administrative workflows remain explicit CLI/spec operations where inputs and diffs are easier to review.
Promotion is unavailable when an evaluation is missing, rejecting, or belongs to a previous candidate. InferCrane never treats historical acceptance as permission to promote a new revision.

​
Read-only environments

Start the same workspace with mutation controls disabled:
The action palette retains copyable command handoffs but cannot construct API mutations. This is useful for shared incident sessions, demos, and restricted credentials. Server-side authorization remains authoritative in both modes.

​
Reconnection

The control plane—not the terminal—owns deployment work. Quit, disconnect SSH, or close the laptop, then reopen:
The workspace reconstructs itself from persisted deployments, operations, revisions, Guard evaluations, benchmarks, scaling decisions, and events. tmux is optional and InferCrane does not manage tmux sessions.

​
Keyboard reference

The workspace detects light and dark terminal backgrounds, adapts to narrow screens, requires an interactive TTY, and reconnects after transient API failures. For screen readers and logs, use --output json or the equivalent status, events, explain, and operation commands.