Safety prompts recur across run_skill and transfer_task sub-sessions

Abierto
#4,882 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@onatozmenn ya está trabajando en esto.

Desde el 12/11/2026.

  • #4915 de @onatozmenn — abierto

Evaluación

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

Línea de trabajo

Start by tracing how run_skill classifies read-only operations and how safety approvals are scoped when transfer_task creates a child session; the issue does not name source files or tests. Reproduce the reported flow, confirm both behaviors from the source, then add a focused regression test for a read-only skill crossing the sub-session boundary while preserving write confirmations and safety hooks.

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

Descripción

area/runtime area/security area/sessions area/skills

Problem

A prior session using Docker Agent dev build bbe70f53 observed repeated safety prompts across delegated work: 10/10 runs in the surviving log window prompted again. This report is about runtime safety-state/tool classification, not agent prompt design.

Working hypothesis from the observed behavior: launching a skill with run_skill does not mark its execution read-only, so the default safety mode prompts; an approve-autonomous decision appears scoped to the current sub-session, while transfer_task creates a new sub-session that prompts again. These details need source-level confirmation and a minimal reproduction by maintainers; the surviving observations alone do not establish the mechanism.

Reproduction to investigate

  1. In default safety mode, run a skill via run_skill that performs only read operations.
  2. Observe whether the tool launch prompts for approval despite being read-only.
  3. Grant the applicable autonomous/safety approval in that session, then delegate via transfer_task to a child session that performs the same read-only operation.
  4. Observe whether the new sub-session prompts again.

Reported observation: repeated prompts occurred in 10/10 runs visible in the surviving log window. This count is limited to that window and is not a broader rate estimate. No raw logs, private content, local paths, or credentials are attached.

Expected

Provide safe, explicit, least-privilege handling for read-only operations and/or scoped reuse of a user-granted safety policy across related sub-sessions, with clear visibility of scope. Preserve safety hooks and their enforcement. Reuse must not automatically authorize writes or bypass explicit confirmation for external, irreversible, or production-reaching writes.

Actual observation / uncertainty

Prompts recurred across skill/delegation runs. The proposed run_skill classification and per-sub-session approval scope are hypotheses, not independently verified source conclusions.

Environment / limitations

  • Docker Agent dev build: bbe70f53
  • macOS arm64
  • Prior-session observation; exact source revision and a standalone reproduction were not retained.

Please confirm the classification and approval-scope behavior, then add a focused regression test for a read-only skill crossing a transfer_task sub-session boundary.

Lenguaje dominante
Go
Estrellas
4.7k
Forks
565
Merge medio
18 h 52 min
PR fusionados (30 d)
221

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 docker/docker-agent

Todos los issues de docker/docker-agent

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.