---
schema_version: 1
route: /t/render.md
tool: "render"
---

# sincecutoff.com /t/render — Render CLI

- name: Render CLI
- kind: cli
- children: none
- homepage: <https://github.com/render-oss/cli>

Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows.
Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json).
To stay current, read the changes feed: [`/v1/changes.md?tool=render`](https://sincecutoff.com/v1/changes.md?tool=render) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt).

### render ea sandboxes create adds HTTPS egress allow-list option (2026-10-18)
- slug: render-ea-sandboxes-create-adds-https-egress-allow-list-option-9b2737275a5d
- score: 0.94

How to use it:

When creating a sandbox that needs outbound HTTPS access to specific domains, run `render ea sandboxes create --allow-egress-https <domain>` and repeat the flag for each domain. If no network policy is specified, this sets the `allow-list` policy.

Examples:

```
render ea sandboxes create --allow-egress-https <domain>
```

- why_it_matters: Create a sandbox that can make outbound HTTPS requests to specific domains.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.30.0>, <https://render.com/docs/sandboxes-cli-reference>
- gotchas: "Version: v2.30.0"; "--allow-egress-https <domain>: Allows outbound HTTPS to the specified domain; repeat for multiple domains."; "Prerequisite: Sandbox commands use the `render ea` namespace during early access."; "Prerequisite: Render Sandboxes is in early access; request access is available from Render."; "The flag allows outbound HTTPS to specific domains."; "Repeat the flag for multiple domains."; "The flag sets the `allow-list` network policy only if no policy is specified."; "Docs conflict: The current Sandboxes CLI reference does not list `--allow-egress-https`; it lists `--network-policy` values `allow-all` and `deny-all` and a default of `allow-all`. The v2.30.0 release note documents the new flag and its `allow-list` default behavior."

### Render CLI sandbox snapshots can be named and reused by name or ID (2026-10-12)
- slug: render-cli-sandbox-snapshots-can-be-named-and-reused-by-name-or-id-d17020959f5b
- score: 0.97

How to use it:

When creating and reusing a sandbox snapshot, the v2.29.0 release note says to name it with `snapshots create --name`, then create a sandbox from its name or ID with `sandboxes create --from`. The current Render reference documents different flags, so it does not establish runnable usage for these v2.29.0 commands.

- why_it_matters: Create a named sandbox snapshot and start another sandbox from it during repository development.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.29.0>, <https://render.com/docs/sandboxes-cli-reference>
- gotchas: "Version: v2.29.0"; "Prerequisite: Render Sandboxes is in early access; sandbox commands use the `render ea` namespace."; "Prerequisite: Snapshot creation requires a running sandbox; wait until the snapshot status is `available` before restoring from it."; "Docs conflict: The current Render reference documents `snapshots create <sandboxId>` and `sandboxes create --snapshot-id <id>`. The v2.29.0 release note names `snapshots create --name` and `sandboxes create --from`; the current reference does not document those flags."

### render ea sandboxes snapshots delete removes sandbox snapshots (2026-09-10)
- slug: render-ea-sandboxes-snapshots-delete-removes-sandbox-snapshots-da4e78d47b9e
- score: 0.94

How to use it:

When the snapshot is not still being created, run `render ea sandboxes snapshots delete <snapshotId> --confirm` to delete it.

Examples:

```
render ea sandboxes snapshots delete <snapshotId> --confirm
```

```
render ea sandboxes snapshots delete <snapshotId> --group <sandboxGroupId> --confirm
```

- why_it_matters: Delete a sandbox snapshot while managing sandbox snapshots from the CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.28.0>, <https://render.com/docs/sandboxes-cli-reference>, <https://render.com/docs/sandboxes>
- gotchas: "Version: v2.28.0"; "<snapshotId> (required): ID of the snapshot to delete."; "--group <sandboxGroupId>: Select the snapshot’s sandbox group; defaults to the active workspace’s default group."; "--confirm: Global option that skips confirmation prompts; without it, deletion previews and makes no changes."; "Prerequisite: Render Sandboxes is in early access and must be enabled for the workspace."; "Prerequisite: The snapshot cannot be deleted while its status is `creating`."

### render ea sandboxes snapshot commands create, get, list, and restore sandboxes (2026-09-10)
- slug: render-ea-sandboxes-snapshot-commands-create-get-list-and-restore-sandboxes-9e4e85b40078
- score: 0.97

How to use it:

When a running sandbox needs preserving, create a snapshot and poll its status with `get` until it is `available`. Then restore it as a new sandbox with `--snapshot-id`; snapshots and restored sandboxes must use the source sandbox’s group.

Examples:

```
render ea sandboxes snapshots create <sandboxId>
render ea sandboxes snapshots get <snapshotId>
render ea sandboxes snapshots list
```

```
render ea sandboxes create --snapshot-id <snapshotId>
```

- why_it_matters: When maintaining a repository that uses Render sandboxes, snapshot a running sandbox and restore a sandbox from that snapshot.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.27.0>, <https://render.com/docs/sandboxes-cli-reference>, <https://render.com/docs/sandboxes>
- gotchas: "Version: v2.27.0"; "<sandboxId> (required): ID of the running sandbox to snapshot."; "<snapshotId> (required): Snapshot ID to retrieve or restore; restore requires an available snapshot."; "--snapshot-id (required): Start the new sandbox from this snapshot; it must be available and in the same sandbox group. A runtime snapshot requires `--plan` matching its plan."; "--kind: Snapshot kind: `filesystem` (default) or `runtime`."; "--group: Sandbox group for `get` or `list`; defaults to the active workspace’s default group."; "--status: For `list`, repeatable filter: `creating`, `available`, or `failed`."; "Prerequisite: Render Sandboxes must be enabled for the workspace; docs say sandboxes require a valid Render API key and workspace ID."; "Prerequisite: The current quickstart requires Render CLI 2.28.0 or later."; "Docs conflict: Version discrepancy: release v2.27.0 says these snapshot commands and `--snapshot-id` were added in v2.27.0, while the current Render quickstart states CLI 2.28.0 or later is required. The cited current docs do not establish v2.27.0-specific command behavior."

### render postgres connection pool management and detail output (2026-09-01)
- slug: render-postgres-connection-pool-management-and-detail-output-ae27792e912f
- score: 0.93

How to use it:

When creating or updating a Render Postgres database, set `--connection-pool` to `none` or `pgbouncer`; inspect the database’s detail output to see its current mode.

Examples:

```
render postgres create --connection-pool=<none|pgbouncer>
```

```
render postgres update <postgresID|postgresName> --connection-pool=<none|pgbouncer>
```

```
render postgres get <postgresID|postgresName>
```

- why_it_matters: Create or update a Render Postgres database with a specific connection pool mode, or inspect its current mode.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.26.0>, <https://render.com/docs/cli-reference>
- gotchas: "Version: v2.26.0"; "--connection-pool: Set the connection pool to `none` or `pgbouncer`."; "<postgresID|postgresName> (required): Target Postgres database for update or detail lookup; accepts an ID or name in the CLI reference."; "Docs conflict: The current CLI reference is for v2.29.0 and documents these commands as `render pg ...`; the v2.26.0 release note uses `render postgres ...`. I used the release-note command spelling and did not use the newer command alias as evidence for v2.26.0 invocation syntax."

### Render CLI Key Value commands show and set persistence mode (2026-07-21)
- slug: render-cli-key-value-commands-show-and-set-persistence-mode-7fff0d83c6d6
- score: 0.96

How to use it:

When creating or updating a Key Value instance, pass `--persistence-mode` to set its mode; use `kv get` to inspect the instance details, including persistence mode. [CLI reference](https://render.com/docs/cli-reference)

Examples:

```
render kv create --name <name> --region <region> --plan <plan> --persistence-mode <journal_snapshot|snapshot|off>
```

```
render kv update <keyValueID|keyValueName> --persistence-mode <journal_snapshot|snapshot|off>
```

```
render kv get <keyValueID|keyValueName>
```

- why_it_matters: Create or update a Key Value instance and inspect or set its persistence mode.
- before: Journal + Snapshot was the behavior of all paid Key Value instances before the persistence-mode feature.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.22.0>, <https://render.com/docs/cli-reference>, <https://github.com/render-oss/cli/blob/v2.22.0/CHANGELOG.md>, <https://render.com/docs/key-value>, <https://render.com/changelog/specify-disk-persistence-behavior-for-paid-key-value-instances>
- gotchas: "Version: v2.22.0"; "--name: Instance name; generated if omitted."; "--region: Instance region: frankfurt, ohio, oregon, singapore, or virginia."; "--plan: Instance plan: free, 256mb, 1g, 5g, 10g, 20g, or 40g; custom enterprise plan names are accepted."; "--persistence-mode: Set disk persistence to journal_snapshot, snapshot, or off. For create, omit to use the plan default. The docs do not state these values are mutually exclusive, but the option accepts one mode."; "<keyValueID|keyValueName> (required): Target Key Value ID or name for update/get. Name lookup uses the active workspace; use an ID or disambiguate duplicate names with --environment."; "Prerequisite: Use Render CLI v2.22.0 or later for the release-note change. Authenticate with `render login` or an API key; the CLI docs describe API-key authentication for automation."; "Prerequisite: Data persistence is unavailable for free Key Value instances."

### render keyvalues exposes top-level Key Value commands (2026-06-29)
- slug: render-keyvalues-exposes-top-level-key-value-commands-ccb97fbc29a2
- score: 0.98

How to use it:

For managing a Render Key Value resource, use the generally available `render keyvalues` commands; `render kv` is a shorthand alias.

Examples:

```
render keyvalues list
```

```
render keyvalues get <keyValueID|keyValueName>
```

- why_it_matters: Manage a Key Value resource from the Render CLI.
- before: Before v2.21.0, Key Value commands were under `render ea kv`; that earlier CLI version described them as experimental.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.21.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>, <https://github.com/render-oss/cli/blob/main/CHANGELOG.md>
- gotchas: "Version: v2.21.0"; "Availability: generally available"; "<keyValueID|keyValueName> (required): Target Key Value ID or name for `get`."; "--project <id|name>: Narrow `list` results to a project."; "--environment <id|name>: Narrow `list` results to an environment."; "Prerequisite: Install the Render CLI and authenticate with `render login` or an API key; commands operate on the active workspace."; "Docs conflict: The available generated CLI reference is for v2.29.0, not v2.21.0; its Key Value sections show `kv` command spellings. The release note confirms the `keyvalues` top-level name and `kv` alias, but exact v2.21.0 usage and flags were not available in the reference."

### render postgres exposes top-level Postgres commands (2026-06-29)
- slug: render-postgres-exposes-top-level-postgres-commands-0b3bcc37dd97
- score: 0.93

How to use it:

When managing a Render Postgres resource, use the CLI commands available in version 2.21.0 or later; `render pg` is the documented shorthand. Create a database with `render pg create --name <name> --region <region> --version <major> --plan <plan> --confirm`, or use the documented `list` and `get` commands to inspect resources.

Examples:

```
render pg create --name <name> --region <region> --version <major> --plan <plan> --confirm
```

```
render pg list
```

```
render pg get <postgresID|postgresName>
```

- why_it_matters: Manage a Postgres resource from the Render CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.21.0>, <https://render.com/changelog/manage-postgres-and-key-value-instances-using-the-render-cli>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.21.0"; "Availability: generally available"; "<postgresID|postgresName> (required): Target database ID or name for `get`; names are looked up in the active workspace."; "--name <name>: Set the database name; generated if omitted."; "--region <region>: Set the region; server picks one if omitted."; "--version <major>: Set the Postgres major version; defaults to 18 in the current reference."; "--plan <plan>: Choose the Postgres plan."; "--confirm: Skip confirmation prompts; with create, skip the wizard and create immediately from flags and defaults."; "Prerequisite: Render CLI version 2.21.0 or later."; "Prerequisite: Authenticate with `render login`, or provide a Render API key for CLI authentication."; "Docs conflict: The card says top-level `render postgres` is available. The current generated CLI reference (v2.29.0) documents Postgres commands under `pg` and does not document `postgres`; it is newer than the card version."

### render ea pg commands manage Postgres databases (2026-06-05)
- slug: render-ea-pg-commands-manage-postgres-databases-ee2cc3062817
- score: 0.98

How to use it:

For Postgres databases, use `render ea pg list` to find targets, `get` to inspect one, `update` to modify one, and `suspend` or `resume` to change its state.

- why_it_matters: Inspect, update, suspend, or resume a Postgres database in a workspace, project, or environment.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.20.0>, <https://render.com/docs/cli>
- gotchas: "Version: v2.20.0"; "Prerequisite: Install the Render CLI and authenticate with `render login` or an API key; CLI commands operate on the active workspace."; "Prerequisite: The v2.20.0 release adds the listed `render ea pg` commands."; "Docs conflict: The current CLI reference documents these operations as `render pg ...` and does not provide usage for the card’s `render ea pg ...` interface. Its command flags may differ from v2.20.0."

### render ea pg create interactive wizard (2026-06-05)
- slug: render-ea-pg-create-interactive-wizard-b7b3ba0a222b
- score: 0.92

How to use it:

When creating a Postgres database in interactive output mode, run `render ea pg create` without `--confirm` to open the wizard.

Examples:

```
render ea pg create
```

- why_it_matters: Create a Postgres database interactively when setting one up from the CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.20.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.20.0"; "--confirm: Skip confirmation prompts; omit it to use the wizard in interactive output mode."; "--output: Select output format; `interactive` is the interactive mode. It is the default in TTY environments."; "Prerequisite: Use CLI v2.20.0 or later for the documented wizard change."; "Prerequisite: The CLI must be authenticated to Render and have an active workspace."; "The wizard is offered only when `render ea pg create` is run without `--confirm` in interactive output mode."; "Docs conflict: Current CLI docs describe the promoted command as `render pg create`; that promotion occurred after v2.20.0. This card's v2.20.0 command remains `render ea pg create`."

### render ea pg create creates a Postgres instance (2026-05-28)
- slug: render-ea-pg-create-creates-a-postgres-instance-7100a5bc0d72
- score: 0.98

How to use it:

When setting up a repository’s development environment, run `render ea pg create` to create a Postgres instance. The v2.19.0 release note does not specify options for this command.

Examples:

```
render ea pg create
```

- why_it_matters: Create a Postgres instance from the CLI while setting up a repository's development environment.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.19.0>, <https://render.com/docs/cli>
- gotchas: "Version: v2.19.0"; "Prerequisite: Install the Render CLI and authenticate with a CLI token; the CLI uses the active workspace."; "Docs conflict: The current CLI reference documents `pg create`, not the card’s `ea pg create` interface; it is for v2.29.0, newer than v2.19.0. Its flags and behavior are not established here for v2.19.0."

### render ea kv manages Key Values (2026-05-21)
- slug: render-ea-kv-manages-key-values-b97c73ef2e61
- score: 0.94

How to use it:

When managing a Render Key Value with CLI v2.18.0, the release adds `render ea kv` commands for create, get, list, update, delete, suspend, and resume. Use the `ea` namespace until the interface stabilizes.

- why_it_matters: Create or manage a Key Value from the Render CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.18.0>, <https://render.com/docs/cli>
- gotchas: "Version: v2.18.0"; "Availability: Key Value itself is generally available; the CLI interface remains in the `ea` namespace until it stabilizes."; "Prerequisite: Install the Render CLI, authenticate with `render login`, and set an active workspace; CLI commands operate on that workspace."; "Prerequisite: The release describes Key Value as generally available; the CLI `kv` interface remains under `ea` until stabilized."; "The `kv` commands remain under the `ea` namespace until the interface stabilizes."

### render workflows dev loads .env files (2026-05-21)
- slug: render-workflows-dev-loads-env-files-df2368f88fe4
- score: 0.96

How to use it:

To run a workflow locally with repository environment variables, run `render workflows dev -- <command>` from the repository; the current-directory `.env` is loaded automatically. To load specific files, repeat `--env-file <path>`; later files override earlier ones.

Examples:

```
render workflows dev -- <command>
```

```
render workflows dev --env-file <path> -- <command>
```

- why_it_matters: Run a workflow locally with environment variables from the repository's `.env` files.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.18.0>, <https://render.com/docs/cli-reference>
- gotchas: "Version: v2.18.0"; "<command> (required): Command to start the workflow service; supplied after `--`."; "--env-file <path>: Path to an environment file for the workflow subprocess. Repeat to load multiple files; later files override earlier ones."; "The default `.env` file is loaded from the current directory."

### render logout revokes the stored OAuth token and clears local CLI credentials/settings (2026-05-13)
- slug: render-logout-revokes-the-stored-oauth-token-and-clears-local-cli-credentials-se-f403e2322756
- score: 0.94

How to use it:

To remove stored Render CLI authentication locally, run `render logout` to revoke the stored OAuth token and clear local CLI credentials/settings.

Examples:

```
render logout
```

- why_it_matters: Remove stored Render CLI authentication from the local environment.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.17.0>, <https://github.com/render-oss/cli/blob/main/CHANGELOG.md>
- gotchas: "Version: v2.17.0"

### render workflows create creates workflows from the CLI (2026-04-29)
- slug: render-workflows-create-creates-workflows-from-the-cli-df898e0ab2f6
- score: 0.97

How to use it:

To create a workflow service on Render, run `render workflows create` with its required configuration flags in non-interactive mode, or fill in the interactive form.

Examples:

```
render workflows create --name <workflow-name> --repo <repository-url-or-local-directory> --runtime <node|python|go|ruby|elixir> --build-command '<build-command>' --run-command '<workflow-run-command>'
```

- why_it_matters: Create a new workflow from the CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.16.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.16.0"; "--name <workflow-name> (required): Workflow name in non-interactive mode."; "--repo <repository-url-or-local-directory> (required): Git repository URL, or local directory path resolved through its origin remote, in non-interactive mode."; "--runtime <runtime> (required): Runtime: node, python, go, ruby, or elixir."; "--build-command <command> (required): Build command in non-interactive mode."; "--run-command <command> (required): Command to run the workflow in non-interactive mode."; "--branch <branch>: Git branch."; "--root-directory <directory>: Root directory in the repository."; "--region <region>: Deployment region; defaults to oregon."; "--auto-deploy-trigger <behavior>: Autodeploy behavior: commit, off, or checksPass; defaults to commit."; "--env-file <path>: Load variables from an existing env file; repeatable, with later files overriding earlier files."; "--env-var KEY=VALUE: Set an environment variable; repeatable. Inline values override values loaded from env files."; "Prerequisite: Install the Render CLI and authenticate with `render login` or provide a Render API key; select the active workspace for the target service."

### render workflows runs cancel cancels a running task (2026-04-29)
- slug: render-workflows-runs-cancel-cancels-a-running-task-4bb08efd4e6f
- score: 0.95

How to use it:

When a workflow task is running, use `render workflows runs cancel <taskRunID>` to cancel its run. The v2.16.0 release note confirms the command was added for this task; the current CLI reference documents it under a newer command path.

Examples:

```
render workflows runs cancel <taskRunID>
```

- why_it_matters: Cancel a running workflow task from the CLI.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.16.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.16.0"; "taskRunID: Task run ID to cancel; the current reference shows this positional argument as optional."; "Prerequisite: Authenticate the CLI and set an active workspace; CLI commands operate on that workspace."; "Docs conflict: The current CLI reference documents cancellation as `render workflows tasks runs cancel [taskRunID]`, with optional `--local` and `--port` flags. That command path differs from v2.16.0's `render workflows runs cancel`."

### workflows create --repo accepts a local directory (2026-04-29)
- slug: workflows-create-repo-accepts-a-local-directory-97e2df46bd08
- score: 0.93

How to use it:

To create a workflow from the current repository directory, run `render workflows create` with `--repo .` and provide the required workflow configuration.

Examples:

```
render workflows create --repo . --name <workflow-name> --runtime <node|python|go|ruby|elixir> --build-command '<build-command>' --run-command '<run-command>'
```

- why_it_matters: Create a workflow from the current repository directory.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.16.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.16.0"; "--repo (required): Repository URL or local directory path; `.` resolves through the repository's origin remote."; "--name (required): Workflow name in non-interactive mode."; "--runtime (required): Runtime: node, python, go, ruby, or elixir."; "--build-command (required): Build command in non-interactive mode."; "--run-command (required): Command to run the workflow; required in non-interactive mode."; "Prerequisite: Use the Render CLI and authenticate with `render login` before running commands that access your account."

### render services update changes service configuration (2026-03-23)
- slug: render-services-update-changes-service-configuration-984381279d35
- score: 0.95

How to use it:

When a Render service needs configuration changes from a repository workflow, run `render services update <service>` with flags for the fields to change. The command runs only in non-interactive mode.

Examples:

```
render services update <service> --name <name> --branch <branch> --image <image-url> --build-command '<build-command>' --start-command '<start-command>' --auto-deploy
```

- why_it_matters: Update a Render service's configuration from a repository workflow.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.15.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.15.0"; "<service> (required): Service identifier or name to update; the command reference shows it as a required positional argument."; "--name <name>: Set the service name."; "--branch <branch>: Set the Git branch."; "--image <image-url>: Set the Docker image URL."; "--build-command <command>: Set the build command."; "--start-command <command>: Set the start command."; "--auto-deploy: Enable auto-deploy."; "Prerequisite: Run in non-interactive mode."; "Prerequisite: Authenticate with Render using `render login` before running commands that require account access."; "Docs conflict: The available CLI reference documents v2.29.0, newer than the card’s v2.15.0. It documents the named update flags but does not establish that their behavior or availability was identical in v2.15.0."

### render commands accept RENDER_OUTPUT as a global output format (2026-02-11)
- slug: render-commands-accept-render-output-as-a-global-output-format-e38510cac7a0
- score: 0.98

How to use it:

When scripts or CI need a consistent Render CLI output format, set `RENDER_OUTPUT` to `json`, `yaml`, or `text`. Override it for a command with `--output` or `-o`; the CLI reference documents output selection and TTY behavior, but the current docs are newer than v2.9.0.

Examples:

```
export RENDER_OUTPUT=json
```

```
render services list -o yaml
```

```
render services list -o text | grep my-service
```

- why_it_matters: Set a consistent output format for Render CLI commands used in scripts or CI, with a per-command override where needed.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.9.0>, <https://render.com/docs/cli>, <https://render.com/docs/cli-reference>
- gotchas: "Version: v2.9.0"; "RENDER_OUTPUT: Sets the output format globally; documented precedence is command `--output`/`-o`, then this environment variable, then TTY/CI auto-detection. The CLI guide documents `json`, `yaml`, and `text` values."; "--output / -o: Sets a command's output format. The current CLI reference lists `interactive`, `json`, `yaml`, and `text`; it says output auto-switches to text on non-TTY."; "Prerequisite: Install the Render CLI; the guide describes installation methods and advises running `render` with no arguments to confirm installation."; "Output selection precedence is command `--output` / `-o`, then `RENDER_OUTPUT`, then auto-detection based on TTY/CI signals."; "Docs conflict: The currently published CLI docs identify v2.28.0/v2.29.0, later than the card’s v2.9.0; no differing `RENDER_OUTPUT` behavior was found. Current reference lists `interactive` as a supported `--output` value, while the guide names `json`, `yaml`, and `text` for non-interactive use."

### render ssh supports ephemeral shells (2026-02-11)
- slug: render-ssh-supports-ephemeral-shells-dff0693f4cb5
- score: 0.98

How to use it:

When you need an isolated temporary shell for a service, run `render ssh <service-name> --ephemeral` (or `-e`). Run `render ssh` to select a service interactively and connect ephemerally.

Examples:

```
render ssh <service-name> --ephemeral
```

```
render ssh <service-name> -e
```

```
render ssh
```

- why_it_matters: Open an isolated temporary shell for a service in the current workspace.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.9.0>, <https://render.com/docs/ssh>, <https://render.com/docs/cli-reference>
- gotchas: "Version: v2.9.0"; "serviceID|serviceName: Selects the service; omit it in interactive mode to choose from the workspace."; "--ephemeral / -e (required): Connects to an ephemeral instance."; "Prerequisite: Install and log in to the Render CLI."; "Prerequisite: The service must be compatible, run on a paid compute plan, and have at least one successful deploy."; "The shell instance is temporary and isolated."

### render psql supports non-interactive queries and output formats (2026-02-09)
- slug: render-psql-supports-non-interactive-queries-and-output-formats-9b487113d1d1
- score: 0.99

How to use it:

When you need to run a database query from a script and capture its output, use `render psql` with `-c` and select `-o json`, `-o yaml`, or `-o text`. Pass extra `psql` flags after `--`.

Examples:

```
render psql <databaseID-or-name> -c "<SQL query>" -o json
```

```
render psql <databaseID-or-name> -c "<SQL query>" -o text -- --csv
```

```
render psql <databaseID-or-name> -c "<SQL query>" -o yaml
```

- why_it_matters: Run a database query from a script and capture its output.
- before: Use `render psql` to open an interactive psql session; non-interactive query execution was added in v2.8.0.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.8.0>, <https://render.com/docs/cli-reference>, <https://render.com/changelog/render-cli-v2-8-0>
- gotchas: "Version: v2.8.0"; "<databaseID-or-name>: Optional Render Postgres database ID or name; if omitted, interactive mode can prompt for a database."; "--command / -c (required): Execute a SQL command in non-interactive mode."; "-o (required): Select the output format: `json`, `yaml`, or `text`. These choices are alternatives."; "-- [psql args]: Pass additional flags to psql, such as `--csv`, `-t`, or `-A`."

### render workspaces lists workspaces with selectable output (2026-02-09)
- slug: render-workspaces-lists-workspaces-with-selectable-output-2a23d67b2c08
- score: 0.95

How to use it:

When you need to inspect workspaces, run `render workspaces` to browse interactively, or add `-o <format>` for non-interactive output.

Examples:

```
render workspaces
```

```
render workspaces -o json
```

```
render workspaces -o <text|yaml>
```

- why_it_matters: Inspect available workspaces from a script or terminal session.
- sources: <https://github.com/render-oss/cli/releases/tag/v2.8.0>, <https://render.com/docs/cli-reference>, <https://render.com/docs/cli>
- gotchas: "Version: v2.8.0"; "-o, --output <format>: Sets output format. Allowed values: `interactive`, `json`, `yaml`, `text`. Interactive is the default in TTY environments; non-TTY environments default to text. The docs do not say the values are mutually exclusive."; "Prerequisite: Authenticate the CLI with `render login` or provide a Render API key; the docs describe API-key authentication for automation."