pp-render

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Render — Printing Press CLI

Prerequisites: Install the CLI

前提条件：安装CLI

This skill drives the

render-pp-cli

binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

Install via the Printing Press installer:

bash

npx -y @mvanhorn/printing-press install render --cli-only

Verify:
```
render-pp-cli --version
```
Ensure
```
$GOPATH/bin
```
(or
```
$HOME/go/bin
```
) is on
```
$PATH
```
.

If the

npx

install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

bash

go install github.com/mvanhorn/printing-press-library/library/cloud/render/cmd/render-pp-cli@latest

--version

reports "command not found" after install, the install step did not put the binary on

$PATH

. Do not proceed with skill commands until verification succeeds.

本Skill驱动

render-pp-cli

二进制文件。**在调用本Skill的任何命令之前，您必须确认CLI已安装。**如果未安装，请先执行以下步骤安装：

通过Printing Press安装器安装：

bash

npx -y @mvanhorn/printing-press install render --cli-only

验证：
```
render-pp-cli --version
```
确保
```
$GOPATH/bin
```
（或
```
$HOME/go/bin
```
）已添加到
```
$PATH
```
环境变量中。

如果

npx

安装失败（如无Node环境、离线等），可以改用Go直接安装（要求Go 1.26.3或更高版本）：

bash

go install github.com/mvanhorn/printing-press-library/library/cloud/render/cmd/render-pp-cli@latest

如果安装后执行

--version

返回“command not found”，说明安装步骤未将二进制文件添加到

$PATH

中。请在验证成功前不要执行本Skill的命令。

When to Use This CLI

何时使用本CLI

Use render-pp-cli when you need to reason about your Render footprint as a whole, not one resource at a time. It shines for env-var promotion across environments, blueprint drift checks in CI, monthly cost rollups, preview cleanup, and audit-log forensics. For one-off interactive workflows like

render psql

render ssh

, the official CLI is fine — render-pp-cli covers those too but its real value is the analytical commands the dashboard hides.

当您需要整体管理Render资源，而非逐个处理单个资源时，可以使用render-pp-cli。它在跨环境同步环境变量、CI中的蓝图漂移检查、月度成本汇总、预览环境清理以及审计日志取证等场景下表现出色。对于

render psql

或

render ssh

这类一次性交互式工作流，官方CLI已足够——render-pp-cli也支持这些操作，但它真正的价值在于提供了仪表盘所隐藏的分析类命令。

Unique Capabilities

独特功能

These capabilities aren't available in any other tool for this API.

这些功能是其他基于该API的工具所不具备的。

Local state that compounds

可累积的本地状态

env diff
— Compare env vars between any two services, env-groups, or a service vs an env-group, three-way diff style.
Reach for this when promoting config across environments — it's the cheapest way to see what's actually different without click-through.
bash
```
render-pp-cli env diff srv-staging-api srv-prod-api --json
```
env promote
— Copy env vars from a source service or env-group to a target with --only/--exclude/--dry-run.
Use when shipping a known-good staging config to prod without dragging dev-only keys along.
bash
```
render-pp-cli env promote --from srv-staging-api --to srv-prod-api --exclude DEBUG_TOKEN --dry-run
```
drift
— Compare a checked-in render.yaml against live workspace state and report added/removed/modified entities by name.
Run this in CI to fail builds when someone edits prod through the dashboard instead of the blueprint.
bash
```
render-pp-cli drift --blueprint render.yaml --json
```
cost
— Sum monthly cost across services, postgres, key-value, redis, and disks; group by project, environment, or owner.
Reach for this on the Friday cost-review or when finance asks 'what would happen if we downsized these three services?'
bash
```
render-pp-cli cost --group-by project --json
```
rightsize
— For each service, fetch last --since 7d of CPU and memory; compute p95 utilization; flag services breaching --high or --low thresholds against plan capacity.
Run this before the cost rollup to find quick downsizing wins or services about to throttle.
bash
```
render-pp-cli rightsize --since 7d --high 80 --low 20 --json
```

env diff
— 以三方对比的方式，比较任意两个服务、env-group，或服务与env-group之间的环境变量差异。
当您需要跨环境同步配置时可以使用此命令——这是无需点击操作即可查看实际差异的最简方式。
bash
```
render-pp-cli env diff srv-staging-api srv-prod-api --json
```
env promote
— 从源服务或env-group复制环境变量到目标服务或env-group，支持
```
--only
```
/
```
--exclude
```
/
```
--dry-run
```
参数。
当您需要将经过验证的 staging 配置同步到生产环境，同时排除仅用于开发的密钥时使用此命令。
bash
```
render-pp-cli env promote --from srv-staging-api --to srv-prod-api --exclude DEBUG_TOKEN --dry-run
```
drift
— 将已提交的render.yaml与实时工作区状态进行对比，按名称报告新增、移除或修改的实体。
在CI中运行此命令，当有人通过仪表盘而非蓝图修改生产环境时，可使构建失败。
bash
```
render-pp-cli drift --blueprint render.yaml --json
```
cost
— 汇总服务、Postgres、键值存储、Redis和磁盘的月度成本；支持按项目、环境或所有者分组。
在周五成本审查或财务询问“如果我们缩减这三个服务的规模会怎样？”时使用此命令。
bash
```
render-pp-cli cost --group-by project --json
```
rightsize
— 针对每个服务，获取过去
```
--since 7d
```
的CPU和内存数据；计算p95利用率；标记超出
```
--high
```
或低于
```
--low
```
阈值的服务。
在成本汇总前运行此命令，可快速找到缩减规模的空间或即将出现性能瓶颈的服务。
bash
```
render-pp-cli rightsize --since 7d --high 80 --low 20 --json
```

Lifecycle hygiene

生命周期管理

preview-cleanup
— List preview services older than --stale-days N; delete in bulk on --confirm.
Use when the monthly bill spikes and you suspect orphaned preview envs.
bash
```
render-pp-cli preview-cleanup --stale-days 14 --confirm
```
orphans
— Find unattached disks, empty env-groups, custom-domains pointing at deleted services, registry credentials referenced by no service, and disk snapshots beyond retention.
Audit cleanup, billing review, and SOC 2 evidence-gathering all start here.
bash
```
render-pp-cli orphans --json
```

