Open-source AI penetration testing tool to find and fix your app’s vulnerabilities.
Python agentsai-hackingai-penetration-testingai-pentestingai-securityartificial-intelligencebug-bountycode-qualityctf-toolscybersecuritycybersecurity-toolsethical-hackinghackingllm-securityoffensive-securitypenetration-testingpentesting-toolsred-teamingsecuritysecurity-automation
docs(finish_scan): elevate the active-agent check to a mandatory pre-flight
0xallam6bdaa843d9ef
diff --git a/strix/tools/finish/tool.py b/strix/tools/finish/tool.pyindex 95dc623a..005cfc45 100644--- a/strix/tools/finish/tool.py+++ b/strix/tools/finish/tool.py@@ -86,14 +86,21 @@ async def finish_scan(2. Writes the four narrative sections to the scan record.3. Marks the scan completed and stops execution.- **Pre-flight checklist:**-- - All vulnerabilities you found are filed via- ``create_vulnerability_report`` (un-reported findings are not- tracked and not credited).- - All subagents have terminated. If any are still ``running`` /- ``stopping``, message them or use ``wait_for_message``.- - Don't double-report — one report per distinct vulnerability.+ **Pre-flight checklist (mandatory — do not skip):**++ 1. **Call ``view_agent_graph`` first.** Inspect every entry in the+ summary. If ANY agent is in ``running`` / ``waiting`` /+ ``llm_failed`` state, you MUST NOT call ``finish_scan`` yet —+ wrap them up first via ``send_message_to_agent`` (ask them to+ finish), ``wait_for_message`` (block until their report+ arrives), or ``stop_agent`` (graceful cancel). Only ``completed``+ / ``crashed`` / ``stopped`` agents are safe to leave behind.+ Calling ``finish_scan`` while children are alive orphans their+ work and produces an incomplete report.+ 2. All vulnerabilities you found are filed via+ ``create_vulnerability_report`` (un-reported findings are not+ tracked and not credited).+ 3. Don't double-report — one report per distinct vulnerability.**Calling this multiple times overwrites the previous report.**Make the single call comprehensive.