Background agents in skill context cannot execute Bash commands

Resolved 💬 2 comments Opened Feb 20, 2026 by simpsonw Closed Feb 20, 2026

Description

When a skill (like /claudit:audit) launches a background agent using the Task tool, the background agent encounters permission denials when attempting to use the Bash tool.

Steps to Reproduce

  1. Run /claudit:audit (or any skill that launches background agents needing Bash access)
  2. The skill launches a background agent with subagent_type: "general-purpose" and run_in_background: true
  3. The background agent attempts to execute Bash commands
  4. The agent receives permission denials and cannot execute the workflow

Expected Behavior

Background agents launched from skills should have the same tool permissions as the parent skill/session, including Bash tool access.

Actual Behavior

Background agents report Bash access denied, preventing execution of workflows that require system commands (git operations, directory creation, file discovery, etc.).

Impact

This prevents multi-step audit workflows (like claudit) from functioning correctly. The claudit orchestrator needs Bash to:

  • Determine repository name (gh repo view)
  • Create audit directories (mkdir -p)
  • Check git history for baseline dates
  • Discover code scopes via file system traversal
  • Launch parallel auditor subagents
  • Collect and process results

Environment

  • Command: /claudit:audit
  • Skill: claudit@etsy-claudit version 0.6.0
  • Session type: Main conversation (not plan mode)

Workaround

None found. The orchestrator workflow cannot proceed without Bash access.

Notes

The parent session (where /claudit:audit was invoked) has full Bash access. Only the background agent launched via Task tool encounters the restriction.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