Command structure
All Clanker commands follow this structure:Core commands
ask
Ask natural language questions about your cloud infrastructure
k8s
Manage Kubernetes clusters and query workloads
config
Manage Clanker configuration and credentials
credentials
Store and manage cloud credentials in the backend
cost
View and analyze cloud infrastructure costs
deploy
Analyze and deploy GitHub repositories to the cloud
github
Query GitHub repository information directly
terraform
Manage Terraform workspace operations
postgres
Manage PostgreSQL database operations
AWS commands
aws maker
Generate infrastructure change plans for AWS
aws apply
Execute approved infrastructure plans on AWS
Global flags
These flags are available for all commands:Path to config file (default:
$HOME/.clanker.yaml)Enable debug output with progress and internal diagnostics
Enable local mode with rate limiting to prevent system overload
Delay in milliseconds between calls in local mode
Backend API key (or set
CLANKER_BACKEND_API_KEY)Backend environment:
testing, staging, or productionBackend API URL (overrides
--backend-env)Getting help
Get help for any command:Next steps
Ask command
Learn how to query infrastructure with natural language
Configuration
Set up your AI providers and cloud credentials