---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxNTYxLCJzaW5jZSI6bnVsbCwidG9vbCI6InJlbmRlciIsInYiOjF9
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=render&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNTYxLCJzaW5jZSI6bnVsbCwidG9vbCI6InJlbmRlciIsInYiOjF9
items: 10
---
# sincecutoff.com changes: render

## render psql supports non-interactive queries and output formats (render, 2026-02-09)
Published 2026-10-19
- 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 (render, 2026-02-09)
Published 2026-10-19
- 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."

## render commands accept RENDER_OUTPUT as a global output format (render, 2026-02-11)
Published 2026-10-19
- 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 (render, 2026-02-11)
Published 2026-10-19
- 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 services update changes service configuration (render, 2026-03-23)
Published 2026-10-19
- 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 workflows create creates workflows from the CLI (render, 2026-04-29)
Published 2026-10-19
- 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 (render, 2026-04-29)
Published 2026-10-19
- 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 (render, 2026-04-29)
Published 2026-10-19
- 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 logout revokes the stored OAuth token and clears local CLI credentials/settings (render, 2026-05-13)
Published 2026-10-19
- 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 ea kv manages Key Values (render, 2026-05-21)
Published 2026-10-19
- 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."

Next: https://sincecutoff.com/v1/changes.md?tool=render&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNTYxLCJzaW5jZSI6bnVsbCwidG9vbCI6InJlbmRlciIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->