Skip to content

docs(skill): document brev ls nodes and the instance/node split - #434

Open
theFong wants to merge 2 commits into
brevdev:mainfrom
theFong:docs/skill-brev-ls-nodes
Open

docs(skill): document brev ls nodes and the instance/node split#434
theFong wants to merge 2 commits into
brevdev:mainfrom
theFong:docs/skill-brev-ls-nodes

Conversation

@theFong

@theFong theFong commented Jul 31, 2026

Copy link
Copy Markdown
Member

Problem

The brev-cli agent skill never mentioned brev ls nodes, so external nodes were effectively invisible to it. An agent that ran brev ls, saw no match, and concluded a machine didn't exist would be wrong on any org that registers external nodes — the two are separate namespaces and a node never appears in brev ls.

What changed

Documentation only, no CLI behaviour changes.

.agents/skills/brev-cli/SKILL.md

  • brev ls nodes in Quick Start
  • New "Listing Instances and Nodes" section covering the instances / nodes / orgs subcommands, with a table contrasting the two namespaces (status vocabulary, columns, whether stop/start/delete apply)
  • "Instance not found" troubleshooting now points at brev ls nodes

.agents/skills/brev-cli/reference/commands.md

  • brev ls entry expanded with the subcommand table and side-by-side output samples

The --json shape difference

Both files call out something that's easy to trip over when scripting: the two --json outputs have different shapes, so the same jq path can't serve both.

brev ls nodes --json | jq -r '.[].name'            # top-level array
brev ls       --json | jq -r '.workspaces[].name'  # rows wrapped in .workspaces

Using the wrong one fails with Cannot index array with string "name".

Verification

Every command shown was run against a live org on v0.6.329.

The brev-cli skill never mentioned `brev ls nodes`, so external nodes were
invisible to it. An agent that ran `brev ls`, saw no match, and concluded a
machine did not exist would be wrong on any org that registers external nodes.

Adds the `brev ls` subcommands (instances / nodes / orgs), a short comparison
of the two namespaces, and a troubleshooting pointer under "Instance not
found". Also notes that the two --json shapes differ: `ls nodes --json` is a
top-level array while `ls --json` wraps rows in .workspaces, so the same jq
path cannot serve both.

Documentation only; no CLI behaviour changes.
@theFong
theFong requested a review from a team as a code owner July 31, 2026 16:58
Keep the change scoped to documenting brev ls nodes; the existing trigger
keyword list is left untouched.
@patelspratik

Copy link
Copy Markdown
Contributor

might be worth including information about --all since that does show both instances and nodes, and instances of teammates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants