openaiprovider: Chat tool continuation drops reasoning_content from the originating assistant message

Abierto
#1,409 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@nicksin-leroux ya está trabajando en esto.

Desde el 20/11/2026.

  • #1410 de @nicksin-leroux — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
74/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start in the Go Chat Completions provider path used by openaiprovider.NewChatCompletionsAgent and trace how the assistant response is added to the automatic tool loop. Add a regression test with the fake HTTP transport and local lookup tool described in the issue. Done means the immediate follow-up includes the supplied reasoning_content, omits it when absent, and does not carry it into unrelated later turns.

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

Descripción

Problem

When a Chat Completions endpoint returns reasoning_content alongside a tool call, the Go Chat provider omits that field from the assistant message on the next request. The tool runs and its result is paired with the correct call. However, an endpoint that requires the original field can reject the follow-up instead of completing the answer. We’ve observed this requirement with Kimi.

Reproduced on both v0.3.1 and main at 045c7be52783e6ae383c816cf9c64310f8d25240, using openaiprovider.NewChatCompletionsAgent and the standard automatic tool loop with streaming disabled.

How to reproduce

Use a fake HTTP transport and one local lookup tool. No API key or live endpoint is needed.

  1. Have the transport return a completion with finish_reason: "tool_calls" and this assistant message:
{
  "role": "assistant",
  "content": "I'll look that up.",
  "reasoning_content": "synthetic-marker",
  "tool_calls": [{
    "id": "call_1",
    "type": "function",
    "function": {"name": "lookup", "arguments": "{}"}
  }]
}
  1. Let the automatic loop execute lookup. Inspect the messages array in the next HTTP request.

Actual: The assistant message still contains call_1, and the tool result references call_1, but reasoning_content is missing.

Expected: For endpoints that require it, the assistant message containing call_1 should retain the exact value "synthetic-marker" on that immediate follow-up. If the endpoint didn’t supply the field, it should remain absent. The value shouldn’t appear in visible output, logs or unrelated later turns.

Related work and proposed contribution

PR #630 preserves reasoning that has already reached the automatic tool loop. This case occurs one step earlier: the Chat provider doesn’t carry the endpoint’s reasoning_content field into that loop.

We’ll open a PR linked to this issue with a proposed fix and a regression test. The test will check that reasoning_content is returned with the matching tool result when supplied, stays absent when omitted, and isn’t carried into unrelated later turns.

Lenguaje dominante
Go
Estrellas
683
Forks
70
Merge medio
17 h 50 min
PR fusionados (30 d)
64

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/agent-framework-go

Todos los issues de microsoft/agent-framework-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.