Troubleshooting
Collect a safe support report
Give Support enough context to investigate without sharing credentials or private work.
Include:
- The Agent Approve app version
- Your operating system versions
- The coding agent and its version
- The setup mode shown by
npx agentapprove status - The time of the failed test and your time zone
- The step that failed and the result you expected
- A short redacted error message, if one appeared
Remove:
- API tokens, pairing codes, encryption keys, and authorization values
- Full device, account, or organization identifiers
- Private repository paths and machine names
- Commands, prompts, file contents, or output that contain customer or company data
- Raw logs unless Support asks for a specific redacted section
The hook debug log can contain raw commands, prompts, paths, and tool input even when end-to-end encryption is enabled for network delivery. Never attach the complete file. Follow Trace a request with the hook debug log and include only the smallest redacted section around one test.
Use invented names such as builder and my-mac when you need to describe profiles or devices.
Open Support to use the public issue tracker for a reproducible problem or email Support when the details are sensitive.