Diagnostics
Generate diagnostic bundles for troubleshooting or when contacting support.
Generate a diagnostic bundle
hooklistener diagnostics --output ./debug-bundle
| Flag | Short | Default | Description |
|---|---|---|---|
--output | -o | . (current directory) | Output directory for the bundle |
Bundle contents
The diagnostic bundle is created as a directory named hooklistener-diagnostics-YYYYMMDD-HHMMSS/ containing:
| File | Contents |
|---|---|
logs/ | Recent log files (JSON format) |
config.json | Sanitized config (tokens are redacted) |
system_info.json | Session ID, timestamp, CLI version, OS, architecture |
Clean up log files
Remove old log files to free disk space:
hooklistener clean-logs --keep 5
| Flag | Short | Default | Description |
|---|---|---|---|
--keep | -k | 10 | Number of recent log files to keep |
The command keeps the most recent log files (by modification time) and deletes older ones. Only files matching the pattern hooklistener-*.log are affected.
Log file location
Log files are stored in ~/.config/hooklistener/logs/ and use the naming format hooklistener-YYYYMMDD-HHMMSS.log.
When to use diagnostics
- Reporting bugs — attach the diagnostic bundle to GitHub issues
- Contacting support — provide context about your environment
- Self-debugging — review logs for connection issues or errors