Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Concurrent subagent dispatch: `additionalDirectories` glob doesn't propagate from parent to child

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

When a parent agent dispatches a subagent (via the Agent / Task tool), the child subagent's permission resolver does not consistently honor glob-based entries in the parent's additionalDirectories. The child gets denied (or re-prompted) on paths that the parent has explicit permission to read via its own additionalDirectories globs.

Root Cause

Possibly related to F7 (Edit/Write re-prompt) and F8 (parallel dispatch state drift) — filing separate issues in case the root causes differ; feel free to consolidate at triage if they're the same bug.

Fix Action

Workaround

Serial dispatch works fine. We've pivoted our remediation program (183/185 findings closed across 30+ PRs) to serial execution. Parallel dispatch has been blocked since 2026-04-18.

RAW_BUFFERClick to expand / collapse

Summary

When a parent agent dispatches a subagent (via the Agent / Task tool), the child subagent's permission resolver does not consistently honor glob-based entries in the parent's additionalDirectories. The child gets denied (or re-prompted) on paths that the parent has explicit permission to read via its own additionalDirectories globs.

Setup

  • Claude Code CLI running with .claude/settings.json + .claude/settings.local.json
  • Parent session has additionalDirectories: ["/repo/worktrees/*/.claude/features", "/repo/worktrees/*/.claude/shared"] (glob entries)
  • Parent successfully reads files matching those globs
  • Parent dispatches a child subagent with a prompt that asks the child to read a file matching the same glob

Expected

Child can read the file without prompting — it's within the parent's declared additionalDirectories surface.

Actual

Child is denied or prompted on first read, as if the glob entries weren't honored.

Reproducer

Minimal reproducer harness: https://github.com/Regevba/FitTracker2/tree/main/docs/superpowers/plans/f6-f9-reproducer (see child-agent-task-template.md § F6 and classification-template.md § F6).

Why we think it's not a config issue

We added the worktree glob entries to settings.local.json in wave-2 of a stress test. The wave still failed with per-child permission denials, ruling out the "missing declaration" hypothesis. See the "Framework Bug Saga" section of our post-stress-test case study for the full timeline.

Related

Possibly related to F7 (Edit/Write re-prompt) and F8 (parallel dispatch state drift) — filing separate issues in case the root causes differ; feel free to consolidate at triage if they're the same bug.

Workaround

Serial dispatch works fine. We've pivoted our remediation program (183/185 findings closed across 30+ PRs) to serial execution. Parallel dispatch has been blocked since 2026-04-18.

extent analysis

TL;DR

The most likely fix is to modify the permission resolver to correctly handle glob-based entries in the parent's additionalDirectories when dispatching subagents.

Guidance

  • Review the implementation of the permission resolver in the Agent / Task tool to ensure it properly handles glob patterns when checking permissions for subagents.
  • Verify that the additionalDirectories configuration is being correctly passed from the parent agent to the subagent, and that the glob entries are being expanded correctly.
  • Consider modifying the subagent dispatch process to explicitly set the additionalDirectories configuration for the child agent, ensuring that it includes the glob entries from the parent agent.
  • Investigate the possibility of a timing issue, where the permission resolver is being called before the glob entries have been fully expanded or processed.

Example

No code snippet is provided as the issue does not include specific implementation details.

Notes

The issue may be related to other reported issues (F7 and F8), and resolving this issue may require a deeper understanding of the underlying framework and its handling of permissions and glob patterns.

Recommendation

Apply a workaround by using serial dispatch, as it has been reported to work fine, until a proper fix can be implemented for parallel dispatch. This is because serial dispatch has been proven to be a reliable alternative, and it allows for continued progress on the remediation program.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Concurrent subagent dispatch: `additionalDirectories` glob doesn't propagate from parent to child