preview-cleanup
— 列出超过
```
--stale-days N
```
天的预览服务；使用
```
--confirm
```
参数可批量删除。
当月度账单激增且您怀疑存在孤立预览环境时使用此命令。
bash
```
render-pp-cli preview-cleanup --stale-days 14 --confirm
```
orphans
— 查找未挂载的磁盘、空的env-group、指向已删除服务的自定义域名、无服务引用的注册表凭据，以及超出保留期限的磁盘快照。
审计清理、账单审查和SOC 2证据收集都可以从这个命令开始。
bash
```
render-pp-cli orphans --json
```

Agent-native plumbing

Agent原生功能

env where
— For a given env-var key, list every service and env-group that defines it with hash, length, and last-modified timestamp (never raw value).
First call during a credential rotation or a 'who uses this secret' audit.
bash
```
render-pp-cli env where STRIPE_KEY --json
```
incident-timeline
— Merge deploys, events, and audit-logs for one service into one chronological table for a given window.
First command on-call should run during a 2am page after a deploy.
bash
```
render-pp-cli incident-timeline srv-checkout-api --since 2h --json
```
audit search
— FTS5 search across cached audit logs by actor, target, action, and time window.
Use during SOC 2 evidence-gathering or to answer 'who rotated this key last quarter'.
bash
```
render-pp-cli audit search --actor riley@example.com --target STRIPE_KEY --since 30d --json
```
deploys diff
— Show commit range, env-var changes, image-tag changes, and plan/region/scale changes between two deploys of one service.
First command in a post-deploy regression triage — answers 'what actually changed'.
bash
```
render-pp-cli deploys diff srv-checkout-api dep-aaa dep-bbb --json
```

env where
— 针对指定的环境变量键，列出所有定义了该变量的服务和env-group，包含哈希值、长度和最后修改时间戳（绝不会返回原始值）。
在凭据轮换或“谁在使用这个密钥”审计时，首先调用此命令。
bash
```
render-pp-cli env where STRIPE_KEY --json
```
incident-timeline
— 将指定服务的部署记录、事件和审计日志合并为一个按时间排序的表格，时间范围可自定义。
在凌晨2点收到部署后的告警时，值班人员应首先运行此命令。
bash
```
render-pp-cli incident-timeline srv-checkout-api --since 2h --json
```
audit search
— 通过FTS5搜索缓存的审计日志，支持按执行者、目标、操作和时间范围筛选。
在SOC 2证据收集或回答“上季度谁轮换了这个密钥”时使用此命令。
bash
```
render-pp-cli audit search --actor riley@example.com --target STRIPE_KEY --since 30d --json
```
deploys diff
— 显示同一服务两次部署之间的提交范围、环境变量变化、镜像标签变化以及计划/区域/规模变化。
在部署后回归问题排查时，首先运行此命令——它能回答“实际发生了哪些变化”。
bash
```
render-pp-cli deploys diff srv-checkout-api dep-aaa dep-bbb --json
```

Command Reference

命令参考

blueprints — Blueprints allow you to define your resources in a

render.yaml

file and automatically sync changes to your Render services. The API gives control over how your Blueprints are used to create and manage resources.

```
render-pp-cli blueprints disconnect
```
— Disconnect the Blueprint with the provided ID. Disconnecting a Blueprint stops automatic resource syncing via the...
```
render-pp-cli blueprints list
```
— List Blueprints for the specified workspaces. If no workspaces are provided, returns all Blueprints the API key has...
```
render-pp-cli blueprints retrieve
```
— Retrieve the Blueprint with the provided ID.
```
render-pp-cli blueprints update
```
— Update the Blueprint with the provided ID.
```
render-pp-cli blueprints validate
```
— Validate a
```
render.yaml
```
Blueprint file without creating or modifying any resources. This endpoint checks the syntax...

cron-jobs — Manage cron jobs

disks — Disks allow you to attach persistent storage to your services.

```
render-pp-cli disks add
```
— Attach a persistent disk to a web service, private service, or background worker. The service must be redeployed for...
```
render-pp-cli disks delete
```
— Delete a persistent disk attached to a service. All data on the disk will be lost. The disk's associated service...
```
render-pp-cli disks list
```
— List persistent disks matching the provided filters. If no filters are provided, returns all disks you have...
```
render-pp-cli disks retrieve
```
— Retrieve the persistent disk with the provided ID.
```
render-pp-cli disks update
```
— Update the persistent disk with the provided ID. The disk's associated service must be deployed and active for...

env-groups — Manage env groups

```
render-pp-cli env-groups create
```
— Create a new environment group.
```
render-pp-cli env-groups delete
```
— Delete the environment group with the provided ID, including all environment variables and secret files it contains.
```
render-pp-cli env-groups list
```
— List environment groups matching the provided filters. If no filters are provided, all environment groups are returned.
```
render-pp-cli env-groups retrieve
```
— Retrieve an environment group by ID.
```
render-pp-cli env-groups update
```
— Update the attributes of an environment group.

environments — Manage environments

