Antigravity: "Running view_file" never gets a completed status mid-turn, so the UI shows it hanging for minutes and the trail log records fake durations

Abierto
#22 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #31 de @warhammered — cerrado sin fusionar

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, testing

Línea de trabajo

Start by tracing the ACP adapter’s handling of session/update messages and how it matches tool call IDs to open view_file calls; the issue does not name source files. Enable DUSK_DEBUG_ACP=1 and reproduce by asking Antigravity to read several workspace files. Done means read calls emit their completion before bot.turn.end, covered by a test for an Antigravity read.

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

Descripción

Version

0.2.15 (also seen on 0.2.12 before the update)

Platform

Own server (Windows 11 + WSL2 Ubuntu 24.04)

Engine

Gemini 4 Hydrogen via Antigravity ACP (agy_acp_server.par in bwrap)

What happened

Expected: each view_file tool call is marked done when Antigravity finishes it, like Read on the Claude engine.

Actual: the chat shows "Running view_file" for minutes (users see "Digging around" for 10 to 14 minutes). In logs/trail-server.jsonl (16 Nov 22:32 to 17 Nov 18:33 WIB):

count
Running view_file events 393
logged ok:true, all within 2 s of bot.turn.end 195
logged ok:false mid-turn 189
ok:true logged mid-turn 0
completions sharing the same second with others 358 (bursts up to 20)

Median logged duration 52 s, p90 366 s, max 957 s. Claude engine Read in the same period: 119 calls, median 0.2 s, 97% ok. Running client_view_file: 10 calls, 3 ok.

So a view_file is never closed when it actually finishes. It is closed in a batch, either as failed when the next step starts or as ok when the turn ends. The status the user sees and the durations in the log are both wrong, which makes every Gemini turn look stuck and makes the "slow model" notice fire.

Steps to reproduce
  1. Bot on Antigravity / Gemini 4 Hydrogen, ask it to read 5 files in its workspace and summarize them.
  2. Watch the chat: each "Running view_file" stays until the turn ends.
  3. grep 'view_file' ~/.duskbot/logs/trail-server.jsonl and compare ts with the turn's bot.turn.end.
Likely cause (hypothesis, not confirmed in source)

The ACP adapter does not match Antigravity's tool_call_update with status: completed to the open view_file call (different toolCallId, or the update arrives without the status field the adapter checks), so the call is only settled by the end-of-step or end-of-turn sweep.

Suggested fix

Log the raw session/update messages for one view_file with DUSK_DEBUG_ACP=1 and settle the call on the first update that carries completed/failed or content for that toolCallId. Add a test that bot.tool for an Antigravity read is emitted before bot.turn.end.

Lenguaje dominante
TypeScript
Estrellas
277
Forks
27
Merge medio
2 h 47 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 DuskBotAI/duskbot

Todos los issues de DuskBotAI/duskbot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.