openaiprovider: Chat tool continuation drops reasoning_content from the originating assistant message
Los mantenedores suelen responder en 1 día
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
- Área
- ai-infra-agents
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.
- 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": "{}"}
}]
}
- Let the automatic loop execute
lookup. Inspect themessagesarray 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
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/agent-framework-go
-
Expose session state keys on the Go todo and agent-mode providersPosiblemente ocupada @gabisonia la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
microsoft/agent-framework-go#1412 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
microsoft/agent-framework-go#1414 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
microsoft/agent-framework-go#1408 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[aw] Upgrade availableAbiertoagentic-workflows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 20/100
microsoft/agent-framework-go#1406 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 Medio día Aptitud para principiantes 28/100
microsoft/agent-framework-go#1398 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/agent-framework-go
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
keyxmakerx/Chronicle#2616 ·
Los mantenedores suelen responder en 1 día
-
go good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
hive size:simple
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nwverse/persona#12800 · 1 comentario ·
Los mantenedores suelen responder en 1 día