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

Aperta
#1,409 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@nicksin-leroux ci sta già lavorando.

Dal 20/11/2026.

  • #1410 di @nicksin-leroux — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
74/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
683
Fork
70
Merge medio
17h 50m
PR unite (30g)
64

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/agent-framework-go

Tutte le issue di microsoft/agent-framework-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.