Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Small-team tasks

Run work that spans several repos in one Copilot Project, and keep computer use on a short leash

Written November 1, 2026

For a developer whose feature touches three repos plus a design document: Copilot Projects, in public preview in the GitHub Copilot app since 28 October 2026, give that work one home, with parallel agent sessions and pull requests to review. Computer use, in the same release, can drive desktop apps — pilot it separately, on a machine with nothing sensitive on it.

What changed

Work does not always fit in a single repository or session, GitHub's changelog says: a feature can span several repositories, and a launch plan can pull in specs, designs, and assets without touching a repository at all. Projects in the GitHub Copilot app give that work one home, with its context, agents, and results together. You start a project, describe what you want done, and add the context Copilot needs — repositories, design mocks, Slack threads, or notes from a design meeting. You choose the models and tools for the job, Copilot runs as many agents as the work needs in parallel managed sessions, and it brings back results, such as pull requests, for your review. Project automations cover repeatable tasks, such as creating a new promo video whenever a feature lands. For a focused task in a single repository, GitHub says to start a session directly from that repository instead. Projects are in public preview and subject to change, according to the projects documentation.

One thing the announcement and the documentation do not state: which plans include Projects, or how Projects usage is counted. Neither page says it. Before starting a project, check GitHub's plans page for your own plan, and check your account's usage view for how project sessions appear there. If Projects do not appear in your app, or a project session behaves differently from what this page describes, the terms for your account govern — do not assume a project is included, and do not start a large multi-repo run until you have seen the check for yourself.

Before you start

Pick one piece of work with a single goal that genuinely spans repositories or mixes code with other material — a feature across three repos, or an investigation across customer feedback and a specification. A single-repo task does not need a project. Gather the material before you create anything: the repositories involved, the design document or specification, and any feedback or notes the agent must use. Decide the result you want and the constraints that bind it, in writing, before the first prompt. A project with a vague goal and every repository attached will produce parallel sessions pulling in opposite directions.

Steps

  1. Create the project with one focused goal. In the sidebar of the GitHub Copilot app, next to Projects, open the new-project page. Give the project a focused goal so related tasks and results stay together. You can start a project without adding a repository, for work that needs no code at all.
  2. Attach only the repositories and material the goal needs. Under the repositories question, select the repositories the project should use, or search by owner and name. Add supporting material through the Library tab: files or folders that the agent should draw on, such as the specification and the feedback document. Keep the Library relevant to the goal, and tell Copilot which sources to use when you assign a task. Material from other projects does not belong in this one.
  3. State the goal, the result, and the constraints in the first prompt. Describe what you want the project for and the initial tasks, including the results you want and any constraints — for example, to use only the provided feedback, and to make no code changes, for an investigation. Copilot coordinates the work toward the goal; follow overall progress in the project rather than directing each session separately.
  4. Review from the Overview, and answer what needs input. The Overview tab groups the project's work by status: Needs input, for decisions, reviews, and permission requests that need your attention; Open, for work with an open pull request, showing the session status and lines added and deleted; Working, for sessions currently working; and Done, for completed work. Review the Needs input items first. To inspect one session, open it from the Overview: review the conversation, the changes, the pull request, and the plan, or steer it with a follow-up message. Review every pull request the project produces before merging, the same way you would review a colleague's.
  5. Set up recurring work deliberately, and check its schedule. To set up recurring work, ask Copilot in the project's conversation, describing the task, its schedule, and the expected result — for example, a summary every Monday of the feedback added to the Library that week, grouped by theme, using only the provided material. Then open the Automations tab and check the task's schedule and next run time. You can pause, edit, or delete a recurring task from that tab. A recurring task that reads the Library will read whatever has been added since the last run, so keep the Library current and remove material that no longer applies.

Computer use: a separate pilot, on a short leash

Computer use, in public preview on macOS and Windows, lets Copilot read app content, click controls, enter or edit text, and navigate across apps, including apps with no API, command-line interface, or MCP integration. It is useful for workflows in legacy and GUI-only software, according to the computer-use documentation. It is also the feature in this release that reaches outside the repository and the browser into arbitrary desktop software, so treat it as a different decision from Projects, not as part of the same first run.

Pilot it on a dedicated machine, or on a machine with nothing sensitive open, and keep the pilot to work with no irreversible result: reading and summarizing what an app shows, not submitting forms, sending messages, or changing values. To enable it, open the Copilot app settings, select Computer Use, and turn on Enable Computer Use; on macOS, grant both the Accessibility and Screen Recording permissions. Describe the outcome you want, the applications involved, and the constraints — for example, to summarize the status shown in an app's main window, and to change no values or submit no forms. Copilot asks for approval before controlling an app: check that the requested application and action match your prompt, then allow it for the current session only. Do not choose Always allow during a pilot. An Always allow approval is saved and applies to both the app and the CLI on the same computer, and removing it later does not revoke access already granted in a running session. Your organization can disable computer use through managed settings. To stop an operation, click Stop or press Esc, and end the session to revoke the access granted to it.

What can go wrong

Limits

Related playbooks

Sources

Back to: Small-team playbooks hub · Also: Onboard onto an unfamiliar codebase with an agent · Triage a backlog of issues with an agent · Run a reasoning task on a schedule with GitHub Agentic Workflows