bgdnvk/clanker

Registry

Summary

Clanker is an autonomous systems engineering CLI agent built in Go, designed to manage cloud infrastructure across AWS, GCP, Cloudflare, and Kubernetes environments. It leverages AI to automate DevOps, SRE, and observability tasks, integrating with tools like Terraform and Harness for intelligent infrastructure operations.

Key features

• Multi-cloud CLI agent for AWS, GCP, Cloudflare, and Kubernetes
• AI-driven automation for DevOps, SRE, and observability workflows
• Built with Go for high performance and portability
• Integrates with Terraform and Harness for infrastructure as code
• Supports Cloudflare Workers and edge computing deployments

Use cases

• Automate cloud infrastructure provisioning and management
• Streamline incident response and observability with AI agents
• Manage multi-cloud environments from a single CLI
• Deploy and scale Kubernetes clusters intelligently
• Integrate AI-ops into existing DevOps pipelines

README excerpt

# Clanker CLI <p> <img src="assets/clanker-logo.png" alt="Clanker logo" width="96" height="96"> </p> Agent swarm powering [Clanker Cloud](https://clankercloud.ai), the first AI DevOps IDE for agents and humans. Docs available at [docs.clankercloud.ai](https://docs.clankercloud.ai/) Ask questions about your infra (and optionally GitHub/etc). Clanker can inspect existing environments and also generate or apply infrastructure and deploy plans through its maker and deploy flows. Repo: [bgdnvk/clanker](https://github.com/bgdnvk/clanker) Homebrew tap: [clankercloud/homebrew-tap](https://github.com/clankercloud/homebrew-tap) ## Install ### Homebrew (can be outdated, the best is to build from master) ```bash brew tap clankercloud/tap brew install clanker ``` ### From source ```bash make install ``` ### Self-update ```bash clanker update ``` By default, `clanker update` replaces the current binary with the latest GitHub release from `bgdnvk/clanker`. To track the latest commit on the repository's default branch instead, set the update channel during setup: ```bash clanker config init --update-channel main ``` or edit `~/.clanker.yaml`: ```yaml update: channel: main # release or main ``` You can also override it for one run: ```bash clanker update --channel release clanker update --channel main ``` ### Requirements - Go - AWS CLI v2 (recommended; v1 breaks `--no-cli-pager`) ```bash brew install awscli ``` ## Config Copy the example config and edit it for your environments/providers: ```bash cp .clanker.example.yaml ~/.clanker.yaml ``` alternatively you can do `clanker config init` Most providers use env vars for keys (see [.clanker.example.yaml](.clanker.example.yaml)), e.g.: ```bash export OPENAI_API_KEY="..." export GEMINI_API_KEY="..." export

Topics