GitHub Copilot Coding Agent: Windows Projects Now Supported
GitHub CopilotGitHub expanded the Copilot coding agent to support Windows-based development environments, removing a longstanding limitation that restricted the autonomous background agent to Linux. Teams working on Windows-targeted projects can now configure the agent to run in a Windows environment via a copilot-setup-steps.yml file, enabling it to build, test, and lint Windows-specific code before submitting a pull request. GitHub notes that the integrated firewall is incompatible with Windows, so network controls must be handled through self-hosted or larger runners with Azure private networking.
Sources & Mentions
3 external resources covering this update
GitHub Copilot Coding Agent Expands to Windows Development Environments
On February 18, 2026, GitHub announced that the Copilot coding agent — the platform's asynchronous, autonomous background agent — now supports Windows development environments. Previously, the agent operated exclusively in Linux-based environments by default, creating friction for teams whose projects target Windows or rely on Windows-specific tooling. This update extends the agent's reach to cover those workflows natively.
How the Coding Agent Works
The Copilot coding agent operates asynchronously and autonomously. Developers assign it a task by delegating a GitHub Issue or initiating a session through Copilot Chat, and the agent takes over from there — exploring the codebase, running tests, executing linters, and ultimately delivering a draft pull request for human review. The entire process runs in an ephemeral development environment powered by GitHub Actions, with the agent committing its progress as it works.
Configuring Windows Environments
Switching to a Windows environment requires creating a copilot-setup-steps.yml file in the repository root and specifying a custom runs-on setting that targets a Windows runner. The configuration follows the same conventions as GitHub Actions workflow files, making it familiar for teams already using Actions.
With proper setup, the coding agent can verify that a Windows project builds successfully, that automated test suites pass, and that linters run cleanly — all before raising a pull request, reducing the back-and-forth that comes with environment-specific failures caught only in review.
Firewall Compatibility and Network Controls
One important caveat accompanies the Windows support: the integrated firewall feature built into the Copilot coding agent is not compatible with Windows environments. For teams that need network egress controls — restricting what external services the agent can reach during a session — GitHub recommends using Windows only with self-hosted runners or larger runners configured with Azure private networking. This allows organizations to implement custom network controls at the infrastructure level in place of the built-in firewall.
Availability
The Windows environment support is available across all paid Copilot tiers — Pro, Pro+, Business, and Enterprise. Full configuration documentation is available in GitHub's docs under "Customizing the development environment for Copilot coding agent."