Repository navigation
Conversation
…lignment and Design Decision Gate workflows Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…triction Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix max turns issue due to Bash permission denials
Fix Step Name Alignment and Design Decision Gate max-turns failures from bash allow-list/working-directory mismatch
May 10, 2026
Contributor
|
Hey One thing worth addressing before merge:
If you'd like a hand adding coverage, here's a ready-to-use prompt:
|
github-actions
Bot
deleted the
copilot/aw-failures-fix-bash-permission-denials
branch
May 18, 2026 03:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug Fix
What was the bug?
Both workflows exhausted
--max-turnswith zero forward progress: every turn was apermission_denial. Two independent blocking layers:jqabsent from--allowed-tools— both prompts calljqextensively, but it wasn't in either workflow's bash allow-list, so every invocation was denied before reaching the shell./tmp/gh-aw/agent/, outside the session's allowed directory (/home/runner/work/gh-aw/gh-aw). Even allow-listed commands were blocked at the Claude Code layer with:cat in '/tmp/gh-aw/agent/...' was blocked. Claude Code may only concatenate files from the allowed working directories.How did you fix it?
step-name-alignment.mdjq:*to the bash allow-listRead/Writetools (not Bash) for cache-memory access — Bashcatto/tmp/is blocked at the Claude Code layer despite appearing in the compiled allow-list;Read(/tmp/gh-aw/cache-memory/*)andWrite(/tmp/gh-aw/cache-memory/*)grants bypass this restrictiondesign-decision-gate.mdjq:*andmkdir:*to the bash allow-list/tmp/gh-aw/agent/→${{ github.workspace }}/.gh-aw-context/so all pre-fetched files land inside the Claude Code working directory and are directly readable by the agent/tmp/gh-aw/agent/…→.gh-aw-context/…Both lock files recompiled after changes.