Inspecting

Describe, raw YAML, live troubleshooting, and the related-objects drill-through: the read-only views for going deep on one object.

Three full-screen views let you look closely at a single object without leaving the TUI. All three are read-only, all three scroll the same way ( / , PgUp / PgDn), and esc returns you to the list.

Describe

Press V (or D) on a selected row to open the describe view, a kubectl describe-style layout of the object: its metadata, spec, conditions, and, once an asynchronous fetch returns, its recent Events. V works on every view, including the mixed-kind Related list. On the Workstations tab it is the way in, because there Enter opens an SSH shell instead.

The view has three modes, and its header shows which one you are in plus the switches available on this object:

KeyAction
yToggle raw YAML.
cToggle the resolved configuration (Workstations only).
zToggle timestamps between UTC and your local time zone.
/ , PgUp / PgDnScroll.
escBack to the list.

Pressing the current mode’s own key returns you to the describe layout, and each mode remembers its own scroll position, so flipping to the YAML and back does not lose your place. On a kind that has no resolved configuration, [c] config is simply absent from the header — the hint is never a lie.

The z toggle is pure reformatting of already-fetched data: it re-renders the conditions, the created line, and the Events from their stored timestamps without going back to the API, so flipping it is instant.

The describe view: metadata and conditions up top, the Events section below, with the y and z toggles in the footer.
The describe view: metadata and conditions up top, the Events section below, with the y and z toggles in the footer.

The resolved configuration (c)

On a Workstation, c shows the merged effective configuration the workstation resolves to — the same document rl workstation get-resolved-configuration prints, served by the control plane that homes the workstation: the applied configs with their source and priority, the configuration fingerprint, and the whole merged spec including environment, files, scripts, sources, devtools, toolconfigs, and dotfiles.

This is the fastest way to answer “is my devtool actually going to be installed?” without leaving the TUI.

The pane fetches once, on the first c, and shows a brief loading state. Secret references are not resolved: a ${secret:NAME} renders verbatim, because this is the effective spec rather than what is delivered to the workstation. If the resolve fails, the pane says so and shows why, rather than rendering an empty document.

Troubleshoot

Press T on a workstation to run diagnostics against it. Unlike Describe, which renders instantly from objects already in hand, Troubleshoot opens an SSH session to the workstation and runs a series of probes (the operating system, Docker, disk, the login user, the agent), so it shows a brief loading state while the gather runs.

This is the same diagnostic bundle as rl troubleshoot <workstation> on the command line, rendered inline. When you want to save a shareable bundle, use the command with --diagnostics.

Note

Troubleshoot dials the workstation over SSH, so on a wedged or unreachable workstation it can take a few seconds to time out. That is expected: the probes are bounded, and the view only ever renders whatever the gather has returned so far.

Press x on a workstation to open the Related view: a single mixed-kind list of everything tied to that workstation, computed from the reference graph rather than a raw label match. It gathers the WorkstationConfigs whose selector targets the workstation, the LocalBindings pointed at it, and the SSHKeys whose selector reaches it, and shows them together with a KIND, NAME, and DETAIL column.

The Related view is deliberately read-only, because its rows span several kinds and a results list should not fan a destructive action across them:

KeyAction
Enter / VView the selected related object.
DDescribe it.
xDrill further into that object’s own relations.
escBack.

Because the pane keys off the selected object’s own kind, pressing c on a Workstation row here opens its resolved configuration just as it would on the Workstations tab.

This is the fastest way to answer “what actually applies to this workstation?” without cross-referencing selectors by hand. To go the other direction (which workstations a config or key applies to), open that object’s own describe view, which lists the workstations it resolves onto.