Copilot can now auto-triage, assign and close your GitHub issues
In public preview it applies only high-confidence label, assignee and close actions, each with a rationale; GitHub's MCP server also goes stateless.
Copy markdown
What Copilot can now do to your issues
In public preview, Copilot can label GitHub Issues, set their fields and type, assign them, and close them on its own. By default only high-confidence actions auto-apply — medium- and low-confidence ones wait as suggestions, each with a visible rationale — and repo admins set the confidence threshold.
Turning it on takes one setting
For the Copilot cloud agent, create an automation from the Automations pane in your repo's Agents tab — no update needed. For GitHub Agentic Workflows, add "issue-intents: true" to the workflow frontmatter. It's built for auto-triage, backfilling missing metadata, and flagging spam for review.
GitHub's MCP server drops sessions, adds conformance tests
Ahead of the July 28 MCP spec, the GitHub MCP Server now runs stateless — no Redis sessions, no initialize handshake, so clients handshake in parallel and deployments scale out. Elicitation moves to per-step HTTP requests, and new official conformance tests let you validate your own MCP agents. It stays backward-compatible, so nothing breaks.