Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
autonomous systems engineering cli agent for any cloud environment: AWS, GCP, Cloudflare, etc
| Date | Stars |
|---|---|
| 2026-07-31 | 371 |
| 2026-08-06 | 371 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
15.0
growth rate 0.00%/day
# 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/)
Language: English | [简体中文](README.zh-CN.md)
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
- Provider CLIs only for the providers you want Clanker to inspect or manage
```bash
clanker onboarding scan
clanker onboarding scan --provider aws,gcp,azure,kubernetes,flyio,linear,notion --format json
clanker onboarding install --dry-run --provider aws,gcp,azure,kubernetes,flyio
clanker onboarding install --yes aws gcloud az kubectl flyctl
```
`clanker onboarding scan` detects local credentials and missing provider CLIs,
then returns official install docs, auth commands, and token/account URLs for
users and agents. Install only the tools needed for selected or detected
providers. Examples: AWS uses the official AWS CLI installer and local profiles,
GCP uses the official Google Cloud CLI plus Application Default Credentials, and
Azure uses the official Azure CLI sign-in flow. Agents that have been asked to
install or use Clanker Cloud should run the install step, rerun the scan, then
walk any remaining browser login, SSO, sudo, or official API-token step with the
user.
## 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 COHERE_API_KEY="..."
```
### No config file defaults
If you run without `~/.clanker.yaml`:
- Default provider: `openai` (unless you pass `--ai-profile`).
- OpenAI key order: `--openai-key` → `OPENAI_API_KEY` (also supports `ai.providers.openai.api_key` and `ai.providers.openai.api_key_env` if config exists).
- Gemini API key order (when using `--ai-profile gemini-api`): `--gemini-key` → `GEMINI_API_KEY` (also supports `ai.providers.gemini-api.api_key` and `ai.providers.gemini-api.api_key_env` if config exists).
- Cohere API key order (when using `--ai-profile cohere`): `--cohere-key` → `COHERE_API_KEY` (also supports `ai.providers.cohere.api_key` and `ai.providers.cohere.api_key_env` if config exists).
- Model: `openai` defaults to `gpt-5`; `gemini`/`gemini-api` defaults to `gemini-2.5-flash`; `cohere` defaults to `command-a-03-2025`.
### AWS
Clanker uses your local AWS CLI profiles (not raw access keys in the clanker config).
Create a profile with the official AWS CLI. Prefer SSO where your AWS account
supports it; use access keys only when your account requires them.
```bash
aws configure sso
aws sso login --profile clankercloud-tekbog
aws configure --profile clankercloud-tekbog | cat
aws sts get-caller-identity --profile clankExcerpt of 38,373 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:a69c967f2b0e58ca, llm:Repository topics and description: 'agent, ai, ai-agent, ai-ops, autonomous systems engineering cli agent for any cloud environment: AWS, GCP, Cloudflare, etc' and languages: Go.
matched fp:a69c967f2b0e58ca, llm:Repository topics and description: 'agent, ai, ai-agent, ai-ops, autonomous systems engineering cli agent for any cloud environment: AWS, GCP, Cloudflare, etc' and languages: Go.
matched fp:a69c967f2b0e58ca, llm:Repository topics and description: 'agent, ai, ai-agent, ai-ops, autonomous systems engineering cli agent for any cloud environment: AWS, GCP, Cloudflare, etc' and languages: Go.
matched fp:a69c967f2b0e58ca, llm:Repository topics and description: 'agent, ai, ai-agent, ai-ops, autonomous systems engineering cli agent for any cloud environment: AWS, GCP, Cloudflare, etc' and languages: Go.