Repository navigation
Conversation
/v1/responses goes through stream.js → openai-responses translator. Map state.usage to Responses API shape in sendCompleted so Codex Desktop can parse response.completed.response.usage.
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
1 participant
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
Codex Desktop reads
response.completed.response.usageto show the context window usage indicator. When/v1/responsesroutes through a chat-completions upstream (e.g. MiniMax), theopenai-responsestranslator synthesizedresponse.completedwithout ausagefield, and even after adding usage it emitted Chat Completions field names (prompt_tokens) that Codex cannot parse (missing field input_tokens).This PR maps upstream usage to the Responses API shape in
sendCompleted.Changes
toResponsesUsage()inopen-sse/translator/concerns/usage.js— convertsprompt_tokens/completion_tokens→input_tokens/output_tokens, preservescached_tokensininput_tokens_detailsresponse.completedinopenai-responses.jssendCompletedRuntime path
/v1/responses→handleChat→handleChatCore→stream.js(extractUsage) →openai-responsestranslator (sendCompleted). Does not go throughresponsesTransformer.js(handleResponsesCoreis unused).Test plan
npm run build && npm run start— Codex Desktop shows context usageresponse.completedcarriesinput_tokens/output_tokens(no parse error)