Quick Answer: The GitHub Copilot app is an agent-native desktop app for finding, running, steering, and landing software work across your GitHub repositories. Local sessions run in isolated git worktrees, cloud sessions run in GitHub-hosted environments, and any Copilot plan works, or you can bring your own key. Verify the download source before you install it.
The GitHub Copilot app tries to collapse a familiar mess: a terminal, an editor, a dozen browser tabs, and the GitHub website, all open just to ship one pull request. The README describes it as a single control center for that whole loop. Before you install anything, though, the repository has a problem you need to see first. We'll get to it.
What the app covers, from idea to pull request
The app handles four jobs. It helps you find work, runs agents on that work, lets you steer them while they run, and carries the result through to merge. That's a wider scope than most coding assistants, which stop once the code is written.
The README points to three features that do the heavy lifting:
- Canvases show plans, terminals, browser previews, diffs, and workflow state in one place, so you can see what an agent is doing instead of scrolling a chat thread.
- My Work pulls sessions, issues, pull requests, and repository context into one list so you can decide what needs attention next.
- Automations turn repeatable prompts into scheduled or background tasks.
Here's the part most AI tooling overlooks. The README admits that much of a developer's time goes to work that isn't writing code: triage, reviews, checks, and merges. The app is aimed at that overhead, not just at generation.
Why each session gets its own git worktree
This is the design choice that matters most for anyone running more than one agent. The README says each local session runs in its own isolated git worktree. A worktree is a second checkout of the same repository, with its own working directory and its own branch, sharing the same history.
Here's why that matters. Suppose you ask one agent to fix a bug and another to implement an issue in the same checkout. Both write to the same files at the same time, and one agent's half-finished edit quietly overwrites the other's. The failure is hard to spot because nothing errors out. You just get a broken build later.
Separate worktrees prevent that collision. Each agent edits its own copy of the files, so the bug fix and the feature can progress side by side. The README says this is what lets you have Copilot investigate bugs, implement issues, and address review feedback in parallel "without branches or files colliding."
Most guides stop there, and that's where the nuance begins. Worktrees stop file-level collisions, not merge conflicts. When you bring two branches together, they can still conflict on the same lines. Isolation buys you parallel work, but integration remains your job.
- Give each task a clear, narrow scope before you start the session.
- Keep sessions that touch the same module apart, or run them in sequence.
- Review each branch's diff on its own before merging anything.
Local sessions versus cloud sessions
The README describes two session types. They solve different problems, so pick based on where you need the work to happen.
| Session type | Where it runs | Isolation | Access |
|---|---|---|---|
| Local | Your machine, through the desktop app | Dedicated git worktree per session | Only where the app is running |
| Cloud | Isolated GitHub-hosted environment | Separate hosted environment per session | Pick it up from anywhere, per the README |
| Both | Parallel with other sessions | No shared files between sessions | Depends on session type |
Use local sessions when you need your own toolchain, local services, or quick iteration on your machine. Use cloud sessions when you want an agent to keep working after you close your laptop, or when you want to check progress from another device. The trade-off is that cloud work depends on GitHub's hosted environment, while local work depends on your machine staying available.
Agent Merge and the work around the code
The README's most ambitious claim is that Agent Merge helps carry pull requests through review, checks, and merge conditions. The stated goal is to keep you focused on judgment, quality, and delivery rather than on clicking through a checklist.
Two cautions. First, the README doesn't document the exact merge policies or permissions the feature needs, so read the current docs before you grant it anything in a repository that matters. Second, automation that approves and merges is only as safe as the branch protection rules behind it. If your repo doesn't require reviews and passing checks, a merge helper can move faster than your safeguards. Check your branch protection settings first.
Plans, bring-your-own-key, and cost
The README says any GitHub Copilot plan works, including Copilot Free and Student plans. If you don't have a Copilot subscription, you can still use the app with bring your own key (BYOK) and your own model provider.
The trade-off with BYOK is billing. With a Copilot plan, usage sits inside your subscription. With your own key, you pay the model provider directly, and heavy agent sessions can run up token costs quickly. Set a spending limit with your provider before you start running parallel sessions. That single step prevents most surprise bills.
Read this before you install
Here's where most guides go wrong: they tell you to click the download badge and move on. Don't do that here.
The README's download button points to a .rar archive on Dropbox, not to a GitHub Releases asset. The badge text reads "GET — Manus," which doesn't match the product name. The README also says you can "browse all builds" on the Releases page, but that link is relative, so it resolves to whichever repository you're viewing. In this case, that's a personal account, not the GitHub organization.
These details don't prove the file is malicious. They do mean you shouldn't trust it yet. Here's a safer path:
- Confirm the repository owner. The README's issue tracker links to
github.com/github/app, so start there. - Download only from that organization's Releases page, and check whether signed builds or published checksums exist.
- If you can't verify the source, don't run the binary on your primary machine. Use a virtual machine or a spare device for the first run.
- Use a read-only or limited-scope GitHub token for initial testing, not one with broad write access.
The counterintuitive point: a "Download" button is the least trustworthy thing on a repo page. Verification comes before convenience.
Data, telemetry, and what you're sharing
The README says that if you use the app with your Copilot account, GitHub may collect usage data such as code acceptance or rejection, associated conversation data, and feedback you submit through the feedback dialog. It points to the GitHub Copilot Trust Center for details, and that's the page to read before you assume how your data is handled.
Feedback reports carry their own risk. The README warns that logs from /collect-debug-logs may contain sensitive information. Review the output and remove tokens, paths, or proprietary code before you attach anything to an issue.
Frequently Asked Questions
What is the GitHub Copilot app?
The GitHub Copilot app is a desktop application for managing software work from idea to pull request. It groups finding issues, running agents, reviewing progress, and merging changes into one interface. According to the README, it works across your GitHub repositories and runs local sessions in isolated git worktrees or cloud sessions in GitHub-hosted environments.
How do I install the GitHub Copilot app safely?
Download it only from the official github/app organization's Releases page, not from a Dropbox link or a personal repository. Check for published checksums or signatures, and test unverified builds in a virtual machine first. Use a limited-scope GitHub token until you've confirmed what the app can access.
Why does each agent session need its own git worktree?
Two agents editing the same checkout can overwrite each other's files without any error. A separate worktree gives each session its own working directory and branch while sharing history. This prevents file-level collisions, but you still need to resolve merge conflicts when you combine branches.
Can I use the GitHub Copilot app without a Copilot subscription?
Yes. The README says you can bring your own key and use your own model provider. Be aware that you'll pay the provider directly for usage, so set a spending limit before running multiple agent sessions in parallel.
Start with one low-risk session
Your most useful takeaway is this: verify the source first, then run one isolated session on a non-critical issue and review its branch before anything merges. If you're evaluating the GitHub Copilot app, try it this week on a repo where a bad merge is cheap to undo, and note whether the worktree isolation actually saved you time. Pass this to anyone on your team who's about to install a desktop agent from a download link they found in a README.