fix: preserve API error response bodies - #38
Merged
Conversation
josuesilva-doit
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Follow-up to Alfredo review comment on #32. Agent mode previously suppressed the complete API error body, so payloads such as structured validation errors could become an unrecoverable generic HTTP status message.
Test methods
go test ./...Could this break things?
Risk: medium, intentional output correction. Agent-mode failures will now retain the API error body on stdout while the stable envelope remains on stderr. Exit codes and human-mode behavior are unchanged. Consumers that explicitly assumed stdout was empty on failures will now see the detailed response.
Jira
CMP-48643