[ENHANCEMENT] Global enhanced logging to VS Code Output + warning banner #8098
Description
Type
Enhancement
Problem / Value
Across Roo Code, failures often surface as generic errors with little detail. Users can’t see what went wrong, which slows troubleshooting and blocks workflows.
Context
Affects anyone configuring or using Roo Code features where external calls or actions may fail (for example: adding/refreshing models, connecting services, running background operations). Users need a clear, local way to view what happened.
Proposed Improvement
Add a global “Enhanced logging” toggle on the Settings → Info tab (avoiding the term “debug mode” to prevent confusion with the Debug Mode feature). When enabled:
- Write detailed failure logs to the VS Code Output panel (local only) under Roo Code’s output channel.
- For failed attempts, include: endpoint/method, timing, status code, and the provider/service error message/body where applicable.
- Do not embed logs in the app UI; optionally show a small “View in Output” link near failure messages that focuses the Output panel.
- Display a yellow indicator banner while this setting is enabled, matching the visual style of the existing “footgun/custom prompt” warning bar, so the state is clearly visible.
- Designed as a general mechanism we can extend to additional areas over time.
Behavior
- Off by default; existing UX unchanged when disabled.
- Logs remain local; nothing is auto-uploaded or shared.
Impact
- Enables self-serve troubleshooting and fewer support loops
- Unblocks integrations and tasks by exposing root causes
- Reduces frustration and time spent guessing