Use the AI SDK's native message history in the agent

Abierto
#9,455 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@bobbai00 ya está trabajando en esto.

Desde el 16/11/2026.

  • #9494 de @bobbai00 — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
scala
Área
ai, backend

Línea de trabajo

Start by finding the service that builds the single summary message before every model call, and the point where tool calls are flattened to just a name and status. Read the referenced threads #9119, #9120, #9244 and #9259 to see what the summary currently drops, and where #9423's last-execution report and #9424's docs section would move. Done means the SDK's own message history is kept as-is with one dataflow block appended, and the rendered chat looks the same as today; compare the agent's existing chat output before and after.

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

Descripción

Task Summary

Before every model call, the service drops the message history and writes one summary message instead. Since #9244, a past tool call also shows its summary and the first line of its result, but not its other arguments or the rest of the result, and the whole summary message is written again before every call. Every new tool also needs its own section in that summary, and the system prompt spends 1.4 KB describing its format.

Keep the SDK's messages as they happen, and append one block with the current dataflow. The chat should look the same as today.

  • Run the loop as the SDK's ToolLoopAgent, and pass only the enabled tools with activeTools (what #9149 does by hand).
  • Build each step from initialMessages, responseMessages and the dataflow block. In AI SDK 7, messages returned from prepareStep carry over to later steps, so returning them would stack one block per step.
  • Drop the description of the context format from the system prompt.
  • The same message list is what the chat loads when it opens (#9482).

#9244 and #9259 fix the summary; this replaces it. #9423's report on the user's last execution moves into the dataflow block, and the docs section that #9424 adds is no longer needed.

What the model receives, today and after
Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Lenguaje dominante
Scala
Estrellas
333
Forks
202
Merge medio
3 d 11 h
PR fusionados (30 d)
185

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 apache/texera

Todos los issues de apache/texera

Issues similares

Más issues de Scala

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.