CLI Reference

The Cloudwerk CLI provides commands for development, building, and deployment.

Installation

The CLI is included with @cloudwerk/cli:

pnpm add -D @cloudwerk/cli

Commands

cloudwerk dev

Start the development server with hot reload.

cloudwerk dev [path] [options]

Options:

Option	Description	Default
--port, -p	Port number	8787
--host, -H	Host to bind	localhost
--config, -c	Path to config file	Auto-detected
--verbose	Enable verbose logging	false

Examples:

# Start dev server
cloudwerk dev

# Custom port
cloudwerk dev --port 3000

# All interfaces
cloudwerk dev --host 0.0.0.0

# With custom config
cloudwerk dev --config cloudwerk.staging.ts

cloudwerk build

Build the application for production.

cloudwerk build [path] [options]

Options:

Option	Description	Default
--output, -o	Output directory	./dist
--ssg	Generate static pages for rendering: static routes	false
--minify	Minify bundles	true
--no-minify	Disable minification	-
--sourcemap	Generate source maps	false
--config, -c	Path to config file	Auto-detected
--verbose	Enable verbose logging	false

Examples:

# Production build
cloudwerk build

# With bundle analysis
cloudwerk build --sourcemap

# Development build
cloudwerk build --no-minify

# Static site generation
cloudwerk build --ssg

cloudwerk deploy

Deploy to Cloudflare Workers.

cloudwerk deploy [path] [options]

Options:

Option	Description	Default
--env, -e	Environment to deploy to	-
--dry-run	Preview without deploying	false
--skip-build	Skip the build step	false
--config, -c	Path to config file	Auto-detected
--verbose	Enable verbose logging	false

Examples:

# Deploy to production
cloudwerk deploy

# Deploy to staging
cloudwerk deploy --env staging

# Preview deployment
cloudwerk deploy --dry-run

cloudwerk config

Manage Cloudwerk configuration.

cloudwerk config <command> [options]

Subcommands:

Command	Description
get <key>	Get a configuration value
set <key> <value>	Set a configuration value

Examples:

# Get config value
cloudwerk config get appDir

# Set config value
cloudwerk config set dev.port 3000

cloudwerk bindings

Manage Cloudflare bindings (D1, KV, R2, Queues, etc.).

cloudwerk bindings [options]
cloudwerk bindings <command> [options]

Running without a subcommand shows an overview of all configured bindings.

Subcommands:

Command	Description
add [type]	Add a new binding (d1, kv, r2, queue, do, secret)
remove [name]	Remove a binding
update [name]	Update an existing binding
generate-types	Regenerate TypeScript type definitions

Examples:

# Show bindings overview
cloudwerk bindings

# Add D1 database
cloudwerk bindings add d1

# Add KV namespace
cloudwerk bindings add kv

# Remove a binding
cloudwerk bindings remove --force

# Regenerate types
cloudwerk bindings generate-types

cloudwerk triggers

Manage Cloudwerk triggers (scheduled, queue, R2, webhook, etc.).

cloudwerk triggers [options]
cloudwerk triggers <command> [options]

Running without a subcommand shows an overview of all triggers.

Subcommands:

Command	Description
list	List all triggers with details
validate	Validate trigger configurations
generate	Regenerate wrangler.toml and TypeScript types

Examples:

# Show triggers overview
cloudwerk triggers

# List all triggers
cloudwerk triggers list

# Filter by type
cloudwerk triggers list --type scheduled

# Validate configs
cloudwerk triggers validate --strict

# Regenerate config
cloudwerk triggers generate

# Output as JSON
cloudwerk triggers list --json

cloudwerk objects

Manage Cloudwerk Durable Objects.

cloudwerk objects [options]
cloudwerk objects <command> [options]

Running without a subcommand shows an overview of all durable objects.

Subcommands:

Command	Description
list	List all durable objects with details
info <name>	Show durable object details
migrations	Show migration history for SQLite durable objects
generate	Regenerate wrangler.toml and TypeScript types

Examples:

# Show objects overview
cloudwerk objects

# List all durable objects
cloudwerk objects list

# Show details for specific object
cloudwerk objects info Counter

# View migrations
cloudwerk objects migrations

# Regenerate config
cloudwerk objects generate

cloudwerk services

Manage Cloudwerk services (RPC bindings).

cloudwerk services [options]
cloudwerk services <command> [options]

Running without a subcommand shows an overview of all services.

Subcommands:

Command	Description
list	List all services with details
info <name>	Show service details
extract <name>	Extract service to separate Worker
inline <name>	Convert extracted service back to local mode
deploy <name>	Deploy extracted service
status	Show status of all services

Examples:

# Show services overview
cloudwerk services

# List all services
cloudwerk services list

# Show details for specific service
cloudwerk services info email

# Extract service to separate Worker
cloudwerk services extract payments

# Convert back to local mode
cloudwerk services inline payments

# Deploy extracted service
cloudwerk services deploy payments --env staging

# Show all services status
cloudwerk services status

Global Options

These options work with all commands:

Option	Description
--config, -c	Config file path
--help, -h	Show help
--version, -v	Show version
--verbose	Verbose output

Configuration

Commands read from cloudwerk.config.ts by default. Override with --config:

cloudwerk dev --config cloudwerk.production.ts

Exit Codes

Code	Description
0	Success
1	General error
2	Configuration error
3	Build error
4	Deployment error

Planned Commands

Coming Soon

The following commands are planned for future releases:

• cloudwerk generate — Scaffold pages, layouts, routes, middleware, components
• cloudwerk migrate — Database migrations (create, up, down, status, reset)
• cloudwerk routes — Display registered routes
• cloudwerk typecheck — Run TypeScript type checking
• cloudwerk lint — Run ESLint with Cloudwerk-specific rules
• cloudwerk test — Run Vitest tests with Cloudwerk test utilities

Next Steps

• Configuration - Config file options
• Deployment Guide - Deploy your app
• Testing - Testing utilities