brev-cli

Automate lifecycle management of Brev instances with approval guardrails.

179|21|Updated Apr 28, 2026

Search Tags:#automation #deployment #cli #lifecycle #guardrails #instance #brev

Ready to run

npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill brev-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brev-cli
Source: https://github.com/NVIDIA-Omniverse/content-agents/tree/main/.agents/skills/brev-cli
Command: npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill brev-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brev CLI enables safe, centralized management of Brev instances for Content Agents deployments, reducing manual overhead and risk.

Core Features & Use Cases

Create, list, access, port-forward, stop, and delete Brev instances with guardrails.
Enforce explicit approvals before destructive actions and provide lifecycle visibility across environments.
Support common deployment workflows for Content Agents, including multi-environment provisioning and resource cleanup.

Quick Start

Use the brev-cli to list Brev instances and perform a dry-run before creating resources.

Frequently Asked Questions about brev-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Brev instance lifecycle management for deployments?▼

You can automate Brev instance lifecycle management by using the Brev CLI to safely list, create, access, port-forward, stop, and delete instances across multiple environments with enforced guardrails and explicit user approvals for destructive operations.

What is the safest way to delete Brev instances across multiple environments?▼

The safest way to delete Brev instances is to use a CLI tool that enforces explicit user approval before executing destructive operations, ensuring resource cleanup is intentional and providing lifecycle visibility across multiple environments.

Do I need SSH access to manage Brev instances from the command line?▼

Yes, managing Brev instances from the command line requires SSH access to the created instances, along with an installed and authenticated Brev CLI to execute lifecycle management commands safely and apply guardrails.

How do I perform a dry-run before creating new Brev instances?▼

To perform a dry-run before creating new Brev instances, use the Brev CLI to first list existing instances and validate your deployment configuration, ensuring safety constraints and guardrails are met before provisioning new resources.

Can I port-forward to a Brev instance using the Brev CLI?▼

Yes, you can port-forward to a Brev instance using the Brev CLI, which supports common deployment workflows for Content Agents by enabling secure access and network routing to the created instances across environments.

What limitations exist when using CLI guardrails for instance management?▼

Limitations of CLI guardrails for instance management include the strict requirement for explicit user approval before destructive operations, meaning automated cleanup scripts cannot bypass safety constraints without manual confirmation.