Show when a run was stopped or interrupted, and tell the agent
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- ai-infra-agents
Línea de trabajo
Start from the timeline entry for a stopped run and from the path that sends the previous run's state into the agent's next turn. The payload names the desktop_insert entry with stopReason: aborted and the Stop action, but no source files, so locate those in the repo first. Done means three things: a stopped run shows who stopped it and when, a partial tool call is labeled as not run, and the next turn says the run was stopped or interrupted by a restart. Scope is cross-cutting, so confirm the approach in the thread before writing code.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Found in the desktop tools study (#427), D3 and D3b on Canary 0.0.46+684262d. Stopping and restarting worked: nothing was replayed, and an interrupted action was left as unknown. What the timeline shows doesn't match that.
Observed:
- After the owner presses Stop during a desktop run, the timeline shows the last tool calls as ordinary results, and nothing says the run was stopped. Tester confusion 1/3.
- In the next turn, the agent doesn't know its previous run was stopped by a person. It said: "Neither run hit an error or refusal on my side… I can't see why it stopped; my guess is the run was halted from outside."
- When the channel's worker is killed while the model is still writing a tool call, the partial call (arguments without
text,stopReason: aborted) shows as a reddesktop_insertentry with "Stopped.". It opens to nothing. The run then resumes after the worker restarts, and its summary ("Worked for 2 minutes 8 seconds") doesn't mention the restart. Tester confusion 2/3.
Expected:
- A Stop leaves a visible marker: who stopped it, when, and which in-flight action ended as unknown.
- The agent's next turn includes a note that the previous run was stopped by its owner, or interrupted by a restart.
- A tool call that never ran is labeled as such, for example "not run: the agent was interrupted while writing this call", and a resumed run says it resumed.
Part of #427.
- Lenguaje dominante
- TypeScript
- Estrellas
- 1
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/ace2
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 94/100
githubnext/ace2#487 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
githubnext/ace2#486 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
githubnext/ace2#459 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
githubnext/ace2#437 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 40/100
githubnext/ace2#440 ·
Todos los issues de githubnext/ace2
Issues similares
-
The inspector never shows the instances field, so scaling out is unreachablePosiblemente ocupada @Mrkewl la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
xevrion/breakscale#96 ·
Los mantenedores suelen responder en 4 días
-
Object parameters lose their structure when resources is enabledPosiblemente ocupada @asts-top la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
rossant/awesome-math#199 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
jaegertracing/jaeger-ui#4618 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
mifi/lossless-cut#3125 ·
Los mantenedores suelen responder en 1 día