fix: remove GH_AW_AGENT_TOKEN from reply-to-pr-review-comment safe output in create-issue-command workflow#90
Draft
fix: remove GH_AW_AGENT_TOKEN from reply-to-pr-review-comment safe output in create-issue-command workflow#90
Conversation
…tput to fix create-issue workflow Co-authored-by: pmalarme <686568+pmalarme@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Debug workflow failure in create issue command
fix: remove GH_AW_AGENT_TOKEN from reply-to-pr-review-comment safe output in create-issue-command workflow
Feb 19, 2026
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.
The
create-issue-commandagentic workflow was failing becausereply-to-pull-request-review-commentwas configured withgithub-token: ${{ secrets.GH_AW_AGENT_TOKEN }}, a secret that isn't set in the repo. This caused two failures: the tool was excluded from the agent's available MCP tools (so no reply was ever sent), and the invalid token triggered a401on MCP gateway cleanup, failing the job.Changes
create-issue-command.md: Removegithub-token: ${{ secrets.GH_AW_AGENT_TOKEN }}fromreply-to-pull-request-review-comment. Thesafe_outputsjob already haspull-requests: writeand usesGH_AW_GITHUB_TOKEN || GITHUB_TOKEN— no custom token needed.create-issue-command.lock.yml:reply_to_pull_request_review_comment: {max: 1}to the agent job'sconfig.jsonso the MCP safe-outputs server exposes the tool to the agent.reply_to_pull_request_review_commentinvalidation.json(body,comment_id,pull_request_number).Testing
uv run poe checkconfig.jsonmismatch between what compiler emitted and what the MCP gateway served to the agent.Checklist
Additional context
The gh-aw compiler excludes a safe output from the agent-side
config.jsonwhen a customgithub-tokenis specified, while still including it intools.jsonand thesafe_outputsjob's handler config — creating a silent mismatch where the tool appears compiled-in but is never reachable by the agent.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.