Prepare the report
- Open the account menu’s report-issue action, or the issue action associated with the affected session when offered.
- Sign in to Rudr to submit the report. Local diagnostic export does not require Rudr sign-in.
- Choose Issue type and Severity.
- Complete What went wrong? with the expected and actual result. Add Steps to reproduce when you can describe them.
- Use Attach screenshot or paste an image only after removing private content. Review attached thumbnails and use their remove control for unwanted images.
A useful setup report distinguishes a missing CLI from failed sign-in or unavailable model. A continuation report names source/destination harnesses and whether the source was idle. Include Rudr and provider versions without pasting secrets.
Review diagnostic consent
Read Redacted diagnostic snapshot and the listed scope. The report includes diagnostic metadata, recent error states, model/harness identifiers, app/platform versions, and the screenshots you attach. Session-specific reporting can attach a filtered session snapshot.
The automatic snapshot is designed to exclude credentials, environment variables, source files, and personal machine paths. Your typed description and screenshots still need your review; automatic filtering is not a reason to paste keys or private transcripts.
Check the consent stating that you agree to send the diagnostic report and attachments, then use the submit action only when you are ready. The report goes to Rudr’s reporting backend; this is not merely a local export.
Check the result
Wait for success or an explicit error before resubmitting. No support response time is promised by this guide. If submission fails, preserve your description and sanitized error. Use Export diagnostics when you only need a local file.
No report or account change was performed to verify this documentation draft.
Rudr account requirements
Rudr supports guest use. See what requires Rudr sign-in for the cloud account features that are unavailable while signed out, and how they differ from AI-provider credentials.