/report command allows you to report bugs, issues, or problems you encounter while using ScryCLI.
Usage
How It Works
What to Include in Your Report
When reporting a bug, include:- Description: What happened and what you expected
- Steps to reproduce: How to trigger the bug
- Environment: Your OS, ScryCLI version, etc.
- Error messages: Any error text or screenshots
- Context: What you were trying to do when the bug occurred
Navigation
- Enter: Open the bug report form
- Esc: Cancel and return to chat
Example Flow
The report form opens in your default web browser. Make sure you have a browser configured and can access the internet.
Common Issues to Report
- Application crashes or freezes
- Unexpected error messages
- Commands not working as documented
- Performance problems
- Incorrect AI responses or behavior
- Installation or setup issues
- Documentation errors or unclear instructions
Privacy
When you use/report, only your web browser is opened. No automatic data collection or telemetry is sent. You control what information to share in the report form.
Response Time
The ScryCLI team reviews bug reports regularly. While response times vary, you can expect:- Acknowledgment of critical bugs: Within 24-48 hours
- Updates on bug fixes: As patches are developed
- General reports: Response within a few days
Alternative Reporting Methods
Besides/report, you can also:
- Check the GitHub repository for known issues
- Contact support through official channels
- Join the community discussion forums
