You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Latest Copilot CLI v1.0.22 blocks safeoutputs MCP server #25550
Today we just started seeing this message in our agentic workflows under the agent / Execute GitHub Copilot CLI section:
! 2 MCP servers were blocked by policy: 'github', 'safeoutputs'
which are typically coupled with something like:
I need to call the safe-output tool directly from this conversation:
✗ create_pull_request branch: "no-ticket/maintain-agents-md-2026-04-09b", base: "main", title: "No …
└ Tool 'create_pull_request' does not exist.
I am not sure if this is due to a change in MCP support by copilot cli that was released today that needs to be updated in the workflows or if this is a bug in Copilot CLI. My workflows are for a private repo but let me know if there is something specific I can include to help.
pinning copilot to 1.0.20 or 1.0.21 still fail to work for our runs, it failed with a different error though:
[copilot-driver] 2026-04-10T21:10:51.124Z attempt 1: spawning: /usr/local/bin/copilot --add-dir /tmp/gh-aw/ --log-level all --log-dir /tmp/gh-aw/sandbox/agent/logs/ --disable-builtin-mcps --allow-all-tools --allow-all-paths --add-dir /home/runner/work/vscode-engineering/vscode-engineering --prompt <redacted>
[copilot-driver] 2026-04-10T21:10:51.129Z attempt 1: process started (pid=150)
Error: Authentication failed (Request ID: A029:5213:A3C858:B8321A:69D9675C)
Your GitHub token may be invalid, expired, or lacking the required permissions.
To resolve this, try the following:
• Start 'copilot' and run the '/login' command to re-authenticate
• If using a Fine-Grained PAT, ensure it has the 'Copilot Requests' permission enabled
• If using COPILOT_GITHUB_TOKEN, GH_TOKEN or GITHUB_TOKEN environment variable, verify the token is valid and not expired
• Run 'gh auth status' to check your current authentication status
This has noww been fixed. Existing installs of agentic workflows started to fail. This was due to an update to Copilot CLI causing agentic workflows to start to fail. We've now pinned that component.
To get your agentic workflows working again, do this:
gh extension upgrade gh-aw
gh aw compile
commit+push
Activity
pelikhan commentedon Apr 9, 2026
You can pin copilot for now.
engine:
id: copilot
version: v1.0.20
lpcox commentedon Apr 9, 2026
@kthompson what version of gh-aw were you using when you saw this error?
kthompson commentedon Apr 9, 2026
@lpcox I was on v0.65.x but after running into this I updated to v0.67.1 (and still had the issue).
Also pinning the copilot version to v1.0.20 seems to work around the issue.
lpcox commentedon Apr 10, 2026
Cool, I was a little worried that this could be a regression on our side. If pinning copilot solved it, then I think we're in good shape.
sg650 commentedon Apr 10, 2026
Also, seeing this in all our workflows.
So then this will be resolved with a future update to the CLI project @lpcox ?
lpcox commentedon Apr 10, 2026
@sg650 fix is in gh-aw:v0.67.4 (currently latest) https://github.com/github/gh-aw/releases/tag/v0.67.4
Update gh-aw to v0.68.0 and recompile workflows
Update gh-aw to v0.68.0 to fix MCP server blocking (#38089)
bryanchen-d commentedon Apr 10, 2026
pinning copilot to 1.0.20 or 1.0.21 still fail to work for our runs, it failed with a different error though:
Any ideas?
lpcox commentedon Apr 10, 2026
@sg650 @kthompson please update to gh-aw v0.68.1 https://github.com/github/gh-aw/releases/tag/v0.68.1
@bryanchen-d if this is in a public repo can you share a link to the action run? if not can you follow these instructions and share what copilot finds? https://github.com/github/gh-aw/blob/main/docs/src/content/docs/troubleshooting/debugging.md
srgibbs99 commentedon Apr 13, 2026
I updated to
0.68.1and pinned to copilot cli1.0.21and things seem to be smooth now. Are we OK to unpin now, is that handled bygh-awnow?dsyme commentedon Apr 15, 2026
This has noww been fixed. Existing installs of agentic workflows started to fail. This was due to an update to Copilot CLI causing agentic workflows to start to fail. We've now pinned that component.
To get your agentic workflows working again, do this:
community: update community contributions in README
Add agent compatibility matrix and validation
Add agent compatibility matrix and validation
Add agent compatibility matrix and validation