Skip to main content
A result in Neo is not a summary. Every task leaves behind a working directory of artifacts: the reports Neo wrote, the scripts and tools it built, the HTTP traces it captured, the screenshots it took, and the evidence behind every finding. Neo doesn’t hand you a verdict and throw the work away. It keeps the work. Reading results is about getting at that material. Knowing where it lives, shaping it to your team’s conventions, and routing it into the tools you already use. Where verification decides what’s real before anything reaches you, results is what you do with everything once it has.
Confirmed findings and their proof artifacts (PoC scripts, traces, screenshots) are part of what you’ll find here, alongside every other output from the run. Verification is the gate; results is the full surface of what made it through, plus everything Neo produced along the way.

​
Artifacts are the output of every task

Neo isn’t just generating text. It’s writing code, running tools, and saving outputs as it works. At the bottom of every task, you’ll find the artifacts that run produced. Open any of them to see exactly what Neo built, what it ran, and what came back. The artifact renders in the form it was created in. A Markdown report renders as a report, a script shows its source, an HTTP trace shows the full request and response. Each artifact ties back to the step that created it, so the output is never separated from the work that produced it. As an example, a business logic pentest might leave behind a Markdown file like workflow-bypass-results.md: a report Neo wrote to document the workflow bypass and RBAC test results for that engagement. Open it and you see the finding, the steps that reproduced it, and the evidence that confirmed it, exactly as Neo recorded it during the run.

​
The Files workspace

Zoom out from a single task and the Files tab is your working directory across every run. Artifacts are organized by task, so a run from last week is still intact. You can go back and pull the exact evidence, script, or report Neo produced, attached to the task that created it. This is what makes results durable rather than disposable. The output of a task isn’t a transient summary that scrolls away. It’s a persistent record you can return to whenever a finding resurfaces, an auditor asks for evidence, or you want to reuse a script Neo wrote on a previous engagement.
Treat the Files tab as evidence storage. When you reopen a finding weeks later, the script, trace, and report are already there, attached to the run that created them.

​
Shaping results to your team

Results aren’t fixed. You can dictate exactly how they should look. Tell Neo the Markdown structure you want, or ask for findings in a specific format: CVSS 3.1 scores with reproduction steps and business impact, grouped by severity, written for a particular audience. Neo shapes the artifact to match. 
Write the results as a Markdown report. For each finding, include a
CVSS 3.1 score, reproduction steps, and business impact. Group by
severity, highest first.
You can also upload a PDF of a report format your team already uses and have Neo mimic it. Neo reads the structure, headings, and conventions from your existing report and produces new findings in the same shape, so the output drops straight into your established process instead of forcing you to reformat it.
  • Set the structure: specify the Markdown layout, sections, and ordering you want.
  • Set the scoring: ask for CVSS 3.1, severity labels, or whatever rating system your team uses.
  • Set the depth: reproduction steps, business impact, remediation guidance, code references. Include what your readers need.
  • Match an existing template: upload a report your team already uses and have Neo follow its format.

​
Delivering results where your team works

A result doesn’t have to stay a Markdown file or a PDF. When your integrations are connected, findings can land directly where your team already operates.
  • Jira and Linear: confirmed findings are filed as tickets with full evidence attached, including severity, reproduction steps, code references, and remediation guidance.
  • Slack: critical findings can ping a channel the moment they’re confirmed, so the right people see them without waiting for a report.
The output goes where your team already works, not into a document someone has to find and forward.
Delivery to Jira, Linear, and Slack requires the integration to be connected first. Set them up under Settings → Integrations. See the Linear and Slack integration guides for setup.

​
What this means for your team

Neo treats output as a first-class part of the work, not an afterthought. Everything it produces is saved, organized by task, shaped to fit your conventions, and delivered to the tools you already use. Nothing gets lost between the run and your team. Run a task, then open the Files tab. Once you see what’s actually getting saved, you’ll start asking Neo to produce a lot more of it.

Verification

How Neo proves every finding before it reaches your results.

Issues

The persistent vulnerability database where confirmed findings accumulate across runs.

Security Reporting & Compliance

Turn validated results into reports for engineering, leadership, and auditors.

Integrations

File findings into Linear or Jira and alert your team in Slack.