Skip to content

[BUG] Report generated during scan but not saved on exit (no .md file, exit with vulnerabilities to 0) #294

@JNX03

Description

@JNX03

When running Strix, it appears to successfully generate a vulnerability report during execution (shows “Creating report…”). However, after exiting Strix, the report is not saved to disk. The final result shows 0 vulnerabilities, and no .md report file is created, so the generated report cannot be viewed.

To Reproduce

Steps to reproduce the behavior:

  1. Run Strix normally on a target.
    Example command used for testing:

    strix --target http://localhost:10010 --instruction "test report (you report an Vulnerabilities as 'INFO' and 'High' with 'Test' for description to make sure you able to report) and done you are job is done"
  2. Let the scan complete and wait until it shows “Creating report…”.

  3. Exit Strix.

  4. Check the output directory / project folder for the generated report.

Expected behavior

Strix should save the generated report to disk after the scan finishes.
The vulnerability count should persist, and a .md report file should be created so the findings can be reviewed.

Screenshots

Scan shows report being created:
scan report

More output during scan:
scan output

After exit, vulnerabilities reset to 0 and no report exists:
after exit

System Information

  • OS: Windows 11 (run via Git Bash)

  • Strix Version or Commit: 0.7.0

  • Python Version: 3.13.7

  • LLM Used: GLM 4.7

    • Also tested with: gemini-3-pro-preview, gpt-5.2

Additional context

This looks like the report writer does not persist data on exit or does not flush/write the report to disk. It may be related to output path handling or missing save logic. No error is shown, but the report is silently lost.

It feels like the report exists only in memory and is discarded when the process exits.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions