Skip to content

Restore Agentic Triage tool access - #11911

Closed
Timothee Guerin (timotheeguerin) wants to merge 1 commit into
microsoft:mainfrom
timotheeguerin:fix/agentic-triage-mcp
Closed

Timothee Guerin (timotheeguerin) wants to merge 1 commit into
microsoft:mainfrom
timotheeguerin:fix/agentic-triage-mcp

Conversation

@timotheeguerin

Copy link
Copy Markdown
Member

Agentic Triage can now start, but Copilot CLI 1.0.83 fails its MCP handshake with the gh-aw gateway. The model consequently receives no GitHub or safe-output tools, exits successfully without triaging the issue, and leaves no comment or labels.

Pin the workflow to Copilot CLI 1.0.80, the last version verified to negotiate these MCP servers correctly. This prevents gh-aw’s runtime compatibility matrix from silently selecting the affected 1.0.81+ releases.

Observed in https://github.com/microsoft/typespec/actions/runs/34386967939. The agent log reports MCP error -32022 for both github and safeoutputs; this is the regression documented in github/copilot-cli#4525.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

No changes needing a change description found.

@azure-sdk-automation

Copy link
Copy Markdown

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@timotheeguerin

Copy link
Copy Markdown
Member Author

Superseded by #11912, which restores both GitHub reads and safe outputs through the guarded MCP CLI wrappers without pinning an older Copilot CLI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant