Autobb Analyst

AutoBB Analyst

🇷🇺 [Русская версия](README.ru.md)

Autonomous bug bounty agent driven by [autobb](https://github.com/rivalsec/autobb) reconnaissance. A Telegram bot forwards alerts and chat messages to Claude Code CLI, which **actively pentests targets** using recon data from [autobbmcp](https://github.com/rivalsec/autobbmcp) and a persistent knowledge wiki.

The agent doesn't just summarize — it picks targets, runs real probes, reports only verified findings, and keeps its own wiki of programs, hosts, tech, techniques, findings and dead-ends across sessions.

Requirements

• Docker + Docker Compose
• autobbmcp checked out as a sibling directory (../autobbmcp)
• MongoDB with database autobbdb (populated by autobb) reachable from the host
• Claude Code CLI — installed and authenticated
• Telegram Bot Token (via @BotFather)

Quick Start

1. Clone and configure

git clone https://github.com/rivalsec/autobb-analyst && cd autobb-analyst
cp config.dist.yaml config.yaml

Edit `config.yaml`:

telegram:
  token: "123456:ABC-DEF..."        # token from BotFather
  chat_id: "-1001234567890"         # chat/group ID
  autobb_bot_id: 1871687898         # autobb bot user ID
  ignore_patterns:                  # optional: skip noisy messages
    - "Is something wrong with nuclei templates?"

claude:
  cli_path: "claude"
  timeout: 300

2. Generate Claude Code auth token

claude setup-token
echo "CLAUDE_CODE_OAUTH_TOKEN=" > .env

**Alternative: a non-Anthropic model (z.ai / GLM, etc.)**

The bot can drive the CLI through any Anthropic-compatible endpoint instead of Anthropic — e.g. [z.ai](https://z.ai)'s GLM coding models. Set `claude.base_url` in `config.yaml`, use the provider's own model IDs, and put the provider key in `.env` under the name you reference via `auth_token_env`:

claude: