What version of Kimi Code is running?
VS Code extension 0.7.0
Which open platform/subscription were you using?
OpenAI Responses-compatible third-party endpoint
Which model were you using?
Qwen served by vLLM
What platform is your computer?
Windows x64
What issue are you seeing?
When using Kimi Code VS Code extension 0.7.0 with a vLLM-served Qwen model through an OpenAI Responses-compatible endpoint, the final assistant answer renders, but raw reasoning does not.
GPT reasoning summaries render correctly because the adapter handles response.reasoning_summary_text.delta / response.reasoning_summary_text.done. However, the OpenAI Responses standard raw-reasoning events response.reasoning_text.delta / response.reasoning_text.done are ignored, so no thinking (think) content reaches the UI.
Actual behavior: GPT summary reasoning is visible; vLLM/Qwen raw reasoning is not displayed.
Root cause: the Responses event adapter appears to branch only on the reasoning_summary_text event pair and has no equivalent mapping for the reasoning_text pair.
What steps can reproduce the bug?
- Use VS Code extension 0.7.0 with a Qwen model served by vLLM through an OpenAI Responses-compatible endpoint.
-
- Send a prompt that produces raw reasoning.
-
- Have the endpoint stream this representative minimal event sequence:
data: {"type":"response.reasoning_text.delta","item_id":"rs_1","output_index":0,"content_index":0,"delta":"We need to inspect the request."}
data: {"type":"response.reasoning_text.done","item_id":"rs_1","output_index":0,"content_index":0,"text":"We need to inspect the request."}
- Observe that the final answer renders, but the reasoning text never appears.
For comparison, replacing those event types with response.reasoning_summary_text.delta / response.reasoning_summary_text.done allows GPT-style reasoning summaries to display.
What is the expected behavior?
response.reasoning_text.delta should be mapped to the same internal think stream used for reasoning summaries. response.reasoning_text.done should correctly finalize/close that thinking block without dropping or duplicating content.
Both GPT summary reasoning and vLLM/Qwen raw reasoning should therefore render in the VS Code UI.
Additional information
Suggested fix: add explicit handling for response.reasoning_text.delta and response.reasoning_text.done alongside the existing reasoning_summary_text handlers, with tests covering incremental mapping to think and correct completion of the thinking stream.
Contribution
What version of Kimi Code is running?
VS Code extension 0.7.0
Which open platform/subscription were you using?
OpenAI Responses-compatible third-party endpoint
Which model were you using?
Qwen served by vLLM
What platform is your computer?
Windows x64
What issue are you seeing?
When using Kimi Code VS Code extension 0.7.0 with a vLLM-served Qwen model through an OpenAI Responses-compatible endpoint, the final assistant answer renders, but raw reasoning does not.
GPT reasoning summaries render correctly because the adapter handles
response.reasoning_summary_text.delta/response.reasoning_summary_text.done. However, the OpenAI Responses standard raw-reasoning eventsresponse.reasoning_text.delta/response.reasoning_text.doneare ignored, so no thinking (think) content reaches the UI.Actual behavior: GPT summary reasoning is visible; vLLM/Qwen raw reasoning is not displayed.
Root cause: the Responses event adapter appears to branch only on the
reasoning_summary_textevent pair and has no equivalent mapping for thereasoning_textpair.What steps can reproduce the bug?
For comparison, replacing those event types with
response.reasoning_summary_text.delta/response.reasoning_summary_text.doneallows GPT-style reasoning summaries to display.What is the expected behavior?
response.reasoning_text.deltashould be mapped to the same internalthinkstream used for reasoning summaries.response.reasoning_text.doneshould correctly finalize/close that thinking block without dropping or duplicating content.Both GPT summary reasoning and vLLM/Qwen raw reasoning should therefore render in the VS Code UI.
Additional information
Suggested fix: add explicit handling for
response.reasoning_text.deltaandresponse.reasoning_text.donealongside the existingreasoning_summary_texthandlers, with tests covering incremental mapping tothinkand correct completion of the thinking stream.Contribution