```
render-pp-cli environments create
```
— Create a new environment belonging to the project with the provided ID.
```
render-pp-cli environments delete
```
— Delete the environment with the provided ID. Requires the environment to be empty (i.e., it must contain no services...
```
render-pp-cli environments list
```
— List a particular project's environments matching the provided filters. If no filters are provided, all environments...
```
render-pp-cli environments retrieve
```
— Retrieve the environment with the provided ID.
```
render-pp-cli environments update
```
— Update the details of the environment with the provided ID.

events — View events for a service, postgres or key value

```
render-pp-cli events <eventId>
```
— Retrieve the details of a particular event

key-value — Key Value allows you to interact with your Render Key Value instances.

```
render-pp-cli key-value create
```
— Create a new Key Value instance.
```
render-pp-cli key-value delete
```
— Delete a Key Value instance by ID.
```
render-pp-cli key-value list
```
— List Key Value instances matching the provided filters. If no filters are provided, all Key Value instances are...
```
render-pp-cli key-value retrieve
```
— Retrieve a Key Value instance by ID.
```
render-pp-cli key-value update
```
— Update a Key Value instance by ID.

logs — Logs allow you to retrieve logs for your services, Postgres databases, and redis instances. You can query for logs or subscribe to logs in real-time via a websocket.

```
render-pp-cli logs delete-owner-stream
```
— Removes the log stream for the specified workspace.
```
render-pp-cli logs delete-resource-stream
```
— Removes the log stream override for the specified resource. After deletion, the resource will use the workspace's...
```
render-pp-cli logs get-owner-stream
```
— Returns log stream information for the specified workspace.
```
render-pp-cli logs get-resource-stream
```
— Returns log stream override information for the specified resource. A log stream override takes precedence over a...
```
render-pp-cli logs list
```
— List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to...
```
render-pp-cli logs list-resource-streams
```
— Lists log stream overrides for the provided workspace that match the provided filters. These overrides take...
```
render-pp-cli logs list-values
```
— List all values for a given log label in the logs matching the provided filters.
```
render-pp-cli logs subscribe
```
— Open a websocket connection to subscribe to logs matching the provided filters. Logs are streamed in real-time as...
```
render-pp-cli logs update-owner-stream
```
— Updates log stream information for the specified workspace. All logs for resources owned by this workspace will be...
```
render-pp-cli logs update-resource-stream
```
— Updates log stream override information for the specified resource. A log stream override takes precedence over a...

maintenance — The

Maintenance

endpoints allow you to retrieve the latest maintenance runs for your Render services. You can also reschedule maintenance or trigger it to start immediately.

```
render-pp-cli maintenance list
```
— List scheduled and/or recent maintenance runs for specified resources.
```
render-pp-cli maintenance retrieve
```
— Retrieve the maintenance run with the provided ID.
```
render-pp-cli maintenance update
```
— Update the maintenance run with the provided ID. Updates from this endpoint are asynchronous. To check your update's...

metrics — The

Metrics

endpoints allow you to retrieve metrics for your services, Postgres databases, and redis instances.

```
render-pp-cli metrics get-active-connections
```
— Get the number of active connections for one or more Postgres databases or Redis instances.
```
render-pp-cli metrics get-bandwidth
```
— Get bandwidth usage for one or more resources.
```
render-pp-cli metrics get-bandwidth-sources
```
— Get bandwidth usage for one or more resources broken down by traffic source (HTTP, WebSocket, NAT, PrivateLink)....
```
render-pp-cli metrics get-cpu
```
— Get CPU usage for one or more resources.
```
render-pp-cli metrics get-cpu-limit
```
— Get the CPU limit for one or more resources.
```
render-pp-cli metrics get-cpu-target
```
— Get CPU target for one or more resources.
```
render-pp-cli metrics get-disk-capacity
```
— Get persistent disk capacity for one or more resources.
```
render-pp-cli metrics get-disk-usage
```
— Get persistent disk usage for one or more resources.
```
render-pp-cli metrics get-http-latency
```
— Get HTTP latency metrics for one or more resources.
```
render-pp-cli metrics get-http-requests
```
— Get the HTTP request count for one or more resources.
```
render-pp-cli metrics get-instance-count
```
— Get the instance count for one or more resources.
```
render-pp-cli metrics get-memory
```
— Get memory usage for one or more resources.
```
render-pp-cli metrics get-memory-limit
```
— Get the memory limit for one or more resources.
```
render-pp-cli metrics get-memory-target
```
— Get memory target for one or more resources.
```
render-pp-cli metrics get-replication-lag
```
— Get seconds of replica lag of a Postgres replica.
```
render-pp-cli metrics get-task-runs-completed
```
— Get the total number of task runs completed for one or more tasks. Optionally filter by state (succeeded/failed) or...
```
render-pp-cli metrics get-task-runs-queued
```
— Get the total number of task runs queued for one or more tasks.
```
render-pp-cli metrics list-application-filter-values
```
— List instance values to filter by for one or more resources.
```
render-pp-cli metrics list-http-filter-values
```
— List status codes and host values to filter by for one or more resources.
```
render-pp-cli metrics list-path-filter-values
```
— The path suggestions are based on the most recent 5000 log lines as filtered by the provided filters

metrics-stream — Manage metrics stream

```
render-pp-cli metrics-stream delete-owner
```
— Deletes the metrics stream for the specified workspace.
```
render-pp-cli metrics-stream get-owner
```
— Returns metrics stream information for the specified workspace.
```
render-pp-cli metrics-stream upsert-owner
```
— Creates or updates the metrics stream for the specified workspace.

notification-settings — Notification Settings allow you to configure which notifications you want to recieve, and where you will receive them.

```
render-pp-cli notification-settings list-notification-overrides
```
— List notification overrides matching the provided filters. If no filters are provided, returns all notification...
```
render-pp-cli notification-settings patch-owner
```
— Update notification settings for the owner with the provided ID.
```
render-pp-cli notification-settings patch-service-notification-overrides
```
— Update the notification override for the service with the provided ID.
```
render-pp-cli notification-settings retrieve-owner
```
— Retrieve notification settings for the owner with the provided ID. Note that you provide an owner ID to this...
```
render-pp-cli notification-settings retrieve-service-notification-overrides
```
— Retrieve the notification override for the service with the provided ID. Note that you provide a service ID to this...

organizations — Manage organizations

owners — Manage owners

```
render-pp-cli owners list
```
— List the workspaces that your API key has access to, optionally filtered by name or owner email address.
```
render-pp-cli owners retrieve
```
— Retrieve the workspace with the provided ID. Workspace IDs start with
```
tea-
```
. If you provide a user ID (starts with...

postgres — Postgres endpoints enable you to interact with your Render Postgres databases. You can manage databases, exports, recoveries, and failovers.

```
render-pp-cli postgres create
```
— Create a new Postgres instance.
```
render-pp-cli postgres delete
```
— Delete a Postgres instance by ID. This operation is irreversible, and all data will be lost.
```
render-pp-cli postgres list
```
— List Postgres instances matching the provided filters. If no filters are provided, all Postgres instances are returned.
```
render-pp-cli postgres retrieve
```
— Retrieve a Postgres instance by ID.
```
render-pp-cli postgres update
```
— Update a Postgres instance by ID.

projects — Manage projects

```
render-pp-cli projects create
```
— Create a new project.
```
render-pp-cli projects delete
```
— Delete the project with the provided ID. Requires all of the project's environments to be empty (i.e., they must...
```
render-pp-cli projects list
```
— List projects matching the provided filters. If no filters are provided, all projects are returned.
```
render-pp-cli projects retrieve
```
— Retrieve the project with the provided ID.
```
render-pp-cli projects update
```
— Update the details of a project. To update the details of a particular environment in the project, instead use the...

redis — Manage redis

```
render-pp-cli redis create
```
— Create a new Redis instance. This API is deprecated in favor of the Key Value API.
```
render-pp-cli redis delete
```
— Delete a Redis instance by ID. This API is deprecated in favor of the Key Value API.
```
render-pp-cli redis list
```
— List Redis instances matching the provided filters. If no filters are provided, all Redis instances are returned....
```
render-pp-cli redis retrieve
```
— Retrieve a Redis instance by ID. This API is deprecated in favor of the Key Value API.
```
render-pp-cli redis update
```
— Update a Redis instance by ID. This API is deprecated in favor of the Key Value API.

registrycredentials — Manage registrycredentials

render-pp-cli registrycredentials create-registry-credential

— Create a new registry credential.

render-pp-cli registrycredentials delete-registry-credential

— Delete the registry credential with the provided ID.

```
render-pp-cli registrycredentials list-registry-credentials
```
— List registry credentials matching the provided filters. If no filters are provided, returns all registry...

render-pp-cli registrycredentials retrieve-registry-credential

— Retrieve the registry credential with the provided ID.

```
render-pp-cli registrycredentials update-registry-credential
```
— Update the registry credential with the provided ID. Services that use this credential must be redeployed to use...

services — Services allow you to manage your web services, private services, background workers, cron jobs, and static sites.

```
render-pp-cli services create
```
— Creates a new Render service in the specified workspace with the specified configuration.
```
render-pp-cli services delete
```
— Delete the service with the provided ID.
```
render-pp-cli services list
```
— List services matching the provided filters. If no filters are provided, returns all services you have permissions...
```
render-pp-cli services retrieve
```
— Retrieve the service with the provided ID.
```
render-pp-cli services update
```
— Update the service with the provided ID.

task-runs — Manage task runs

```
render-pp-cli task-runs cancel
```
— Cancel a running task run with the provided ID.
```
render-pp-cli task-runs create-task
```
— Kicks off a run of the workflow task with the provided ID, passing the provided input data.
```
render-pp-cli task-runs get
```
— Retrieve the workflow task run with the provided ID.
```
render-pp-cli task-runs list
```
— List task runs that match the provided filters. If no filters are provided, all task runs accessible by the...
```
render-pp-cli task-runs stream-events
```
— Establishes a unidirectional event stream. The server sends events as lines formatted per the SSE spec. Clients...

tasks — Manage tasks

```
render-pp-cli tasks get
```
— Retrieve the workflow task with the provided ID.
```
render-pp-cli tasks list
```
— List workflow tasks that match the provided filters. If no filters are provided, all task definitions accessible by...

users — The

User

endpoints allow you to retrieve information about the authenticated user

```
render-pp-cli users
```
— Retrieve the user associated with the provided API key.

webhooks — Webhooks allows you to manage your Render webhook configuration.

```
render-pp-cli webhooks create
```
— Create a new webhook.
```
render-pp-cli webhooks delete
```
— Delete the webhook with the provided ID.
```
render-pp-cli webhooks list
```
— List webhooks
```
render-pp-cli webhooks retrieve
```
— Retrieve the webhook with the provided ID
```
render-pp-cli webhooks update
```
— Update the webhook with the provided ID.

workflows — Manage workflows

```
render-pp-cli workflows create
```
— Create a new workflow service with the specified configuration.
```
render-pp-cli workflows delete
```
— Delete the workflow service with the provided ID.
```
render-pp-cli workflows get
```
— Retrieve the workflow service with the provided ID.
```
render-pp-cli workflows list
```
— List workflows that match the provided filters. If no filters are provided, all workflows accessible by the...
```
render-pp-cli workflows update
```
— Update the workflow service with the provided ID.

workflowversions — Manage workflowversions

render-pp-cli workflowversions create-workflow-version

— Creates and deploys a new version of a workflow.

```
render-pp-cli workflowversions get-workflow-version
```
— Retrieve the specific workflow service version with the provided ID.
```
render-pp-cli workflowversions list-workflow-versions
```
— List known versions of the workflow service with the provided ID.

blueprints — Blueprints允许您在

render.yaml

文件中定义资源，并自动同步变更到Render服务。 API提供了对Blueprints创建和管理资源方式的控制。

```
render-pp-cli blueprints disconnect
```
— 断开指定ID的Blueprint。断开后，将停止通过Blueprint自动同步资源...
```
render-pp-cli blueprints list
```
— 列出指定工作区的Blueprint。如果未指定工作区，将返回API密钥有权访问的所有Blueprint...
```
render-pp-cli blueprints retrieve
```
— 获取指定ID的Blueprint详情。
```
render-pp-cli blueprints update
```
— 更新指定ID的Blueprint。
```
render-pp-cli blueprints validate
```
— 验证
```
render.yaml
```
Blueprint文件，无需创建或修改任何资源。此端点会检查语法...

cron-jobs — 管理定时任务

disks — Disks允许您为服务挂载持久存储。

```
render-pp-cli disks add
```
— 为Web服务、私有服务或后台工作者挂载持久磁盘。服务必须重新部署才能...
```
render-pp-cli disks delete
```
— 删除服务挂载的持久磁盘。**磁盘上的所有数据将丢失。**关联的服务...
```
render-pp-cli disks list
```
— 列出符合筛选条件的持久磁盘。如果未指定筛选条件，将返回您拥有的所有磁盘...
```
render-pp-cli disks retrieve
```
— 获取指定ID的持久磁盘详情。
```
render-pp-cli disks update
```
— 更新指定ID的持久磁盘。关联的服务必须处于已部署且活跃状态才能...

env-groups — 管理环境变量组

```
render-pp-cli env-groups create
```
— 创建新的环境变量组。
```
render-pp-cli env-groups delete
```
— 删除指定ID的环境变量组，包括其中所有环境变量和机密文件。
```
render-pp-cli env-groups list
```
— 列出符合筛选条件的环境变量组。如果未指定筛选条件，将返回所有环境变量组。
```
render-pp-cli env-groups retrieve
```
— 通过ID获取环境变量组详情。
```
render-pp-cli env-groups update
```
— 更新环境变量组的属性。

environments — 管理环境

```
render-pp-cli environments create
```
— 为指定ID的项目创建新环境。
```
render-pp-cli environments delete
```
— 删除指定ID的环境。要求环境为空（即不包含任何服务...
```
render-pp-cli environments list
```
— 列出指定项目中符合筛选条件的环境。如果未指定筛选条件，将返回所有环境...
```
render-pp-cli environments retrieve
```
— 获取指定ID的环境详情。
```
render-pp-cli environments update
```
— 更新指定ID的环境详情。

events — 查看服务、Postgres或键值存储的事件

```
render-pp-cli events <eventId>
```
— 获取指定事件的详情

key-value — Key Value允许您与Render Key Value实例交互。

```
render-pp-cli key-value create
```
— 创建新的Key Value实例。
```
render-pp-cli key-value delete
```
— 通过ID删除Key Value实例。
```
render-pp-cli key-value list
```
— 列出符合筛选条件的Key Value实例。如果未指定筛选条件，将返回所有Key Value实例...
```
render-pp-cli key-value retrieve
```
— 通过ID获取Key Value实例详情。
```
render-pp-cli key-value update
```
— 通过ID更新Key Value实例。

logs — Logs允许您获取服务、Postgres数据库和Redis实例的日志。您可以查询日志或通过WebSocket实时订阅日志。

```
render-pp-cli logs delete-owner-stream
```
— 删除指定工作区的日志流。
```
render-pp-cli logs delete-resource-stream
```
— 删除指定资源的日志流覆盖配置。删除后，资源将使用工作区的...
```
render-pp-cli logs get-owner-stream
```
— 返回指定工作区的日志流信息。
```
render-pp-cli logs get-resource-stream
```
— 返回指定资源的日志流覆盖信息。日志流覆盖配置优先级高于工作区的...
```
render-pp-cli logs list
```
— 列出符合筛选条件的日志。日志按开始和结束时间戳分页。还有更多日志...
```
render-pp-cli logs list-resource-streams
```
— 列出指定工作区中符合筛选条件的日志流覆盖配置。这些覆盖配置优先级...
```
render-pp-cli logs list-values
```
— 列出符合筛选条件的日志中指定日志标签的所有值。
```
render-pp-cli logs subscribe
```
— 打开WebSocket连接，订阅符合筛选条件的日志。日志将实时流式传输...
```
render-pp-cli logs update-owner-stream
```
— 更新指定工作区的日志流信息。该工作区下所有资源的日志将...
```
render-pp-cli logs update-resource-stream
```
— 更新指定资源的日志流覆盖信息。日志流覆盖配置优先级高于工作区的...

maintenance —

Maintenance

端点允许您获取Render服务的最新维护记录。您还可以重新安排维护时间或立即触发维护。

```
render-pp-cli maintenance list
```
— 列出指定资源的已计划和/或最近的维护记录。
```
render-pp-cli maintenance retrieve
```
— 获取指定ID的维护记录详情。
```
render-pp-cli maintenance update
```
— 更新指定ID的维护记录。此端点的更新是异步的。要检查更新的...

metrics —

Metrics

端点允许您获取服务、Postgres数据库和Redis实例的指标数据。

```
render-pp-cli metrics get-active-connections
```
— 获取一个或多个Postgres数据库或Redis实例的活跃连接数。
```
render-pp-cli metrics get-bandwidth
```
— 获取一个或多个资源的带宽使用情况。
```
render-pp-cli metrics get-bandwidth-sources
```
— 获取一个或多个资源按流量来源（HTTP、WebSocket、NAT、PrivateLink）拆分的带宽使用情况...
```
render-pp-cli metrics get-cpu
```
— 获取一个或多个资源的CPU使用率。
```
render-pp-cli metrics get-cpu-limit
```
— 获取一个或多个资源的CPU限制。
```
render-pp-cli metrics get-cpu-target
```
— 获取一个或多个资源的CPU目标值。
```
render-pp-cli metrics get-disk-capacity
```
— 获取一个或多个资源的持久磁盘容量。
```
render-pp-cli metrics get-disk-usage
```
— 获取一个或多个资源的持久磁盘使用率。
```
render-pp-cli metrics get-http-latency
```
— 获取一个或多个资源的HTTP延迟指标。
```
render-pp-cli metrics get-http-requests
```
— 获取一个或多个资源的HTTP请求数。
```
render-pp-cli metrics get-instance-count
```
— 获取一个或多个资源的实例数量。
```
render-pp-cli metrics get-memory
```
— 获取一个或多个资源的内存使用率。
```
render-pp-cli metrics get-memory-limit
```
— 获取一个或多个资源的内存限制。
```
render-pp-cli metrics get-memory-target
```
— 获取一个或多个资源的内存目标值。
```
render-pp-cli metrics get-replication-lag
```
— 获取Postgres副本的复制延迟秒数。
```
render-pp-cli metrics get-task-runs-completed
```
— 获取一个或多个任务已完成的任务运行总数。可按状态（成功/失败）或...筛选
```
render-pp-cli metrics get-task-runs-queued
```
— 获取一个或多个任务已排队的任务运行总数。
```
render-pp-cli metrics list-application-filter-values
```
— 列出一个或多个资源可用于筛选的实例值。
```
render-pp-cli metrics list-http-filter-values
```
— 列出一个或多个资源可用于筛选的状态码和主机值。
```
render-pp-cli metrics list-path-filter-values
```
— 路径建议基于符合筛选条件的最近5000条日志行生成

metrics-stream — 管理指标流

render-pp-cli metrics-stream delete-owner

— 删除指定工作区的指标流。

```
render-pp-cli metrics-stream get-owner
```
— 返回指定工作区的指标流信息。
```
render-pp-cli metrics-stream upsert-owner
```
— 创建或更新指定工作区的指标流。

notification-settings — Notification Settings允许您配置想要接收的通知类型和接收渠道。

```
render-pp-cli notification-settings list-notification-overrides
```
— 列出符合筛选条件的通知覆盖配置。如果未指定筛选条件，将返回所有通知...

render-pp-cli notification-settings patch-owner

— 更新指定ID所有者的通知设置。

render-pp-cli notification-settings patch-service-notification-overrides

— 更新指定ID服务的通知覆盖配置。

```
render-pp-cli notification-settings retrieve-owner
```
— 获取指定ID所有者的通知设置。请注意，您需要提供所有者ID给此...
```
render-pp-cli notification-settings retrieve-service-notification-overrides
```
— 获取指定ID服务的通知覆盖配置。请注意，您需要提供服务ID给此...

organizations — 管理组织

owners — 管理所有者

```
render-pp-cli owners list
```
— 列出API密钥有权访问的工作区，可按名称或所有者邮箱地址筛选。
```
render-pp-cli owners retrieve
```
— 获取指定ID的工作区详情。工作区ID以
```
tea-
```
开头。如果您提供的是用户ID（以...开头）

postgres — Postgres端点允许您与Render Postgres数据库交互。您可以管理数据库、导出、恢复和故障转移。

```
render-pp-cli postgres create
```
— 创建新的Postgres实例。
```
render-pp-cli postgres delete
```
— 通过ID删除Postgres实例。此操作不可逆，所有数据将丢失。
```
render-pp-cli postgres list
```
— 列出符合筛选条件的Postgres实例。如果未指定筛选条件，将返回所有Postgres实例。
```
render-pp-cli postgres retrieve
```
— 通过ID获取Postgres实例详情。
```
render-pp-cli postgres update
```
— 通过ID更新Postgres实例。

projects — 管理项目

```
render-pp-cli projects create
```
— 创建新的项目。
```
render-pp-cli projects delete
```
— 删除指定ID的项目。要求项目的所有环境为空（即必须...
```
render-pp-cli projects list
```
— 列出符合筛选条件的项目。如果未指定筛选条件，将返回所有项目。
```
render-pp-cli projects retrieve
```
— 获取指定ID的项目详情。
```
render-pp-cli projects update
```
— 更新项目详情。如果要更新项目中特定环境的详情，请改用...

redis — 管理Redis

```
render-pp-cli redis create
```
— 创建新的Redis实例。此API已废弃，建议使用Key Value API。
```
render-pp-cli redis delete
```
— 通过ID删除Redis实例。此API已废弃，建议使用Key Value API。
```
render-pp-cli redis list
```
— 列出符合筛选条件的Redis实例。如果未指定筛选条件，将返回所有Redis实例...
```
render-pp-cli redis retrieve
```
— 通过ID获取Redis实例详情。此API已废弃，建议使用Key Value API。
```
render-pp-cli redis update
```
— 通过ID更新Redis实例。此API已废弃，建议使用Key Value API。

registrycredentials — 管理注册表凭据

render-pp-cli registrycredentials create-registry-credential

— 创建新的注册表凭据。

render-pp-cli registrycredentials delete-registry-credential

— 删除指定ID的注册表凭据。

```
render-pp-cli registrycredentials list-registry-credentials
```
— 列出符合筛选条件的注册表凭据。如果未指定筛选条件，将返回所有注册表...

render-pp-cli registrycredentials retrieve-registry-credential

— 获取指定ID的注册表凭据详情。

```
render-pp-cli registrycredentials update-registry-credential
```
— 更新指定ID的注册表凭据。使用此凭据的服务必须重新部署才能使用...

services — Services允许您管理Web服务、私有服务、后台工作者、定时任务和静态站点。

```
render-pp-cli services create
```
— 在指定工作区中创建新的Render服务，使用指定配置。
```
render-pp-cli services delete
```
— 删除指定ID的服务。
```
render-pp-cli services list
```
— 列出符合筛选条件的服务。如果未指定筛选条件，将返回您有权访问的所有服务...
```
render-pp-cli services retrieve
```
— 获取指定ID的服务详情。
```
render-pp-cli services update
```
— 更新指定ID的服务。

task-runs — 管理任务运行

```
render-pp-cli task-runs cancel
```
— 取消指定ID的正在运行的任务。
```
render-pp-cli task-runs create-task
```
— 启动指定ID的工作流任务运行，并传递指定的输入数据。
```
render-pp-cli task-runs get
```
— 获取指定ID的工作流任务运行详情。
```
render-pp-cli task-runs list
```
— 列出符合筛选条件的任务运行。如果未指定筛选条件，将返回您有权访问的所有任务运行...
```
render-pp-cli task-runs stream-events
```
— 建立单向事件流。服务器按SSE规范格式发送事件行。客户端...

tasks — 管理任务

```
render-pp-cli tasks get
```
— 获取指定ID的工作流任务详情。
```
render-pp-cli tasks list
```
— 列出符合筛选条件的工作流任务。如果未指定筛选条件，将返回您有权访问的所有任务定义...

users —

User

端点允许您获取已认证用户的信息

```
render-pp-cli users
```
— 获取与指定API密钥关联的用户信息。

webhooks — Webhooks允许您管理Render Webhook配置。

```
render-pp-cli webhooks create
```
— 创建新的Webhook。
```
render-pp-cli webhooks delete
```
— 删除指定ID的Webhook。
```
render-pp-cli webhooks list
```
— 列出Webhook
```
render-pp-cli webhooks retrieve
```
— 获取指定ID的Webhook详情
```
render-pp-cli webhooks update
```
— 更新指定ID的Webhook。

workflows — 管理工作流

```
render-pp-cli workflows create
```
— 使用指定配置创建新的工作流服务。
```
render-pp-cli workflows delete
```
— 删除指定ID的工作流服务。
```
render-pp-cli workflows get
```
— 获取指定ID的工作流服务详情。
```
render-pp-cli workflows list
```
— 列出符合筛选条件的工作流。如果未指定筛选条件，将返回您有权访问的所有工作流...
```
render-pp-cli workflows update
```
— 更新指定ID的工作流服务。

workflowversions — 管理工作流版本

render-pp-cli workflowversions create-workflow-version

— 创建并部署工作流的新版本。

```
render-pp-cli workflowversions get-workflow-version
```
— 获取指定ID的特定工作流服务版本详情。

render-pp-cli workflowversions list-workflow-versions

— 列出指定ID工作流服务的已知版本。

Finding the right command

查找合适的命令

When you know what you want to do but not which command does it, ask the CLI directly:

bash

render-pp-cli which "<capability in your own words>"

which

resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code

means at least one match; exit code

means no confident match — fall back to

--help

or use a narrower query.

当您知道要做什么但不知道对应的命令时，可以直接询问CLI：

bash

render-pp-cli which "<用您自己的语言描述功能>"

which

命令会将自然语言的功能查询解析为CLI精选功能索引中最匹配的命令。退出码

表示至少有一个匹配项；退出码

表示没有确定的匹配项——请改用

--help

或更精确的查询。

Recipes

使用示例

Promote staging env to prod, exclude debug keys

将Staging环境变量同步到生产环境，排除调试密钥

bash

render-pp-cli env promote --from srv-staging --to srv-prod --exclude DEBUG_TOKEN,SENTRY_DEV_DSN

First diff to see what would change, then promote with the dev-only keys filtered out. Add --apply after review to actually issue the writes.

bash

render-pp-cli env promote --from srv-staging --to srv-prod --exclude DEBUG_TOKEN,SENTRY_DEV_DSN

先使用diff命令查看会发生哪些变化，然后排除仅用于开发的密钥后进行同步。审核后添加

--apply

参数以实际执行写入操作。

Find every service that uses a secret before rotating it

在轮换密钥前查找所有使用该密钥的服务

bash

render-pp-cli env where STRIPE_KEY --json --select 'service.name,service.id,updatedAt'

Returns service names, IDs, and timestamps for every place STRIPE_KEY is referenced — your rotation checklist.

bash

render-pp-cli env where STRIPE_KEY --json --select 'service.name,service.id,updatedAt'

返回所有引用STRIPE_KEY的服务名称、ID和时间戳——这就是您的轮换清单。

Friday cost rollup grouped by project

按项目分组的周五成本汇总

bash

render-pp-cli cost --group-by project --json --select 'project,monthly_usd,resource_count'

Joins cached service/postgres/kv/disk plans against a curated price table; export to CSV for finance.

bash

render-pp-cli cost --group-by project --json --select 'project,monthly_usd,resource_count'

将缓存的服务/Postgres/键值存储/磁盘计划与精选价格表关联；导出为CSV文件提供给财务部门。

Detect blueprint drift in CI

在CI中检测蓝图漂移

bash

render-pp-cli drift --blueprint render.yaml --json --quiet || exit 1

Exits non-zero when the live workspace diverges from the checked-in blueprint; wire it into your CI pipeline.

bash

render-pp-cli drift --blueprint render.yaml --json --quiet || exit 1

当实时工作区与已提交的蓝图不一致时，返回非零退出码；将其集成到您的CI流水线中。

Incident timeline for a service over the last 2 hours

服务过去2小时的事件时间线

bash

render-pp-cli incident-timeline srv-checkout-api --since 2h --json --select 'timestamp,kind,actor,summary'

Merges deploys + events + audit-logs into one chronological table — answers 'what changed' during an on-call page.

bash

render-pp-cli incident-timeline srv-checkout-api --since 2h --json --select 'timestamp,kind,actor,summary'

将部署记录+事件+审计日志合并为一个按时间排序的表格——回答值班告警期间“发生了哪些变化”的问题。

Auth Setup

认证设置

Render uses bearer-token auth. Set RENDER_API_KEY (generate one at https://dashboard.render.com/u/settings#api-keys), or run

render-pp-cli auth set-token <RENDER_API_KEY>

to paste it interactively. Every command sends

Authorization: Bearer <key>

; doctor verifies the key is live.

Run

render-pp-cli doctor

to verify setup.

Render使用Bearer令牌认证。设置RENDER_API_KEY（可在https://dashboard.render.com/u/settings#api-keys生成），或运行`render-pp-cli auth set-token <RENDER_API_KEY>

交互式粘贴令牌。每个命令都会发送

Authorization: Bearer <key>`；doctor命令会验证令牌是否有效。

运行

render-pp-cli doctor

验证设置是否正确。

Agent Mode

Agent模式

Add

--agent

to any command. Expands to:

--json --compact --no-input --no-color --yes

Pipeable — JSON on stdout, errors on stderr
Filterable —
```
--select
```
keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
bash
```
render-pp-cli blueprints list --agent --select id,name,status
```
Previewable —
```
--dry-run
```
shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use
```
--idempotent
```
only when an already-existing create should count as success, and
```
--ignore-missing
```
only when a missing delete target should count as success

在任何命令后添加

--agent

参数。它会展开为：

--json --compact --no-input --no-color --yes

。

可管道化 — 标准输出为JSON，错误输出到标准错误
可筛选 —
```
--select
```
参数保留字段子集。点路径可深入嵌套结构；数组可遍历元素。对于冗长的API，这是缩小上下文范围的关键：
bash
```
render-pp-cli blueprints list --agent --select id,name,status
```
可预览 —
```
--dry-run
```
参数显示请求但不发送
离线友好 — 同步/搜索命令在可用时可使用本地SQLite存储
非交互式 — 从不提示，所有输入均通过标志参数提供
显式重试 — 仅当已存在的创建操作应视为成功时使用
```
--idempotent
```
，仅当缺失的删除目标应视为成功时使用
```
--ignore-missing
```

Response envelope

响应包

Commands that read from the local store or the API wrap output in a provenance envelope:

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse

.results

for data and

.meta.source

to know whether it's live or local. A human-readable

N results (live)

summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

从本地存储或API读取数据的命令会将输出包装在来源信息包中：

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

解析

.results

获取数据，

.meta.source

表示数据是实时的还是本地的。仅当标准输出为终端时，才会向标准错误输出人类可读的

N results (live)

摘要——管道/Agent消费者仅会在标准输出获取纯JSON。

Agent Feedback

Agent反馈

When you (or the agent) notice something off about this CLI, record it:

render-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
render-pp-cli feedback --stdin < notes.txt
render-pp-cli feedback list --json --limit 10

Entries are stored locally at

~/.render-pp-cli/feedback.jsonl

. They are never POSTed unless

RENDER_FEEDBACK_ENDPOINT

is set AND either

--send

is passed or

RENDER_FEEDBACK_AUTO_SEND=true

. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

当您（或Agent）发现此CLI存在问题时，请记录反馈：

render-pp-cli feedback "--since参数是包含性的，但文档说是排他性的"
render-pp-cli feedback --stdin < notes.txt
render-pp-cli feedback list --json --limit 10

反馈条目存储在本地

~/.render-pp-cli/feedback.jsonl

文件中。除非设置了

RENDER_FEEDBACK_ENDPOINT

且传递了

--send

参数或

RENDER_FEEDBACK_AUTO_SEND=true

，否则反馈不会被POST发送。默认行为是仅存储在本地。

请写下让您感到意外的内容，而不是正式的错误报告。简短、具体、单行描述：这样的反馈才更有价值。

Output Delivery

输出交付

Every command accepts

--deliver <sink>

. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Sink	Effect
`stdout`	Default; write to stdout only
`file:<path>`	Atomically write output to `<path>` (tmp + rename)
`webhook:<url>`	POST the output body to the URL ( `application/json` or `application/x-ndjson` when `--compact` )

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

每个命令都支持

--deliver <sink>

参数。输出会发送到指定的目标，同时也会（或替代）输出到标准输出，这样Agent无需手动管道即可路由命令结果。支持三种目标：

输出目标	效果
`stdout`	默认值；仅输出到标准输出
`file:<path>`	原子性地将输出写入 `<path>` （先写入临时文件再重命名）
`webhook:<url>`	将输出内容POST到指定URL（使用 `--compact` 时为 `application/json` 或 `application/x-ndjson` 格式）

不支持的协议会返回结构化错误，并列出支持的类型。Webhook失败会返回非零退出码，并在标准错误输出日志中记录URL和HTTP状态码。

Named Profiles

命名配置文件

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

render-pp-cli profile save briefing --json
render-pp-cli --profile briefing blueprints list
render-pp-cli profile list --json
render-pp-cli profile show briefing
render-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults.

agent-context

lists all available profiles under

available_profiles

so introspecting agents discover them at runtime.

配置文件是一组保存的标志值，可在多次调用中复用。当定时Agent每次运行都使用相同配置调用同一命令时，可使用此功能——即HeyGen的“Beacon”模式。

render-pp-cli profile save briefing --json
render-pp-cli --profile briefing blueprints list
render-pp-cli profile list --json
render-pp-cli profile show briefing
render-pp-cli profile delete briefing --yes

显式标志参数始终优先于配置文件值；配置文件值优先于默认值。

agent-context

命令会在

available_profiles

下列出所有可用配置文件，以便自省Agent在运行时发现它们。

Async Jobs

异步任务

For endpoints that submit long-running work, the generator detects the submit-then-poll pattern (a

job_id

task_id

operation_id

field in the response plus a sibling status endpoint) and wires up three extra flags on the submitting command:

Flag	Purpose
`--wait`	Block until the job reaches a terminal status instead of returning the job ID immediately
`--wait-timeout`	Maximum wait duration (default 10m, 0 means no timeout)
`--wait-interval`	Initial poll interval (default 2s; grows with exponential backoff up to 30s)

Use async submission without

--wait

when you want to fire-and-forget; use

--wait

when you want one command to return the finished artifact.

对于提交长时间运行任务的端点，生成器会检测提交-轮询模式（响应中包含

job_id

task_id

operation_id

字段以及对应的状态端点），并为提交命令添加三个额外标志：

标志	用途
`--wait`	阻塞直到任务进入终端状态，而非立即返回任务ID
`--wait-timeout`	最大等待时长（默认10分钟，0表示无超时）
`--wait-interval`	初始轮询间隔（默认2秒；指数退避增长至30秒）

当您想触发即忘时，使用异步提交且不添加

--wait

；当您想让一个命令返回完成的结果时，使用

--wait

。

Exit Codes

退出码

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
4	Authentication required
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

错误码	含义
0	成功
2	使用错误（参数错误）
3	资源未找到
4	需要认证
5	API错误（上游问题）
7	速率限制（请等待后重试）
10	配置错误

Argument Parsing

参数解析

Parse

$ARGUMENTS

Empty,
help
, or
--help
→ show
```
render-pp-cli --help
```
output
Starts with
install
→ ends with
```
mcp
```
→ MCP installation; otherwise → see Prerequisites above
Anything else → Direct Use (execute as CLI command with
```
--agent
```
)

解析

$ARGUMENTS

：

为空、
help
或
--help
→ 显示
```
render-pp-cli --help
```
输出
以
install
开头 → 以
```
mcp
```
结尾 → MCP安装；否则 → 参见顶部的前提条件
其他内容 → 直接使用（以
```
--agent
```
标志执行CLI命令）

MCP Server Installation

MCP服务器安装

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

bash

claude mcp add render-pp-mcp -- render-pp-mcp

Verify:

claude mcp list

从本CLI的已发布公共库条目或预构建版本安装MCP二进制文件，然后注册：

bash

claude mcp add render-pp-mcp -- render-pp-mcp

验证：

claude mcp list

Direct Use

直接使用

Check if installed:
```
which render-pp-cli
```
If not found, offer to install (see Prerequisites at the top of this skill).
Match the user query to the best command from the Unique Capabilities and Command Reference above.

Execute with the

--agent

flag:

bash

render-pp-cli <command> [subcommand] [args] --agent

If ambiguous, drill into subcommand help:
```
render-pp-cli <command> --help
```
.

检查是否已安装：
```
which render-pp-cli
```
如果未找到，提供安装选项（参见顶部的前提条件）。
将用户查询与上述独特功能和命令参考中的最佳命令匹配。

使用

--agent

标志执行：

bash

render-pp-cli <command> [subcommand] [args] --agent

如果存在歧义，查看子命令帮助：
```
render-pp-cli <command> --help
```
。