// reference
Troubleshooting
Common issues with GitHub Apps, pull request scans, reports, findings, and CLA checks.
GitHub and repositories
Repositories missing after install
- Confirm the correct app is installed on the right GitHub org or user:
Superagent Security for scans and repository reports, or
Open CLA for CLA. - Re-select repository access in the GitHub App settings.
- Open Integrations and verify connection status.
- Refresh Repository: repos only appear after the app can access them.
No pull request checks
- Ensure Superagent Security has pull request and contents permissions.
- Open or update a PR on a connected repo to trigger webhooks.
- Check the repository detail page after a few minutes for check activity.
CLA
Check fails for a signed contributor
- Verify the signature matches the current template version hash on that repository.
- For org contributions, confirm the corporate CLA exists and Open CLA has org membership read permission.
"Repository not seen by CLA app"
- Open or update a pull request on the repository first.
- Confirm Open CLA is installed on that repo and a template is assigned on the repository detail page.
Reports
Repository report not starting
- Confirm Superagent Security is installed on the target repo with contents access.
- For private repos, verify the repo appears under Repository with the Security capability badge.
Web app report not starting
- Check that the target URL is public HTTP or HTTPS; localhost and private addresses are rejected.
- If your WAF blocks the scanner, allowlist the static egress IP shown on the New report page when one is configured.
Report missing from the list
- Open Red team and search by name. Reports from all target types share one list.
Findings
No findings after a report
- Not every report produces findings immediately; check report status on the detail page.
- GitHub advisories require advisory webhook permissions on Superagent Security.
MCP server
Connection problems with Cursor, Claude Code, or Codex CLI usually come down to the URL (https://www.superagent.sh/mcp, not the bare domain) or the API key. The MCP server guide has a full symptom table.
Getting help
- Review the relevant feature doc
- Use Support in the sidebar footer when available