fix(langchain): handle missing response token details - #462
Open
annzhang-db wants to merge 2 commits into
Open
Conversation
Signed-off-by: Ann Zhang <105813440+annzhang-db@users.noreply.github.com>
smurching
marked this pull request as ready for review
August 24, 2026 23:24
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.
Fixes #461.
Responses API providers can omit input and output token-detail objects. Build LangChain usage metadata from the required token counts and only attach detail dictionaries when present, avoiding
AIMessageandAIMessageChunkvalidation failures.How do you know it works?
Regression coverage exercises direct conversion, normal Responses invocation, and streamed usage chunks both with and without detail objects. The complete chat-model unit module passes (108 passed, 2 skipped), along with Ruff formatting/lint and
ty check.