Long-running pentest orchestration with independent verification
Vigil keeps offensive security engagements alive across restarts, verifies findings against captured evidence, and exports submission-ready reports.
- LinkLoot access
- Free
- Provider costs
- Unknown
What you get from it
What it does
Vigil is an AI harness for long-running offensive security work: web app pentests, bug bounty hunting, white-box code audits, or both against one target. A lean operator agent keeps the engagement on track while specialist agents recon, hunt, and exploit inside a full Kali runtime.
Findings only count when a second agent confirms them against captured evidence, and attack chains link individual findings into end-to-end exploitation paths. Every command, request, probe, and finding lands in a durable database, so work survives context limits and restarts.
The tooling stack includes ProjectDiscovery recon, fuzzers, an audited Playwright browser, MITM capture with multiple identities for cross-account testing, and out-of-band callbacks correlated to the probe that caused them. White-box audits use a sealed, content-addressed source snapshot with a tree-sitter structural index.
Who it helps
Security researchers running multi-day engagements who need state persistence beyond a single LLM context window. Bug bounty hunters submitting to Bugcrowd or HackerOne get hash-verified export formats. Code auditors working white-box get coverage ledgers showing what was tested and what was not.
Getting started
Requires Python 3.11+. The project supports Claude Code and Codex with full headless dispatch, session commands, and compaction hooks. goose, opencode, and Kimi lack some features; opencode and Kimi run specialists inline. Target-facing commands run through vigil assess kali, which records each command's argv, agent, phase, technique, intent, probe kind, exit status, and output.
Limits and costs
Authorized use only. Vigil autonomously drives offensive tooling against live systems. Use it only with explicit authorization and a reviewed scope. It is provided without warranty under Apache License 2.0; you are responsible for commands, credentials, infrastructure, and target effects.
Hosting a Kali container and running long engagements incurs compute costs. No pricing is documented. Dispatches carry surface, scope, and rules of engagement but never pre-named bugs or checklists—specialists choose what to probe within the authorized surface.
Source links
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in