Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Client tools never execute against spec-compliant AG-UI servers (plain `success` RUN_FINISHED)

Cerrado
  • ¿Algo no está bien?
#1,464 0 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@jherr ya está trabajando en esto.

Desde el 23/9/2026.

  • #1543 de @ArVaViT — fusionado

Evaluación

Este issue todavía no se ha evaluado.

Descripción

has-pr waiting-on: maintainer
TanStack AI version

0.54

Framework/Library version

React 19

Describe the bug and the steps to reproduce it
What happens

When useChat is connected to a third-party AG-UI server (Pydantic AI's AGUIAdapter in my case), the model calls a registered .client() tool, the tool call is rendered, and then the run just ends. The .client() handler is never invoked and no continuation run is started.

The server emits the canonical AG-UI sequence for a frontend tool:

TOOL_CALL_START  { toolCallId: "tooluse_…", toolCallName: "ping" }
TOOL_CALL_ARGS   { delta: "" }
TOOL_CALL_END
RUN_FINISHED     { outcome: { type: "success" } }
Why

Client-tool execution is only triggered from StreamProcessor.handleInterrupts (activities/chat/stream/processor.ts), i.e. when RUN_FINISHED carries outcome.type: "interrupt" with a metadata.kind: "client_tool" interrupt. That's the shape TanStack's own chat() emits, but it isn't what AG-UI specifies.

Per ag-ui-protocol/ag-ui#2731, a frontend tool call ends the run with a plain success outcome. It may include pendingToolCallIds; otherwise the client derives the unanswered calls from the stream. The client then executes the tools and continues with role: "tool" messages in the next run's history. There is no success-outcome path that calls onToolCall, so nothing fires.

Expected

On a success RUN_FINISHED, the client should dispatch onToolCall for tool calls that were started but not answered by TOOL_CALL_RESULT, using outcome.pendingToolCallIds when present. The rest of the pipeline already exists (pendingToolExecutions, addToolResultForClientTool, continuation). The interrupt path would stay unchanged.

Repro
  1. Pydantic AI agent exposed via AGUIAdapter, no server-side ping tool.
  2. useChat({ connection: fetchServerSentEvents(url), tools: [pingDef.client(() => 'pong')] })
  3. Ask the agent to call ping and report the result → handler never runs, conversation stops.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

_

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

None

Terms & Code of Conduct
  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Lenguaje dominante
TypeScript
Estrellas
3.2k
Forks
361
Merge medio
1 d 8 h
PR fusionados (30 d)
266

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 TanStack/ai

Todos los issues de TanStack/ai

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.