GitHub Copilot SDK & Extensions
Build Copilot-powered apps and deploy to Azure.
Quick Reference
| Property | Value |
|---|---|
| Paths | SDK (@github/copilot-sdk) · Extensions (@copilot-extensions/preview-sdk) |
When to Use
- •Build an app with the Copilot SDK or create a Copilot Extension
- •Deploy a Copilot-powered app to Azure
Path Detection
"Copilot SDK" / "@github/copilot-sdk" → SDK path. "Copilot Extension" / "webhook" → Extensions path.
Prerequisites
Docker required — run docker info to verify.
Workflow
Step 1: Scaffold + Customize
- •SDK path → Run
azd init --template jongio/copilot-sdk-agentto scaffold the project. The template's chat app is just an example — adapt the code to the user's scenario. Build a custom UI that fits the use case (it's most likely not a chat experience). See Copilot SDK reference. - •Extensions path → Extensions reference
⚠️ SDK template has infra, test UI, Dockerfile — do NOT recreate.
Step 2: Test
SDK: template includes React web UI — run azd app run. Extensions: see Extensions reference.
Step 3: Deploy
⛔ MANDATORY: You MUST invoke these three skills IN ORDER. Do NOT run
azd upor any deployment commands directly.
- •Invoke the azure-prepare skill — it creates the deployment manifest. The SDK template already has
azure.yaml,infra/, and Dockerfile, so tell it not to regenerate those. - •Invoke the azure-validate skill — it prompts the user for subscription/region and validates the deployment.
- •Invoke the azure-deploy skill — it executes the deployment.
Step 4: Foundry Bridge (Optional)
See Foundry bridge.
Rules
- •Read the template's
AGENTS.mdbefore making changes — it has coding conventions and commands - •Render markdown in agent responses properly in the UI