Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#1,616 コメント 1 件 リアクション 0 件 担当者 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日 2時間
マージ済み PR（30日）
46

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

google/adk-java のほかの issue

google/adk-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。