Safety prompts recur across run_skill and transfer_task sub-sessions

Offen
#4,882 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@onatozmenn arbeitet bereits daran.

Seit 12.11.2026.

  • #4915 von @onatozmenn — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker, go
Bereich
security, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Go
Sterne
4.7k
Forks
565
Ø Merge
18 Std. 52 Min.
Gemergte PRs (30 T.)
221

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus docker/docker-agent

Alle Issues in docker/docker-agent

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.