red-run

What the README says you get

• Deploy
  Installer setupThe installer sets up the orchestrator, teammate templates, and MCP servers
• Other
  Engagement state databasetracks engagement state in a SQLite database that persists across context compactions
• Other
  Semantic skill routingroutes to skills via semantic search (RAG)
• Other
  Persistent domain teammatesdelegates execution to persistent domain teammates that accumulate context across tasks
• Other
  Multiple orchestrator variantsred-run supports multiple orchestrator variants that share the same skills, MCP servers, and engagement state
• Other
  Shared engagement state across variantsAll orchestrators write to the same `engagement/state.db`
• Other
  ChromaDB skill indexingindexes `skills/` into ChromaDB for semantic retrieval
• Other
  Shell serverstarts the shell-server
• Other
  Preflight dependency checkrun the preflight check to verify attackbox dependencies
• Other
  C2 config wizardrun the config wizard before launching
• Other
  Sliver C2 supportCurrently supported: Sliver
• Other
  Persistent SSE shell serviceThe shell-server runs as a persistent SSE service (`127.0.0.1:8022`) shared across all teammates
• Other
  State dashboardBrowser-based read-only dashboard for `engagement/state.db` with an access chain graph and live SSE updates
• Other
  Dashboard auth tokengenerate an auth token — the server will bind to `0.0.0.0` and require the token

Extracted from the kit's README by a local AI model (deepseek-flash) on Sep 29, 2026. Every item is checked against an exact README quote. A README claim is the maker's description, not something we tested.