redeploy - Clawup

Updates agents in-place using pulumi up --refresh to sync cloud state and apply changes. Preserves existing infrastructure and Tailscale devices. If the stack doesn’t exist yet, falls back to a fresh deploy. Like deploy, this command automatically validates secrets and configures Pulumi before redeploying.

Usage

clawup redeploy [options]

Options

Option	Description
`-y, --yes`	Skip confirmation prompt
`-l, --local`	Redeploy local Docker containers
`--env-file <path>`	Path to `.env` file (defaults to `.env` in project root)
`--skip-hooks`	Skip plugin lifecycle hook execution

What It Does

Validates secrets and configures Pulumi (cloud deploys only)
Selects the existing Pulumi stack (or creates one if missing)
Syncs manifest and config to the Pulumi project
Cleans up stale Tailscale devices (cloud only)
Runs pulumi up --refresh to read actual cloud state and apply changes
Displays updated agent details (IPs, Tailscale URLs)

Local Docker Mode

Use --local to redeploy local Docker containers:

clawup redeploy --local

This targets the <stackName>-local Pulumi stack, copies config from the cloud stack (skipping Tailscale keys), and updates containers in-place. No Tailscale setup is performed.

Examples

# Redeploy with confirmation
clawup redeploy

# Redeploy without confirmation
clawup redeploy --yes

# Redeploy local Docker containers
clawup redeploy --local --yes

Use redeploy after changing config values (clawup config set) or secrets (clawup secrets set) to apply changes to running agents.

If an in-place update can’t recover, do a clean rebuild: clawup destroy -y && clawup deploy -y

​Usage

​Options

​What It Does

​Local Docker Mode

​Examples

Usage

Options

What It Does

Local Docker Mode

Examples