Skip to content
Industry Hub
← Industry News

GitHub Universe 2026 brings multi-repository work to Copilot Projects

Copilot Projects enters public preview, bringing repositories, specifications, and agent work together in the Copilot app.

Industry Insights 2 min read
  • #GitHub
  • #Copilot
  • #Universe
  • #agents

GitHub’s October 28 Universe announcements move Copilot beyond a conversation about one repository. Copilot Projects is in public preview in the Copilot app, bringing a goal, related repositories, and supporting context into a shared workspace for agent work.

The distinction matters for tasks that cross boundaries: a feature might require a backend change, a frontend update, and documentation in a third repository. Projects gives those activities a common context rather than making the developer repeat the specification in each session.

Context becomes part of the workflow

GitHub describes projects that can incorporate specifications, designs, assets, and discussions alongside code. Copilot can coordinate background work and bring results, including pull requests, back for approval.

That does not make a project the right starting point for every task. A focused repository session still makes sense for a small bug fix. The project workflow is more interesting when the outcome spans several repositories or includes non-code deliverables.

For example, a team could attach a feature specification and the relevant repositories, then ask for an implementation and documentation update. That is an illustrative workflow, not a promise that every integration or repository combination is supported.

Desktop actions have a separate permission boundary

The same Copilot app release introduces Computer Use in public preview on macOS and Windows. It lets Copilot interact with desktop applications, including applications without a dedicated API or CLI.

GitHub requires approval for the applications Copilot uses, and organizations can disable the feature through managed settings. On macOS, setup also requires Accessibility and Screen Recording permissions.

Computer Use is not a prerequisite for every project. Teams should distinguish repository and tool access from permission to read or operate desktop applications. Giving an agent a project goal should not be treated as blanket approval to access unrelated apps.

What teams should evaluate

The practical question is whether shared context reduces coordination work without making review harder. For a pilot, choose a bounded cross-repository change and define the expected deliverables before starting. Review each repository’s changes independently, and keep approval of desktop actions separate from approval of code.

Projects and Computer Use are previews in the October 28 announcement, reviewed here on October 31, 2026. They should not be confused with the general availability of Copilot Fusion.

Sources