Safety prompts recur across run_skill and transfer_task sub-sessions

Aberta
#4,882 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@onatozmenn já está trabalhando nisso.

Desde 12/11/2026.

  • #4915 de @onatozmenn — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, go
Domínio
security, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
4.7k
Forks
565
Merge médio
18h 52min
PRs com merge (30d)
221

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de docker/docker-agent

Todas as issues de docker/docker-agent

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.