Describe a bot in plain English. Test it against your code. Deploy it alongside a swarm that scans, fixes, and ships PRs autonomously. Start with 6 built-in bots. Create your own in seconds.
6 built-in bots. Two pre-configured swarms. Zero setup.
Security + quality. Runs on every push.
Documentation that updates itself.
These are the starting point. The real power is building your own. →
Bots are data, not code. A system prompt, a config, a lifecycle. Create from the CLI or the chat UI.
{
"name": "large-component-detector",
"status": "active",
"description": "Flag React components over 300 lines",
"systemPrompt": "You are a code reviewer focused on
component size. Flag any React component
(.tsx/.jsx) whose function body exceeds
300 lines. Suggest extraction points.",
"config": {
"filePatterns": ["**/*.tsx", "**/*.jsx"],
"severity": "warning",
"batchSize": 10
}
}Every bot starts as a draft. Test it. Promote to shadow mode. Promote to active. No bot goes live without your approval.
Every swarm is a collection of bots. Mix built-in with your own.
Security scanning, code quality, CI hardening
README, architecture maps, API docs
License headers, GDPR annotations, audit trails
Hook rules, accessibility, bundle analysis
Breaking change detection, schema drift
Version bumps, CVE patches, license checks
Pipe to CI. Works with any model via OpenRouter.
GitHub App integration. Manage your swarm through conversation.
| Capability | Dependabot | Snyk | CodeRabbit | nanobots |
|---|---|---|---|---|
| Dependency updates | ✓ | ✓ | — | ✓ |
| Custom scanning rules | — | YAML | — | Natural language |
| Creates fix PRs | Version bumps | — | — | ✓ |
| Bot creation from description | — | — | — | ✓ |
| Swarm orchestration | — | — | — | ✓ |
| CLI + SaaS | — | ✓ | — | ✓ |
Only pay for people who push code.