GitHub turns Copilot into a multi-agent workspace with new Projects feature

At its GitHub Universe conference, GitHub launched a redesigned Copilot application that the company now positions as a central workspace for AI-driven software development. Instead of a single chat window, the new app connects AI agents with repositories, developer tools and project context, so that work can be planned, delegated and tracked in one place. The redesign effectively turns Copilot from a conversational assistant into an orchestration layer for development work, and GitHub describes the move as a bet on multi-agent software development, where several specialized agents cooperate on the same codebase under human supervision.

The centerpiece of the update is a new capability called Copilot Projects. Developers can assign agents goals that span multiple repositories at once, a coordination task that previously had to be handled manually across projects. Projects also lets teams attach context from outside the code: Slack conversations, design mockups and meeting notes can all be supplied to an agent as background material. Multiple agents can run in parallel on different parts of the same effort rather than waiting in a single queue. GitHub says the goal is to let agents work with the same material a human team would use, not just with source code.

Under the hood, Copilot distributes work across parallel agents, tracks their progress and returns results to the developer. The typical output is a pull request that a human reviews before anything is merged, which keeps people in control of what lands in the codebase. Because progress is tracked centrally, developers can see where each agent stands without chasing status updates. GitHub presents this as the operational model for the next phase of AI-assisted engineering: agents handle drafting, testing and iteration, while people set goals and approve outcomes.

For engineering teams, the change means rethinking how tasks are written: goals for agents must be specific enough to span repositories and end in a reviewable pull request, so task decomposition and clear acceptance criteria become daily skills. Team leads will need new routines for reviewing parallel streams of agent output, since several sets of changes can arrive at once. Security and compliance specialists face a new surface to govern: agents that read Slack conversations, meeting notes and design files work with data well beyond source code, so access policies, audit trails and retention rules need to cover agent context as well.

Organizations adopting the workspace should plan a staged rollout, starting with low-risk repositories, and should expect an adjustment period of weeks to months while review workflows stabilize.

GitHub lists Copilot Projects in public preview, and analysts quoted by InfoWorld flag parallel-agent conflicts, growing token bills and code review as the next bottleneck. Early users are advised to start with low-risk repositories.

Continue the conversation: https://t.me/AIAutomationArchitecture · Bluesky