# GitHub Copilot Projects gives coding agents persistent goals across repositories GitHub's October 28 Copilot Projects preview moves agent work beyond a single repository session: one project can hold a continuing goal, shared files, multiple agent sessions, pull requests and recurring tasks. The app coordinates progress and flags decisions for review, but remains a preview rather than a demonstrated autonomous project manager. Copilot Projects can coordinate agents, files and recurring tasks across repositories or non-code work; review and permissions remain human responsibilities. - Status: Active - Published: 2026-10-30T06:27:59+13:00 - Updated: 2026-10-30T06:27:59+13:00 - Categories: Artificial Intelligence, Web Development, AI Coding, Developer Tools - Tags: AI agents, Automation, Coding agents, GitHub, GitHub Copilot - Canonical HTML: https://beyondthe.news/dossiers/github-copilot-projects-multirepo-agent-work-public-preview-2026 ## What changed On October 28, 2026, GitHub introduced Copilot Projects in public preview within the GitHub Copilot desktop app. Instead of starting each task as a separate repository-scoped session, a user creates a project with an ongoing goal, optional repositories and reference files. Copilot can coordinate multiple agent sessions, recurring automations and artifacts, including work that spans repositories or does not require a repository. A project overview groups work into Needs input, Open, Working and Done, with links to pull requests and the underlying sessions for steering. ## Why it matters Cross-repository features and small-team launch tasks often require more than a code edit. A persistent project gives agents a common place for specifications, intermediate results and follow-up instructions, reducing manual context transfer between sessions. For small teams, the more consequential shift is coordination and traceability, not an unverified productivity multiplier. Generated changes still require code review, tests, permission boundaries and clear ownership of recurring actions. ## A project is a goal, not another Git branch Users can create a project with one or more repositories, or no repository at all, and add documents, folders or design files to its Library. Copilot starts and coordinates sessions toward the goal. This differs from an ordinary single-repository agent session because the same project context persists across related work and results. ## Review queue and steering keep a person involved The overview separates Needs input (decisions, permissions and reviews), Open (including pull requests), Working and Done. Users can inspect individual sessions, see changes and plans, and send steering messages. The product does not imply that agents can bypass repository merge checks or that every output is correct. ## Recurring automations live alongside the project A user can describe a recurring task in the project conversation, such as summarising new feedback weekly. GitHub documents checking its schedule in the project's Automations tab. This adds operational convenience but also makes monitoring task ownership, permissions, costs and stale context important. ## Boundaries and adoption GitHub labels Projects a public preview and says it may change. The Copilot app is available across Copilot plans, but actual model access, usage limits and organisational policies still depend on account settings. No independent benchmark establishes that Projects improves delivery speed, review quality or total cost versus existing agent workflows. ## Key details - Announced October 28, 2026; Copilot Projects are in public preview. - Projects span one or more repositories or work without a repository. - Users add files/folders to a project Library and can inspect generated artifacts. - Copilot coordinates sessions and can create pull requests for review. - Overview groups Needs input, Open, Working and Done. - Recurring tasks can be configured from project chat and checked in Automations. - Preview may change; normal permissions, code review and usage limits still apply. ## Builder takeaways - Use Projects for a defined multi-step outcome rather than every small code edit. - Attach authoritative specifications and constraints to the project Library. - Review the Needs input queue and inspect PR diffs and tests before merging. - Give recurring tasks explicit outputs, cadence and ownership, then monitor their results. - Do not assume the preview guarantees autonomous success or lower agent costs. ## What to watch - Preview-to-GA timeline and organisation-level controls. - Cross-repository permissions and artifact provenance improvements. - Recurring automation reliability and billing/usage behaviour. - Independent comparisons with Claude Code Projects and other multi-agent coordinators. ## Uncertainties - No independent evidence yet quantifies speed, quality or cost gains. - Public-preview features and eligibility may change. - Repository access and model availability depend on plan and organisational policy. - Project coordination does not itself replace human merge approval or testing. ## Sources - [GitHub Copilot app, Universe releases](https://github.blog/changelog/2026-10-28-github-copilot-app-universe-releases/) — GitHub Changelog · primary product announcement · 2026-10-28T00:00:00+13:00. Projects preview, multi-repo goals, session coordination and automation. - [Working with projects in the GitHub Copilot app](https://docs.github.com/en/copilot/how-tos/github-copilot-app/working-with-projects) — GitHub Documentation · primary implementation documentation · 2026-10-29T00:00:00+13:00. Setup, Library, review queue, recurring task configuration and preview status.