Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[spring-ai] Bridge drops reasoning_content (thinking) — surface it as partial events and/or persist it

未關閉
  • 哪裡不對？
#1,616 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@hemasekhar-p 已經在處理了。

開始於 2026年10月5日。

評估

這個 Issue 還沒有評估資料。

描述

needs review
Is your feature request related to a problem? Please describe.

Spring AI 2.0 already exposes reasoning content from thinking models such as DeepSeek-R1, Qwen-Thinking, and GLM via AssistantMessage metadata (reasoningContent). However, in the Spring AI bridge used by ADK, this field is not read or forwarded.

After decompiling 1.11.0, I confirmed the four core bridge classes — SpringAI, MessageConverter, StreamingResponseAggregator, and ConfigMapper — don't reference reasoningContent at all. The result is that reasoning is silently dropped: it is neither forwarded as partial events nor persisted to the session, and there is no warning. Users running thinking models through the bridge lose the entire reasoning stream.

Describe the solution you'd like

During streaming aggregation, the bridge should read reasoningContent and surface it to ADK consumers. For example:

  • emit it as dedicated reasoning parts on partial LlmResponses, persisted together with the final event; or
  • map it onto the thought flag if the Java SDK's Part supports it, similar to the Gemini path.

This would make thinking models actually usable through the bridge: UIs could render collapsible thinking panels, and session history would retain the reasoning trace for audit.

We already handle this in a production fork via a lightweight marker protocol around the reasoning text, with the frontend rendering collapsible thinking panels and per-segment timing. Happy to share the implementation or send a PR.

One thing the bridge would also need to normalize: OpenAI-compatible gateways differ in reasoning chunk semantics — some stream pure deltas, others return cumulative text per chunk. Consumers currently need prefix-detection heuristics to avoid duplication; if the bridge normalized to pure deltas once, all downstream code stays simple.

Describe alternatives you've considered

Keeping the status quo forces anyone using thinking models through the bridge to either fork it or lose reasoning entirely.

Additional context

Verified against 1.11.0 (current latest at the time of writing). No Spring AI changes are needed — the metadata is already there, waiting for the bridge to read it.

主要語言
Java
星號
1.7k
分支
431
平均合併
3 天 11 小時
30 天內合併 PR
50

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

google/adk-java 的其他 Issue

查看 google/adk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。