Playbooks · Teams
Paperclip adds Copilot as a native harness
Written November 13, 2026
In Paperclip v2026.1106.0, GitHub Copilot runs as a native harness: token sign-in, models discovered from your account, Runner boundaries.
What changed
Paperclip's native providers are the agent runtimes that run through the Paperclip Runner under the same rules as the built-in ones. In v2026.1106.0, GitHub Copilot joins that list. The release carries 515 commits and was promoted from the 2026.1023.0 beta line. Its headline is the Runner becoming the default for new agents, a story covered in Paperclip: native Runner now default. This page covers only the Copilot cell of the release: what it takes to connect a Copilot account, and what boundaries the resulting agent runs under.
For a team that already pays for Copilot seats and runs Paperclip, the gap this closes is practical. Before this release, a Copilot subscription had no native seat at the Paperclip table; the providers with first-class Runner support were other vendors' agents. Now the same subscription can supply an agent that Paperclip assigns work to and watches like any other native provider.
How the connection works
The changelog gives the connection route in one sentence, and each part of it matters:
- Connect through Apps / AI Connections with a saved GitHub token. The credential is a GitHub token held in Paperclip's connections, not a separate Copilot sign-in flow inside each agent.
- The model list comes from the authenticated account. Paperclip discovers which models the connected account can use instead of presenting a fixed catalogue. What a given seat can run is therefore whatever that account is entitled to, and two agents on two accounts can legitimately see different lists.
- Copilot runs at CLI 1.0.88. The integration pins Copilot CLI 1.0.88 as the runtime underneath, so the behaviour comes from a named Copilot build rather than an unspecified latest.
The boundaries it runs under
The changelog's key claim is about sameness. Copilot runs through the Paperclip Runner with the same instruction, permission, and completion boundaries as the other native providers. In plain terms, a Copilot agent in Paperclip is not a side door around the controls a team has set for its other agents. The instructions it receives and the permissions it is granted come from the same Runner machinery, and its finished work is judged the same way too.
The release also includes the Linux provider manifest needed for Daytona sandboxes. That detail decides where Copilot can run: a provider without a sandbox manifest tends to work on a local machine and stop at the sandbox boundary. With the manifest in the release, Copilot agents can be placed in Daytona sandboxes on Linux like the other native providers.
What to do with it
- If your team runs Paperclip and holds Copilot seats, connect one account through Apps / AI Connections and look at the model list Paperclip discovers before assigning real work. The discovered list is the ground truth for that seat.
- Give the first Copilot agent the same instructions and permission posture you would give any new native provider. The release's promise is that the boundaries carry over; the first assignments are how a team learns whether its instruction files read as well to a new runtime.
- If your agents run in Daytona sandboxes, the Linux manifest is the line that makes Copilot eligible for those placements at all.
Limits
- The changelog describes the connection, the discovered model list, and the Runner boundaries. It does not promise a particular model for any given account; entitlement stays with the GitHub account you connect.
- The pinned runtime is Copilot CLI 1.0.88. Behaviour from later Copilot CLI releases is a different release's story.
- This is one cell of a large release. The Runner-default change, the removed Pipelines experiment, and the rest of v2026.1106.0 sit outside this page's scope.
Related playbooks
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
- Copilot Automations learn from real outcomes
- Copilot CLI signs in with Microsoft Entra
Sources
Back to: Teams playbooks hub · Also: Paperclip: native Runner now default