[aw] Detection Runs
Author: github-actions[bot]Created Sep 13, 2026Updated Sep 17, 2026
Labelsagentic-workflows
This issue tracks all runs where threat detection flagged problems in agentic workflows in this repository. Each workflow run that completes with a detection warning or failure posts a comment here.
What is a Detection Problem?A detection problem occurs when the threat detection system either:
- Detects potential security threats (prompt injection, secret leak, malicious patch)
- Fails to produce results (agent failure, parse error)
When continue-on-error: true (the default), these problems produce warnings and safe outputs still proceed. When continue-on-error: false, they block safe outputs entirely.
This issue helps you:
- Track workflows where threat detection raised concerns
- Review patterns of detection warnings or failures
- Identify false positives or recurring issues with threat detection
- Monitor the health of the threat detection system
[!TIP] To configure threat detection behavior, update the frontmatter:
safe-outputs: threat-detection: continue-on-error: true # Warnings only (default) # continue-on-error: false # Strict mode — block safe outputs
This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
No action to take - Do not assign to an agent.
- expires on Oct 13, 2026, 4:39 AM UTC
Source: clash-verge-rev/clash-verge-rev