Safety prompts recur across run_skill and transfer_task sub-sessions

Ouverte
#4,882 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@onatozmenn y travaille déjà.

Depuis le 12/11/2026.

  • #4915 par @onatozmenn — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
docker, go
Domaine
security, testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
4.7k
Forks
565
Merge moyen
18 h 52 min
PR mergées (30 j)
221

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de docker/docker-agent

Toutes les issues de docker/docker-agent

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.