agentuity-cli-cloud-env-set

Set an environment variable. Requires authentication. Use for Agentuity cloud platform operations

⭐3stars🔀5forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The agentuity-cli-cloud-env-set skill allows developers to programmatically manage environment variables for the Agentuity cloud platform. It streamlines DevOps workflows by enabling the configuration of application settings, such as ports and runtime environments, directly through a CLI-integrated agent, ensuring consistent and automated infrastructure management.

Use Cases

  • Production Deployment: Quickly set the NODE_ENV to 'production' to ensure the application runs with optimized performance settings in the cloud.
  • Network Configuration: Dynamically update the application's listening port (e.g., setting PORT to 3000) to align with infrastructure or load balancer requirements.
  • Runtime Debugging: Adjust the LOG_LEVEL to 'debug' or 'info' in real-time to facilitate troubleshooting and monitoring of cloud-hosted services.
  • Automated Provisioning: Integrate environment variable setup into automated scripts to ensure new project environments are configured correctly upon creation.
nameagentuity-cli-cloud-env-set
descriptionSet an environment variable. Requires authentication. Use for Agentuity cloud platform operations
version"0.0.103"
licenseApache-2.0
allowed-tools"Bash(agentuity:*)"
argument-hint"<key> <value>"
command"agentuity cloud env set"
tags"mutating updates-resource slow requires-auth requires-project"

Cloud Env Set

Set an environment variable

Prerequisites

  • Authenticated with agentuity auth login
  • Project context required (run from project directory or use --project-id)

Usage

agentuity cloud env set <key> <value>

Arguments

Argument Type Required Description
<key> string Yes -
<value> string Yes -

Examples

Run production command:

bunx @agentuity/cli env set NODE_ENV production

Run 3000 command:

bunx @agentuity/cli env set PORT 3000

Run debug command:

bunx @agentuity/cli env set LOG_LEVEL debug

Output

Returns JSON object:

{
  "success": "boolean",
  "key": "string",
  "path": "string"
}
Field Type Description
success boolean Whether the operation succeeded
key string Environment variable key
path string Local file path where env var was saved