HTTP 400 missing messages[N].reasoning_content after context compaction (long sessions)

Aberta
  • Algo errado?
#1,121 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
ai-infra-agents, typescript
Domínio
ai-infra-agents, backend

Direção de pesquisa

Start by locating the harness message serializer and the compaction/history rebuild path; the issue does not name specific files or tests. Reproduce with a model that requires reasoning_content, then inspect assistant messages after compaction. Done means serialized history retains required reasoning on every assistant message, with a regression test covering compacted turns.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Summary

After a long multi-turn session with auto-compaction, sending the next message fails with HTTP 400:

Missing required parameter: 'messages[50].reasoning_content'. This model needs the reasoning of every earlier assistant message...

The turn is blocked. continue sometimes works for 1–2 turns, but the error recurs. Two trace IDs from the same session are included below.

Expected Behavior

The harness should replay reasoning_content for every earlier assistant message when the selected model requires it. If context compaction drops reasoning, the compacted history should replace old assistant turns with a summary entry that does not require reasoning, rather than leaving assistant entries without the field.

Actual Behavior

After compaction, the rebuilt request omits reasoning_content on older assistant messages. The provider rejects the whole request at messages[50]. No tool call or assistant response executes; the user must retry or start a new session.

Steps to reproduce the issue
  1. Use a model that requires reasoning_content on all assistant history.
  2. Run a long session (40+ assistant turns with tool calls).
  3. Trigger auto-compaction (or /compact).
  4. Send the next user message.
  5. Observe HTTP 400 at messages[N].reasoning_content.
Command Code Version

0.1.60 (desktop, macOS; bundled @commandcode/harness 0.1.0)

Operating System

macOS

Terminal/IDE

Command Code desktop app (macOS)

Shell

zsh

Session file (optional)

Not attached — the session contains project files. Trace IDs from the two occurrences:

  • c36659e1be4cb4330a058117255da812
  • df284ce38687a51028ea4de40acfdd48
Fix prompt (optional)

In the harness message serializer, when rebuilding history after compaction, preserve reasoning_content on every role: assistant message that originally had it. If a message is summarized away, replace it with a system/summary entry instead of an assistant entry lacking reasoning. Add a regression test: build 60 assistant turns with reasoning, compact, serialize, assert every assistant message still has reasoning_content. Include message_index, message_role, provider, and model in the 400 error payload.

Additional context

Exact error text:

Error: 400 Missing required parameter: 'messages[50].reasoning_content'. This model needs the reasoning of every earlier assistant message: send back the 'reasoning_content' returned with that message. If r...

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: c36659e1be4cb4330a058117255da812

Second occurrence in the same session:

Error: 400 Missing required parameter: 'messages[50].reasoning_content'. This model needs the reasoning of every earlier assistant message: send back the 'reasoning_content' returned with that message. If r...

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: df284ce38687a51028ea4de40acfdd48

Suspected cause: compaction/history rebuild keeps {role, content, tool_calls} but drops reasoning_content; the provider validates every assistant message, not just the last one.

Workaround: type continue, or start a new session with a summary.

Linguagem predominante
Sem dados de linguagem
Estrelas
4.2k
Forks
377
Merge médio
1d 3h
PRs com merge (30d)
6

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CommandCodeAI/command-code

Todas as issues de CommandCodeAI/command-code

Issues semelhantes

Mais issues de AI Infra & Agents

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.