Microsoft's Build CLI Turns Conference Talks Into Working Code Instantly
Microsoft's new Build CLI plugin lets GitHub Copilot read your project dependencies and surface relevant Build 2026 sessions, then scaffold working code from what you learn.
Takeaways
- What it is: Microsoft Build CLI is a free GitHub Copilot CLI plugin that connects your project to the Build 2026 session catalog.
- Dependency scanning: It reads
package.json,requirements.txt,.csproj, and other manifests to recommend sessions relevant to your actual stack. - Three-phase workflow: Covers planning your schedule before Build, logging notes during sessions, and scaffolding working code afterward.
- Multi-client support: Works in GitHub Copilot CLI, VS Code, Visual Studio 2026, and Claude Code via the same plugin package.
- Live catalog API: Pulls from the live Build 2026 API with no stale data; falls back to Microsoft Learn MCP Server for docs and code samples.
- Limitations: Requires network access, depends on manifest files being present, and is scoped to Microsoft events only.
Conference session catalogs are a graveyard of good intentions. You bookmark 40 talks, attend 12, and leave with a pile of notes that never make it into your codebase. Microsoft just shipped a tool that tries to close that loop entirely -- and it lives in your terminal.
The Microsoft Build CLI is a GitHub Copilot CLI skill -- a plugin that extends the agent with specialized knowledge -- that connects your local project directly to the Build 2026 session catalog. It reads your dependencies, finds relevant sessions, and helps you act on what you learn, all from your terminal.
One command to install, zero context-switching
Getting started takes about 30 seconds. Open GitHub Copilot CLI in any project and run:
/plugin install microsoft/Build-CLI
/restartThen just ask it a question in plain English:
What Build sessions are relevant to my project?The skill reads package.json, requirements.txt, .csproj, go.mod, and other dependency files, maps them to Microsoft products, and searches the live Build 2026 session catalog. No configuration, no API keys, no manual tagging of your stack.
Node.js 22+ is recommended -- it enables the @microsoft/events-cli package for faster local search and caching. Without it, the skill falls back to direct HTTP and everything still works.
Three phases, one workflow
The skill is designed around the full conference lifecycle, not just discovery. The commands break down into three distinct phases:
Before Build -- plan your schedule:
- "What Build sessions should I attend?" -- scans your project and returns a ranked list
- "What's new at Build for Azure Cosmos DB?" -- topic-specific browsing
- "Tell me about session BRK155" -- look up any session by its code
During Build -- capture what matters:
- "Log a note from session BRK155: great agent demo" -- ties your notes to specific sessions
- "What should I do after session BRK155?" -- generates next steps in context
After Build -- ship what you learned:
- "Scaffold a project from session BRK155" -- generates working starter code based on session content
- "What changed at Build for my project?" -- surfaces the delta relevant to your stack
How it actually works under the hood
A Copilot CLI skill (also called an Agent Skill) is a discrete, callable capability packaged as a SKILL.md file with YAML frontmatter and Markdown instructions. Skills are task-specific instructions that Copilot loads automatically when your prompt matches the skill's description. The Build CLI packages this into an installable plugin -- a bundle that can include skills, MCP server configurations, and custom agents in one unit.
The skill itself is a thin layer over the live Build 2026 catalog API -- no stale data, no manual updates. For SDK docs and code samples, it falls back to the Microsoft Learn MCP Server. MCP (Model Context Protocol) is a standard that lets AI agents call external tools and data sources; here it gives the skill access to Microsoft's documentation and code sample library without baking that content into the plugin itself.
The repo also ships with a .mcp.json file and a .claude-plugin directory, meaning the same skill works across multiple clients:
- GitHub Copilot CLI:
/plugin install microsoft/Build-CLI - VS Code: Search
@agentPlugins microsoft-eventsin the Extensions panel - Visual Studio 2026: Copy
skills/microsoft-build/to a supported skill location - Claude Code:
/plugin marketplace add microsoft/Build-CLI
Where it falls short
The dependency-scanning approach is clever but has a hard ceiling. Recommendations are only as good as the dependency files in your project root. If your project doesn't have a manifest file, you need to tell the skill your stack directly. Projects with monorepo structures, unusual build systems, or dependencies that don't map cleanly to Microsoft products will get weaker results.
The tool is also not offline -- it requires network access to query both the catalog API and the Learn MCP server. And while it indexes Build 2025 and Ignite 2025 alongside Build 2026, it's explicitly scoped to the Microsoft event ecosystem. It won't help you navigate AWS re:Invent or Google I/O sessions.
The bigger picture
This release is a small but telling signal about where developer tooling is heading. The plugin system is the primary extensibility framework for GitHub Copilot CLI, integrating custom agents, MCP servers, and skills into a unified installation and discovery lifecycle. Microsoft is essentially treating the CLI as a platform -- one where domain-specific knowledge (like a conference catalog) can be installed the same way you'd install an npm package.
The scaffold-from-session feature is the most interesting piece. The gap between "I watched a great talk about Azure AI Foundry" and "I have a working project using it" has historically required hours of documentation hunting. A tool that can collapse that into a single terminal command -- even imperfectly -- changes the calculus for how much value you can extract from a conference.
The project is free and open source under the MIT license, requires an existing GitHub Copilot subscription (no additional cost on top), and is available right now on GitHub.