govclisted

# govc — VMware vSphere management from the CLI govc is the vSphere CLI built on govmomi (https://github.com/vmware/govmomi). It talks to vCenter or standalone ESXi hosts over the vSphere API and is ideal for automation: every command supports `-json` output, entities can be referenced by path or glob pattern, and credentials come from environment variables. ## Before doing anything 1. **Check govc is installed and connected:** ```bash govc version # is govc installed? govc about # can we reach vCenter/ESXi? Shows product, version, build ``` If `govc about` fails, walk through connection setup — see `references/setup.md`. **Credentials must come from the environment that launched Claude Code.** govc reads `GOVC_URL` / `GOVC_USERNAME` / `GOVC_PASSWORD` from the process environment, and each shell command you run is a *separate* process — an `export` in one command does **not** carry over to the next. So if the vars are missing, do not try to export them yourself and do not ask the user to paste a password into the chat. Tell the user to set them in their shell and restart Claude Code (`references/setup.md` has the syntax for bash/zsh, PowerShell, and cmd). Check what's visible with `govc env GOVC_URL` — note that a bare `govc env` prints `GOVC_PASSWORD` in cleartext, so never run it. 2. **Know which shell you're in.** The command syntax below differs between POSIX shells and native PowerShell: - Linux, macOS