Inside the shell, /use-node <NAME> resolves a node display name against /list-compute-nodes and pins it for subsequent queries. Ctrl+N opens the picker.
/use-node <NAME|auto>## Overview Pinned routing lets an interactive REPL session target one specific compute node by display name. Unlike the `--compute-url` flag, which takes a raw URL, `/use-node` resolves a friendly name against the control plane's node registry. The resolved URL is stored for the duration of the session and used for every subsequent SQL call, giving the user reproducible worker selection without memorising URLs. ## Behavior - `/use-node <NAME>` calls `/list-compute-nodes`, matches the argument against each node's display name, and pins the resolved URL on the session. Subsequent queries bypass `/nodes/recommend` and go straight to that URL. - `/use-node auto` clears the pin and restores Auto routing, so the control plane resumes picking the node for each statement. - `Ctrl+N` opens an interactive picker populated from `/list-compute-nodes`. Selecting an entry is equivalent to running `/use-node <NAME>`. - The pin is session-local. It is not persisted to config.toml and is lost when the REPL exits. - `query --node <NAME>` and the global `--node` flag use the same name resolution but apply only to a single invocation; they do not change the persistent `/use-node` selection. ## Compatibility - `/use-node` requires a reachable control plane to resolve names. If `/list-compute-nodes` is unavailable, the pin cannot be established and the command reports a lookup error. - When a session is already in explicit-URL mode (`--compute-url` or `DF_COMPUTE_URL`), running `/use-node <NAME>` replaces the explicit URL with the name-resolved URL for the rest of the session.
/use-node prod-worker-01/use-node auto # return to Auto# Ctrl+N opens an interactive node picker that runs /use-node for you