Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Claude model throws UnsupportedOperationException("Not supported yet.") on thinking blocks from Claude 5 models

Ouverte
  • Quelque chose ne va pas ?
#1,630 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@hemasekhar-p y travaille déjà.

Depuis le 8/10/2026.

  • #1634 par @innoprej — ouverte

Évaluation

Cette issue n'a pas encore été évaluée.

Description

needs review

🔴 Required Information

Describe the Bug:

Claude.anthropicContentBlockToPart converts only text and tool_use response blocks and throws for every other block type (Claude.java:374-391):

throw new UnsupportedOperationException("Not supported yet.");

So any Messages API response that contains a thinking or redacted_thinking block makes Claude.generateContent throw, and the agent run ends with that exception. ADK Java never sets thinking on the request (Claude.java:142-147). According to Anthropic's thinking docs (checked 2026-10-08), the Claude 5 models (Opus 5 and 5.5, Sonnet 5 and 5.5, Haiku 5.5, Fable 5 and 5.1, and the Mythos models) use adaptive thinking when that field is absent, and their display default is "omitted". Whenever the model decides to think, the response therefore contains a thinking block with empty text and a signature, at the start of the response or right before a tool_use block. Opus 4.8 and earlier, Sonnet 4.6 and earlier, and Haiku 4.5 do not think unless asked, which is probably why this has not come up before.

Skipping these blocks would stop the exception, and the API accepts a history without them, but the same docs mark passing them back, complete and unmodified, as required within a tool-use turn; without them the model loses its earlier reasoning. The request side has the matching gap: partToAnthropicMessageBlock (Claude.java:176-209) sends a thought Part that has text as an ordinary text block, dropping the signature, and throws the same exception for a thought Part that has only a signature.

Steps to Reproduce:

  1. Use com.google.adk:google-adk 1.11.0 (or main at ce882374) with anthropic-java 2.15.0, the version ADK depends on.
  2. Give a Claude model an AnthropicClient whose response has a thinking block followed by a text block (code below, with a mocked client).
  3. Call generateContent, or run an LlmAgent that uses this model through InMemoryRunner.

Expected Behavior:

thinking and redacted_thinking blocks become thought Parts that keep the block's signature (or the redacted block's data) in thoughtSignature, and the next request sends them back as the same blocks. adk-python has used this mapping since google/adk-python@16952bd39 (src/google/adk/models/anthropic_llm.py), with one difference noted under Additional Context.

Observed Behavior:

java.lang.UnsupportedOperationException: Not supported yet.
	at com.google.adk.models.Claude.anthropicContentBlockToPart(Claude.java:391)
	at com.google.adk.models.Claude.convertAnthropicResponseToLlmResponse(Claude.java:354)
	at com.google.adk.models.Claude.generateContent(Claude.java:158)

The same happens with a summarized thinking block (non-empty text) and with a redacted_thinking block. In an agent run, the Flowable returned by InMemoryRunner.runAsync terminates with this exception on the first model response that contains a thinking block. On the request side, which I tested by putting thought Parts in the history by hand (Claude cannot produce one today), a thought Part with text goes out as a text block (an omitted thought as an empty text block, a summarized one as visible text), and one with only a signature throws the same exception at Claude.java:209.

Environment Details:

  • ADK Library Version (see maven dependency): 1.11.0 and main at ce882374, with anthropic-java 2.15.0
  • OS: Windows 11 (not OS-specific)
  • TS Version (tsc --version): N/A (Java: Microsoft OpenJDK 17.0.19)

Model Information:

  • Which model is being used: claude-opus-5-5 as the model name in a mocked reproduction. The mocked AnthropicClient returns the documented block shape; I did not run it against the live API. Whether a response contains a thinking block is up to the model; per the docs, the models above can return one without being asked.

🟡 Optional Information

Regression:

No. Both conversion methods have thrown for these blocks since Claude was added in 0.1.0; it shows up now because the Claude 5 models think when thinking is not set.

Additional Context:

  • I have a draft fix in Claude.java (+23 lines) that uses the same mapping as google/adk-python@16952bd39: a thinking block becomes Part(text, thought=true, thoughtSignature=signature), a redacted_thinking block becomes Part(thought=true, thoughtSignature=data), and requests convert them back. With the draft, the code below returns a thought Part and a text Part, and in a tool-use turn the second request sends [thinking (same signature), tool_use]. I'll link the PR here.
  • One difference from adk-python: its request side sends a thought with empty text (what display: "omitted" returns) back as redacted_thinking with the signature as data, not as the thinking block the API returned. The draft checks whether the text is present rather than non-empty.
  • One question before the PR: if the history also holds thought Parts produced by another model (for example when the same agent ran on Gemini earlier in the session; other agents' thoughts are already skipped in Contents), should Claude drop them, or keep sending the ones with text as plain text, as it does today? Sending them as thinking blocks would fail, because Anthropic rejects signatures it cannot decode.
  • Related, not duplicates: #1221 (streaming support for Claude, open) changes the same file and drops thinking deltas in the streaming path; #1616 is about the Spring AI bridge dropping reasoning content.

Minimal Reproduction Code:

// The mocked client returns what the Messages API returns when the model thinks with
// display "omitted": an empty thinking block with a signature, then the answer.
AnthropicClient client = mock(AnthropicClient.class);
MessageService messages = mock(MessageService.class);
Message response = mock(Message.class);
when(client.messages()).thenReturn(messages);
when(messages.create(any(MessageCreateParams.class))).thenReturn(response);
when(response.content())
    .thenReturn(
        List.of(
            ContentBlock.ofThinking(
                ThinkingBlock.builder().thinking("").signature("EqQBCkYIBxgC...").build()),
            ContentBlock.ofText(TextBlock.builder().text("4").citations(List.of()).build())));

Claude claude = new Claude("claude-opus-5-5", client);
LlmRequest request =
    LlmRequest.builder()
        .contents(List.of(Content.builder().role("user").parts(Part.fromText("2+2?")).build()))
        .build();

claude.generateContent(request, false);
// throws java.lang.UnsupportedOperationException: Not supported yet.

(AnthropicClient, MessageService (com.anthropic.services.blocking) and the com.anthropic.models.messages types are from anthropic-java 2.15.0; Content and Part are com.google.genai.types. mock, when and any are Mockito 5, whose default inline mock maker is needed because Message is final.)

How often has this issue occurred?:

  • Always (100%) for a response that contains a thinking or redacted_thinking block.
Langage dominant
Java
Étoiles
1.8k
Forks
446
Merge moyen
4 j 19 h
PR mergées (30 j)
60

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de google/adk-java

Toutes les issues de google/adk-java

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.