Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Python: Bug: Claude Opus 5.5 on Bedrock fails with "Unsupported content type" on reasoningContent blocks

Abierto
  • ¿Algo no está bien?
#14,468 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
aws, python
Área
ai, backend

Línea de trabajo

The bug is in python/semantic_kernel/connectors/ai/bedrock/services/bedrock_chat_completion.py. Look at _create_chat_message_content (line 257) and _parse_content_block_delta_event (lines 346-348). The issue is that reasoningContent blocks from Claude Opus 5.5 are not handled. Compare with the Anthropic connector (anthropic_chat_completion.py lines 267-269) which skips unsupported blocks. Write a test using the provided reproduction script to verify the fix skips reasoningContent and returns the subsequent text or toolUse blocks.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

python triage

Thanks to the Python team for the Bedrock connector (#9100) and for dropping the model info check in #12395. Because of that, the Claude Opus 5.5 profile IDs load with no code change.

Describe the bug

With no thinking settings, Claude Opus 5.5 on Bedrock sends a reasoningContent block before the text or toolUse blocks whenever the model decides to think, and BedrockChatCompletion fails on it. This depends on the prompt (raw converse: "Weather in Paris? brief" 5/5, "Hello" 0/5), so a trivial prompt usually works. Opus 5 fails the same way (there even "Hello" had the block 3/3).

case (main ca40aa7, live us-east-1) result
us.anthropic.claude-opus-5-5, "Weather in Paris? brief", non-streaming ❌ 0/5 ServiceInvalidResponseError: Unsupported content type in the response: {'reasoningContent': ...}
same, streaming ❌ 0/5 KeyError: 'toolUse'
global.anthropic.claude-opus-5-5, both modes ❌ 0/3 each, same errors
us.anthropic.claude-opus-5, both modes ❌ 0/3 each, same errors
Opus 5.5, FunctionChoiceBehavior.Auto, model thinks before calling tools ❌ 2/2 ServiceInvalidResponseError (auto_invoke False and True)
Opus 5.5, auto-invoke, model thinks on the turn after the tool result ❌ 3/3 ServiceInvalidResponseError
Opus 5.5, "Hello" ✅ 3/3 (no reasoning block)
Claude Haiku 4.5, Nova Lite ✅ text returned

Cause, in python/semantic_kernel/connectors/ai/bedrock/services/bedrock_chat_completion.py:

  • _create_chat_message_content handles text, image and toolUse, and raises for anything else (L257).
  • _parse_content_block_delta_event treats every delta without text as toolUse (L346-348). The reasoning delta is {"reasoningContent": {"text": ""}}, so it fails with a KeyError.

To Reproduce

# AWS_DEFAULT_REGION=us-east-1 python repro.py
import asyncio

from semantic_kernel.connectors.ai.bedrock import BedrockChatCompletion, BedrockChatPromptExecutionSettings
from semantic_kernel.contents import ChatHistory


async def main():
    svc = BedrockChatCompletion(model_id="us.anthropic.claude-opus-5-5")
    history = ChatHistory()
    history.add_user_message("Weather in Paris? brief")
    print(await svc.get_chat_message_content(history, BedrockChatPromptExecutionSettings(max_tokens=300)))


asyncio.run(main())

semantic_kernel.exceptions.service_exceptions.ServiceInvalidResponseError: Unsupported content type in the response: {'reasoningContent': {'reasoningText': {'text': '', 'signature': 'CA...'}}}

Failed 3/3 runs; raw converse returns ['reasoningContent', 'text'].

Tool-call rows: prompts and output

One get_weather(city) kernel function, FunctionChoiceBehavior.Auto, max_tokens=1000:

prompt A: "I am deciding between Paris, Lyon and Nice for a picnic tomorrow; think about which cities matter, check the weather where needed, and recommend one."
prompt B: "Think about whether tomorrow suits a picnic in Paris: check the weather with the tool, then recommend yes or no."

A Auto(auto_invoke=False) runs 1-2: ServiceInvalidResponseError: Unsupported content type in the response: {'reasoningContent': ...
A Auto(auto_invoke=True)  runs 1-2: ServiceInvalidResponseError: Unsupported content type in the response: {'reasoningContent': ...
B Auto()                  runs 1-3: ServiceInvalidResponseError: Unsupported content type in the response: {'reasoningContent': ...

Expected behavior

The text reply or the tool calls come back. The connector doesn't surface reasoning today, so skipping these blocks would be enough, as the Anthropic connector does (it reads only TextBlock and tool-use blocks, anthropic_chat_completion.py L267-269). Locally that makes the ❌ rows pass, except that auto-invoke with parallel tool calls then hits the separate #14073. I have a small patch with unit tests and can open a PR.

Platform

  • Language: Python
  • Source: main branch (ca40aa7, 1.44.1)
  • AI model: Bedrock us.anthropic.claude-opus-5-5, global.anthropic.claude-opus-5-5, us.anthropic.claude-opus-5
  • IDE: none (script)
  • OS: macOS

Additional context

Lenguaje dominante
C#
Estrellas
28.6k
Forks
4.8k
Merge medio
13 h 24 min
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/semantic-kernel

Todos los issues de microsoft/semantic-kernel

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.