Get the source from reflectionai/laser. Repository access is currently required.
Quickstart
Install Laser and run a local lab engagement.
Developer guide
Configure models, workers, Docker, and live controls.
How Laser works
Thelaser launcher prepares a workspace and records the authorized scope. The executor investigates inside Mirror, saving observations, traffic, and findings to the evidence ledger. It can delegate independent tasks to workers sharing that ledger.
At review checkpoints, a separate supervisor model reads a brief and proposes the next plan. It cannot execute tools. Laser checks the plan against recorded progress before the executor continues.
Tool captures preserve evidence; findings and attack relationships must be recorded explicitly. Review the saved support before accepting a result: an agent’s verified verdict is not independent reproduction.
Monitor and control engagements
Use/laser inside Mirror to expand the native panel, or /laser-brief to print its cached decision brief.
The web UI can launch engagements, monitor terminals, send follow-up input, and stop runs and their workers. It supports host execution and configured Docker profiles.
Overview summarizes outcomes and evidence issues. Evidence compares saved captures; Findings shows each claim’s support; Attack graph shows recorded relationships. Graph connections alone do not establish successful execution.
Choose an engagement mode
src is not a source-code auditing mode. The CLI defaults to redteam; the setup wizard offers ctf. Set a different objective with --objective. A supervisor stop does not necessarily mean success.