Show when a run was stopped or interrupted, and tell the agent
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- ai-infra-agents
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- TypeScript
- Estrelas
- 1
- Forks
- 0
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Sem guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/ace2
-
documentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
githubnext/ace2#530 · 1 comentário ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
githubnext/ace2#437 ·
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/ace2#529 ·
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 45/100
githubnext/ace2#528 ·
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 20/100
githubnext/ace2#511 ·
Todas as issues de githubnext/ace2
Issues semelhantes
-
skillopt: success-reflect prompt omits the edit schema, so every success-only edit is droppedAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Workspace secrets/constants containing "$" are corrupted when resolved in data source optionsAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
mobile-next/mobile-mcp#526 ·
Mantenedores costumam responder em até 1 dia
-
e2e-failure ready-to-code
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 73/100
redhat-developer/rhdh-plugin-export-overlays#4470 · 1 comentário ·
Mantenedores costumam responder em até 1 dia