You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reporting-errors.md
-20Lines changed: 0 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,23 +58,3 @@ After copying error information:
58
58
-**GitHub Issues**: File at [github.com/RooCodeInc/Roo-Code/issues](https://github.com/RooCodeInc/Roo-Code/issues)
59
59
60
60
Include a brief description of what you were trying to do when the error occurred. The exported diagnostics handle the technical details.
61
-
62
-
---
63
-
64
-
## What You Can't Do
65
-
66
-
Error exports don't include your actual code or file contents—only metadata about the task. If the support team needs to see specific code that triggered the error, you'll need to share that separately.
67
-
68
-
---
69
-
70
-
## When to Use Each Option
71
-
72
-
| Scenario | Use This |
73
-
|----------|----------|
74
-
| Quick question in Discord |**Copy basic error info**|
75
-
| Filing a GitHub issue |**Get detailed error info**|
76
-
| Support email for recurring error |**Get detailed error info**|
77
-
| Asking about a specific error message |**Copy basic error info**|
78
-
| Error that only happens in certain conditions |**Get detailed error info**|
79
-
80
-
The detailed report's task history helps the team understand the sequence of events leading to the error—invaluable for intermittent or complex issues.
0 commit comments