Skip to main content
Vigolium’s agent mode runs vulnerability scans with an LLM in the loop. Three subcommands cover the spectrum from single-shot prompts to fully autonomous pentests:
  • vigolium agent query: one-shot prompt against code or a target. Code review, endpoint discovery, secret hunt. No scanning loop.
  • vigolium agent swarm: multi-phase pipeline where native Go does the heavy lifting and AI intervenes at checkpoints (planning attacks, triaging results, generating custom JS extensions).
  • vigolium agent autopilot: one autonomous operator with full tool access. It can run as a legacy conversation or as durable, resumable sections with candidate verification.
All three dispatch through the in-process olium runtime, one unified provider interface, one conversation state. There are no subprocess SDK backends.
Autopilot and Swarm are still maturing. We greatly appreciate feedback on false positives and bug reports.

Prerequisites

  • A working olium provider (Claude / OpenAI / Codex / local). See Setting Up the Agent.
  • Optional: a source-code path or git URL for source-aware scanning (--source).
Smoke-test the provider before launching a real scan:
If that returns a model name, you’re wired up.

Autopilot, autonomous AI pentest

Hand the agent a target and walk away. It opens a shell, reads files, runs the vigolium CLI, decides which modules to invoke, and iterates until it calls halt_scan or hits the max-turns / max-duration cap.

Intensity presets

To enable durable context rotation and verification, set agent.olium.autopilot_mode: enforced in vigolium-configs.yaml. You can then continue an interrupted run with:
Reach for autopilot when the target is fuzzy, JS-heavy, auth-walled, or you want creative / exploratory testing. See Autopilot for the full flag reference.

Swarm, AI-guided multi-phase scan

The agent directs the native scanner instead of becoming it. A state-machine pipeline runs: normalize → auth → source-analysis → code-audit → discover → plan (AI) → extension → native scan → triage (AI) → optional rescan loop.
Reach for swarm when you have a known-good request, want bespoke fuzzing tailored to it, or need a verification loop on findings. See Swarm for the full pipeline reference.

Source-aware scanning (--source)

Both autopilot and swarm accept --source <path|git-url|archive>. When set, vigolium-audit runs first (foreground), prepares a frozen whitebox context bundle, then the autonomous scan launches against that context.
--source accepts local paths, git URLs (cloned with --depth 1 by default), or archive files. For a standalone source audit without a scan, see Agentic Security Audit.

Picking between autopilot and swarm

If you have both source code and a target URL, both work. swarm --source --target ... --code-audit --triage gives the most structured output; autopilot --source ... gives the agent more freedom.

Sessions and findings

Every agent run writes a session directory under ~/.vigolium/agent-sessions/<run-uuid>/ with the checkpoint, plan, rendered prompts, captured output, and any generated extensions. Browse past runs with:
Findings ingest into the same findings table as native scans, tagged by source (autopilot, swarm, audit, piolium). Query them with:

Next steps

  • Autopilot, autonomous operator: full flag reference, intensity presets, halt conditions.
  • Swarm, multi-phase pipeline: phases, extension generation, triage loop.
  • Agent Mode, the full reference for every vigolium agent subcommand.
  • Agentic Security Audit, whitebox source-code audit (vigolium-audit + piolium).
  • Setting Up the Agent, provider/credential setup.