Managing resources | Ringleader Docs

Every tab shares the same navigation, but each has its own actions on the selected row. The footer always shows the ones available where you are; this page is the reference for what each does. The actions that change state are declarative: they edit desired state and let the control loop apply it, the same as the equivalent rl command would.

Workstations

The Workstations tab carries the full lifecycle plus the two ways in.

Key	Action	Notes
`S`	Start	Sets the workstation’s desired state to running.
`s`	Stop	Halts the workstation without losing its disk or installed tools.
`r`	Restart	Bumps a restart nonce the control loop applies.
`Enter`	SSH	Opens an interactive shell on the workstation, the same as `rl shell`.
`t`	Tmux	Attaches a persistent `tmux` session that survives a dropped connection.
`V`	View	Opens the read-only describe view, from which `c` shows the workstation’s resolved configuration.
`D`	Describe	The same view as `V`.
`T`	Troubleshoot	Runs live diagnostics against the workstation (see Inspecting).
`x`	Related	Shows the configs, bindings, and SSH keys tied to this workstation.
`e`	Edit	Opens the object in your `$EDITOR` as YAML.
`c`	Copy	Clones the object into a new one you can rename.
`d`	Delete	Removes the object.

S, s, and r do not call an imperative verb. They patch the workstation’s desired state (spec.stopped, a restart nonce) and let the control loop apply it, so what you do in the TUI matches what a manifest would express. Each is confirmed with a modal before it fires, so a mistyped key never stops the wrong workstation.

Tip

Enter and t shell out to the real rl shell and rl tmux, so they behave identically to running those commands, including automatic reconnect on tmux.

Configs

WorkstationConfigs are read-open to the namespace, so the view is view-and-manage with no lifecycle:

Key	Action
`Enter` / `V`	View the config (its fields and relations).
`e`	Edit as YAML.
`c`	Copy into a new config.
`d`	Delete.

Bindings

LocalBindings add an enable toggle and a retarget action:

Key	Action	Notes
`a`	Enable / Disable	Toggles the binding on or off immediately, no confirm.
`t`	Target	Retargets the binding at a different workstation (the `binding switch` semantics).
`Enter`	View	The `binding show` equivalent.
`e` / `c` / `d`	Edit / Copy / Delete	As elsewhere.

SSH Keys

SSHKeys forward a local key into the workstations their selector matches:

Key	Action	Notes
`a`	Enable / Disable	Toggles forwarding on or off immediately, no confirm.
`D`	Describe	Read-only describe view.
`Enter`	View	Same as describe.
`e` / `c` / `d`	Edit / Copy / Delete	As elsewhere.

Grants

Grants are the shares you have created. They are authored with the share CLI, so this view is list, toggle, and inspect rather than create:

Key	Action	Notes
`a`	Enable / Disable	Turns the share on or off. Reversible both ways; the backend drops or restores the shared access accordingly.
`D`	Describe	Read-only describe view.
`Enter`	View	Same as describe.
`e` / `c` / `d`	Edit / Copy / Delete	As elsewhere.

Creating with the wizard

Press + on the Workstations, Configs, Bindings, or SSH Keys tab to open a create wizard for that kind. The wizard is the one kind-aware part of an otherwise kind-generic UI: it collects the common, high-signal fields (a name, a provider, a config to reference, and so on) and assembles a valid object.

Text fields edit in place; use ← / → to move the caret.
Enum fields either cycle through their options or, for larger option sets, open a pop-up list to choose from.
If you need a field the wizard does not surface, hand the draft off to your editor and finish it as YAML.

There is no wizard on the Grants tab (create a share with the share CLI instead) or on the transient Related view (it is read-only).

Note

e (Edit) and c (Copy) work on every kind because they operate on the raw object, so the TUI is never a subset of what you can express in YAML. Anything the wizard does not cover, e will.