Fix: Properly populate AssistantMessage error field#506
Merged
ashwin-ant merged 1 commit intoanthropics:mainfrom Feb 3, 2026
Merged
Conversation
ashwin-ant
approved these changes
Jan 28, 2026
Contributor
Author
|
Bump: Users still can't use the error field to programmatically handle error responses. This surfaced again as a result of the outages this morning |
Collaborator
|
Sorry, didn't click merge 😳 |
Contributor
Author
Np, appreciate it! |
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
Fixes #505
AssistantMessage.errorfield not being populated due to incorrect data patherrorfield is at the top level of the response (data["error"]), not nested insidedata["message"]["error"]Test plan
python -m pytest tests/test_message_parser.pyto verify all tests pass🤖 Generated with Claude Code