[Enhancement] Improve API Failure Message Handling & Display #6139
Description
What specific problem does this solve?
Currently, when an API request fails a short message is returned in the chat feed but as best I can tell, there is literally no way to see the actual contents. If that error is generic or not tied to a specific code that might help identify it, you're essentially left with nothing.
When an API request is made, you can easily view the contents of the call by clicking to expand it. However, if that request fails, all you get back is a minimal line with no additional information. We must be able to expose the full text if a user desires.
This will make it infinitely easier to debug problems with API providers.
Additional context (optional)
I can view the initial API request in long form, just not the response payload:
Related issues (or places where this feature would have allowed self-solve of their issue)
#2045
#442
#5989
Was also a thread on reddit about this the other day
Roo Code Task Links (Optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear impact and context
Interested in implementing this?
- Yes, I'd like to help implement this feature
Implementation requirements
- I understand this needs approval before implementation begins
How should this be solved? (REQUIRED if contributing, optional otherwise)
Following the current implementation patterns, we'll implement this in the same way as you can currently expand the contents of an outgoing API request in the chat feed (code block)
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
API errors are clickable to expand
Technical considerations (REQUIRED if contributing, optional otherwise)
Want to also resolve the bug where API errors disappear prematurely. There's clearly a race condition that popped up a bunch of times while I was staging API errors to recreate this. Video attached.
error_then_gone.mp4
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
Risks: very difficult to actually figure out what's wrong if we don't fix this.