Roo-Code/apps/docs/docs/reporting-errors.md
Bruno Bergher e921f9d21e
Some checks failed
Code QA Roo Code / check-translations (push) Has been cancelled
Code QA Roo Code / knip (push) Has been cancelled
Code QA Roo Code / compile (push) Has been cancelled
Code QA Roo Code / platform-unit-test (ubuntu-latest) (push) Has been cancelled
Code QA Roo Code / platform-unit-test (windows-latest) (push) Has been cancelled
CodeQL Advanced / Analyze (javascript-typescript) (push) Has been cancelled
Deploy docs to GitHub Pages / build (push) Has been cancelled
Nightly Publish / publish-nightly (push) Has been cancelled
Deploy roocode.com / check-secrets (push) Has been cancelled
Deploy docs to GitHub Pages / deploy (push) Has been cancelled
Deploy roocode.com / deploy (push) Has been cancelled
Remove contributor and community references (#12347)
* Remove contributor and community references

* shutdown notice

* Allow empty web app test suite
2026-05-12 16:33:09 +01:00

2.1 KiB

description keywords
Learn how to report errors in Roo Code by accessing error details, copying diagnostic information, and sharing it with the support team.
error reporting
error details
troubleshooting
support
bug report
diagnostics

Reporting Errors

When Roo Code encounters an error, you can export detailed diagnostic information to share with the support team. This helps resolve issues faster by providing complete context about what went wrong.


Accessing Error Details

When an error appears, click the "Details" link next to the error message. This opens a modal with diagnostic information and export options.

Click Details link on error message to access diagnostic options

The Details link reveals two export options for sharing error information with support.


Choosing the Right Export Option

The Error Details modal offers two buttons, each serving different needs:

  1. Copy basic error info - Copies essential error details to your clipboard:

    • Timestamp and extension version
    • Provider and model being used
    • The specific error message

    Use when: You want to quickly share the error in a brief support email.

  2. Get detailed error info - Opens a full diagnostic report with:

    • Everything from basic info
    • Complete task history showing all messages and actions
    • Full configuration and environment details
    • Provider-specific settings

    Use when: The support team needs to reproduce the issue or you're filing a GitHub issue.

Error Details modal with Copy basic error info and Get detailed error info buttons

Sharing with Support

After copying error information:

Include a brief description of what you were trying to do when the error occurred. The exported diagnostics handle the technical details.