Your agent’s security advisor.
There for every change.

New flaws stopped, existing ones fixed at source and your scanner backlog cleared, by your agents as they work.

  • Claude Code
  • Codex
  • GitHub Copilot
  • Cursor
  • Devin
  • Gemini CLI
  • Antigravity
  • Windsurf
  • OpenCode
  • Hermes Agent

One prompt to set up. Then every change is secure.

LeoTrace runs inside the coding agent you already use, so nothing in your pipeline changes.

  1. 01

    Your agent finishes its turn. LeoTrace reads exactly what it changed, and the code that change reaches.

  2. 02

    It picks the rules that apply to that change, written from real incidents.

  3. 03

    A security judge reads the whole file and decides.

  4. 04

    Anything it finds goes back to your agent with the reason, before you see done.

  5. 05

    When your agent has acted, LeoTrace reads the change again.

WHAT IT DOES

Five jobs, one advisor.
Three as your agent works, two at scale.

Your agent writes code. No new flaw goes with it. LeoTrace checks the code your agent just wrote. If there is a flaw, the agent fixes it before you see done.

The flaws only a security expert would catch. LeoTrace spots the flaws already in the files your agent touches, and advises your agent to fix them in the same turn when it is safe.

Your scanner findings, cleared as you work. Connect the AppSec tool you already use. Real findings are fixed in the turn, and the rest are closed as false positives, with the reason.

Your whole backlog, in one sweep. Run one command and your agent works through every open finding, with LeoTrace confirming each one.

Prove what agents wrote. Reviewed inside the agent, before a PR exists. Then the record: how much of your code AI wrote and which files we reviewed, by agent and engineer.

Ship knowing every change was checked.

A security advisor checks every change your agent makes, so a flaw is fixed while you are still in the file, not in a ticket next sprint.

With LeoTrace: the same five flaws, each fixed in the turn, and no fix pull requests

Your judgement, in every agent.

LeoTrace applies AppSec judgement at the moment code is written, so your team spends its time on the findings that need a person.

Every change attested.
Down to the file.

Reviewed in the turn, not at the PR.

Roll it out across every team. With one standard for every agent.

Match your org tree, sign in with SSO and SCIM, set policies per workspace and keep a full audit trail.

Org tree

Workspaces that match how you report.

SSO and SCIM

People added and removed by your identity provider.

Policies

Rules for each workspace, set once.

ISO 27001

Certified, with a Trust Centre for your review.

Questions engineers ask

Only on turns that changed code, and only while the review runs.

Any model your agent runs. LeoTrace reviews the code, not the model.

Tell the agent. An answered finding is not raised again for 30 days.

Yes. On a turn that changed code, the changed files, the local helpers they import and your prompt go to LeoTrace for review. A sweep, only when you run it, sends the whole files that hold open scanner findings. The Trust Centre lists exactly what is sent.

Yes. The plugin is open source under Apache 2.0 and builds byte for byte from source, so you can check exactly what it sends. It holds no rules: those stay on our server. View on GitHub

Your agent’s security advisor, one prompt away.

  • Works in the coding agent you already use
  • Reviews start on your next turn
  • ISO 27001 certified
What should we cover?