Agent skill · software engineering · github
foundry-hosted-agent-copilotkit
Ongoing development guidance for agentic web apps that pair a CopilotKit frontend with Microsoft Agent Framework agents on Azure AI Foundry hosted agents over the AG-UI protocol - add and gate agent tools, wire human-in-the-loop approvals, build generative UI and shared state, debug the event stream, upgrade pre-1.0 packages safely, and deploy hosted agent updates.
Why this skill is useful
Adds detailed workflows, debugging techniques, and integration patterns specific to the CopilotKit and Azure AI Foundry stack that the AI wouldn't reliably generate on its own.
What it needs
Requires @copilotkit/*, next.js, react installed locally. Requires azure account access. About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Developing with CopilotKit + AG-UI + Azure AI Foundry Hosted Agents Use this skill for development work inside an EXISTING application built on this stack: a React/Next.js frontend using CopilotKit, connected over the AG-UI protocol to a Microsoft Agent Framework (MAF) agent (Python or .NET) that runs as — or is being developed against — an Azure AI Foundry hosted agent (paid Azure service; usage may incur costs). Do NOT use this skill to scaffold a new project. Dedicated scaffolders exist (the CopilotKit CLI, azd ai agent init); use those, then return here for everything that follows: adding tools, gating them behind approvals, generative UI, shared state, debugging, dependency upgrades, and deploying agent updates. Mental model The single most important fact: a deployed Foundry hosted agent endpoint does not speak AG-UI by default. It exposes an OpenAI Responses endpoint (.../protocols/openai/responses) and/or a raw .../protocols/invocations endpoint. AG-UI must be produced somewhere, and where it is produced determines how every feature (especially human-in-the-loop) behaves. The three wirings are described in references/architecture.md. Workflow Follow these steps for every task on this stack: 1. Identify the wiring first. Inspect the codebase before changing anything: addagentframeworkfastapiendpoint(...) (Python) or MapAGUI(...) (.NET) wrapping an in-process agent → Architecture A (in-process AG-UI endpoint). A hosted agent whose own container serves AG-UI, declared with protocol: invocations in agent.yaml → Architecture B. A separate service translating between the AG-UI endpoint and a hosted agent's /responses endpoint (look for previousresponseid, mcpapprovalresponse, or a Foundry conversation object in the code) → Architecture C (translation bridge). Confirm the frontend agent name: the key in the runtime agents config, the agent prop on the <CopilotKit> provider, and the hosted agent name in agent.yaml must all agree. 2. Ground in live documentation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/foundry-hosted-agent-copilotkit