render-clilisted

# Render CLI Use the `render` binary to manage Render services, deploys, logs, and sessions from the terminal. Treat it like a production-control CLI: read first, parse JSON, and only create or mutate resources when the operator explicitly asked for that action. ## Agent defaults Always add these flags for agent-safe commands: - `--output json` for parseable output. - `--confirm` to skip confirmation prompts. The CLI defaults to interactive mode and can hang an agent if a command prompts. If a command is intended to run unattended, include both flags unless the CLI help says the mode is interactive-only. ## Auth Check the active login before assuming access: ```bash render whoami --output json --confirm ``` If the user is not logged in, ask them to complete: ```bash render login ``` `render login` uses the dashboard/browser login flow, so do not run it in an unattended automation loop. ## Services List services in the active workspace: ```bash render services --output json --confirm ``` Use the returned service `id` as `<service-id>` in deploy and log commands. When a push to Git did not deploy, inspect the service JSON for `autoDeploy`; it may be disabled for that service. ## Deploys Trigger a deploy only when the operator explicitly asks for a real deploy: ```bash render deploys create <service-id> --output json --confirm ``` Watch deploy state by polling: ```bash render deploys list <service-id> --output json --confirm ``` Common deploy statuses includ