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

fix(afk-loop): a subagent's rm or heredoc call stops the unattended loop on a confirmation prompt

Abierto Apto para principiantes
#671 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
76/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo

Línea de trabajo

Lee worker-prompt.md, reviewer-prompt.md, SKILL.md y docs/agents/agent-tool-traps.md. Actualiza los prompts con las dos reglas medidas para las llamadas al shell y asegúrate de que los workers transmitan ambas reglas a todos los subagentes. Nombra la trampa de confirmación que afecta a todo el bucle en SKILL.md y registra los tres casos medidos en el documento sobre las trampas de las herramientas de los agentes. La tarea estará completa cuando cada criterio de aceptación esté reflejado en esos archivos.

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

Descripción

bug needs-triage p2 repo

What happens

/afk-loop runs unattended, in a session started with --dangerously-skip-permissions. Claude Code still asks for confirmation on some Bash calls in that mode. While a subagent waits for that answer, its parent's turn waits too, so the whole loop stops until a person answers.

Measured in session afk-loop-498-20261028 on 2026-10-28:

Subagent Call Wait
Diagram subagent of the #439 worker rm of *.visual-check.* files 00:21 to 07:57 UTC, about 7.5 hours. The maintainer was asleep
Round 2 pr-test-analyzer of PR #665 A heredoc that writes a probe workflow file About 53 minutes
Diagram subagent of the #483 worker rm -f of the PNGs in its scratchpad 62 seconds. The maintainer was at the keyboard. Its other Bash calls took 0 to 4 seconds

The #439 worker also waited 18, 34 and 19 minutes for the first subagent, which the loop reported as "pushed without report".

Today nothing in worker-prompt.md or reviewer-prompt.md tells a subagent to avoid these calls. The diagram subagent is spawned by a worker, not by the loop, so it gets only what the worker passes on.

Acceptance criteria

  • worker-prompt.md and reviewer-prompt.md state that the subagent deletes no file with rm, and leaves its scratch files in its scratchpad.
  • Both state that the subagent writes a file with the Write tool, not with a shell heredoc.
  • worker-prompt.md states that the worker passes both rules on, in its own words or verbatim, to the prompt of every subagent it spawns.
  • SKILL.md names the trap: a confirmation prompt under --dangerously-skip-permissions stops the whole loop, not only the subagent that asked.
  • docs/agents/agent-tool-traps.md records the three measured cases above.

Not decided

  • Only rm and a heredoc have been measured. Whether find -delete, git clean or other calls also ask is unknown. The rules above cover the two measured ones and nothing more.
  • Whether a prompt in an unattended loop can be detected and reported, rather than waited on, is not part of this ticket.
Lenguaje dominante
HTML
Estrellas
1
Forks
0
Merge medio
59 min
PR fusionados (30 d)
16

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 unic/unic-agents-plugins

Todos los issues de unic/unic-agents-plugins

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.