{"id":94665,"date":"2026-03-24T09:00:00","date_gmt":"2026-03-24T16:00:00","guid":{"rendered":"https:\/\/github.blog\/?p=94665"},"modified":"2026-04-22T13:46:26","modified_gmt":"2026-04-22T20:46:26","slug":"building-ai-powered-github-issue-triage-with-the-copilot-sdk","status":"publish","type":"post","link":"https:\/\/github.blog\/ai-and-ml\/github-copilot\/building-ai-powered-github-issue-triage-with-the-copilot-sdk\/","title":{"rendered":"Building AI-powered GitHub issue triage with the Copilot SDK"},"content":{"rendered":"\n

The Copilot SDK lets you add the same AI that powers Copilot Chat<\/a> to your own applications. I wanted to see what that looks like in practice, so I built an issue triage app called IssueCrush. Here’s what I learned and how you can get started.<\/p>\n\n\n\n

If you’ve ever maintained an open source project, or worked on a team with active repositories, you know the feeling. You open GitHub and see that notification badge: 47 issues. Some are bugs, some are feature requests, some are questions that should be discussions, and some are duplicates of issues from three years ago.<\/p>\n\n\n\n

The mental overhead of triaging issues is real. Each one requires context-switching: read the title, scan the description, check the labels, think about priority, decide what to do. Multiply that by dozens of issues across multiple repositories, and suddenly your brain is mush.<\/p>\n\n\n\n

I wanted to make this faster. And with the GitHub Copilot SDK, I found a way.<\/p>\n\n\n\n

Enter IssueCrush: Swipe right to ship<\/h2>\n\n\n\n

IssueCrush shows your GitHub issues as swipeable cards. Left to close, right to keep. When you tap “Get AI Summary,” Copilot reads the issue and tells you what it’s about and what to do with it. Instead of reading through every lengthy description, maintainers can get instant, actionable context to make faster triage decisions. Here’s how I integrated the GitHub Copilot SDK to make it happen.<\/p>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

The architecture challenge<\/h2>\n\n\n\n

The first technical decision was figuring out where to run the Copilot SDK. React Native apps can’t directly use Node.js packages, and the Copilot SDK requires a Node.js runtime. Internally, the SDK manages a local Copilot CLI process and communicates with it over JSON-RPC. Because of this dependency on the CLI binary and a Node environment, the integration must run server-side rather than directly in a React Native app. This means the server must have the Copilot CLI installed and available on the system PATH.<\/p>\n\n\n\n

I settled on a server-side integration pattern:<\/p>\n\n\n\n

\"Architecture<\/figure>\n\n\n\n

Here’s why this setup works:<\/p>\n\n\n\n