Skip to content

Latest Copilot CLI v1.0.22 blocks safeoutputs MCP server #25550

Closed

Description

@kthompson

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.

Activity

  1. pelikhan commented on Apr 9, 2026

    @pelikhan
    Collaborator

    You can pin copilot for now.

    engine:
    id: copilot
    version: v1.0.20

  2. locked and limited conversation to collaborators on Apr 9, 2026
  3. unlocked this conversation on Apr 9, 2026
  4. lpcox commented on Apr 9, 2026

    @lpcox
    Collaborator

    @kthompson what version of gh-aw were you using when you saw this error?

  5. kthompson commented on Apr 9, 2026

    @kthompson
    Author

    @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.

  6. lpcox commented on Apr 10, 2026

    @lpcox
    Collaborator

    @lpcox I was on v0.65.x but after running into this I updated to v0.67.1.

    Also pinning the copilot version to v1.0.20 seems to work around the issue.

    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.

  7. locked and limited conversation to collaborators on Apr 10, 2026
  8. unlocked this conversation on Apr 10, 2026
  9. sg650 commented on Apr 10, 2026

    @sg650

    Also, seeing this in all our workflows.

    So then this will be resolved with a future update to the CLI project @lpcox ?

  10. lpcox commented on Apr 10, 2026

    @lpcox
    Collaborator
  11. locked and limited conversation to collaborators on Apr 10, 2026
  12. unlocked this conversation on Apr 10, 2026
  13. bryanchen-d commented on Apr 10, 2026

    @bryanchen-d

    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
    

    Any ideas?

  14. locked and limited conversation to collaborators on Apr 10, 2026
  15. unlocked this conversation on Apr 10, 2026
  16. lpcox commented on Apr 10, 2026

    @lpcox
    Collaborator

    @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

  17. srgibbs99 commented on Apr 13, 2026

    @srgibbs99

    @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

    I updated to 0.68.1 and pinned to copilot cli 1.0.21 and things seem to be smooth now. Are we OK to unpin now, is that handled by gh-aw now?

  18. locked and limited conversation to collaborators on Apr 13, 2026
  19. unlocked this conversation on Apr 13, 2026
  20. dsyme commented on Apr 15, 2026

    @dsyme
    Collaborator

    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
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions