What is GitHub Copilot in Glueprint?
GitHub Copilot CLI is a terminal agent from GitHub that takes development work from issue planning through pull request creation. Installed via npm (@github/copilot), Homebrew, or WinGet and authenticated with GitHub credentials, it uses native MCP to search issues and analyze labels without context-switching. Users switch between Anthropic, Google, and OpenAI models with /model, and can run /plan, /delegate, and /fleet for parallel subagents. It is included across all Copilot tiers, drawing on plan AI Credits, and inherits an organization's Copilot policies and branch protections.
GitHub's AI pair programmer.
GitHub Copilot connects over the open Agent Client Protocol. One generic adapter implements the protocol's client side, so GitHub Copilot gets the same surfaces as every other harness.
Everything below works with the GitHub Copilot CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.
Set up GitHub Copilot on a host.
Installation is host-specific: repeat these steps anywhere this agent should execute. Portal and mobile can control the session afterward, but the process remains on that host.
Open the ACP catalog
On each execution host, open Settings -> Agents -> Browse ACP catalog and choose GitHub Copilot.
Install and initialize
Glueprint installs the registry distribution for GitHub Copilot, starts it, and completes the ACP initialize handshake.
Start a project session
Choose GitHub Copilot from a project or worktree and use the capabilities reported by that installed build.
How the connection works.
Glueprint adds orchestration and shared surfaces without taking ownership of the coding agent or its provider account.
Glueprint finds the GitHub Copilot binary you installed and spawns it, then speaks the Agent Client Protocol — JSON-RPC 2.0 over stdio — to drive it. Same CLI, same authentication; Glueprint just wraps the session.
Message chunks, tool calls, and tool-call updates from GitHub Copilot arrive as protocol notifications and render as the same live, typed timeline every Glueprint session gets — watchable from desktop, browser, or phone.
When GitHub Copilot asks to write a file or run a command, the protocol's permission request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow per tool.
Because GitHub Copilot speaks ACP, adding it is a catalog entry, not an engineering project — the same adapter runs every other agent in the registry, so you can tile them side by side.
Capabilities and discovery.
The status labels separate guaranteed integration behavior from features owned or announced by the installed agent.
| Capability | Status | Behavior |
|---|---|---|
| Native MCP access to GitHub issues and labels | Runtime | Confirmed when the installed agent connects. |
| Switches across Anthropic, Google, OpenAI models | Runtime | Confirmed when the installed agent connects. |
| /plan, /delegate, and /fleet parallel subagents | Runtime | Confirmed when the installed agent connects. |
| Inherits org policies and branch protections | Runtime | Confirmed when the installed agent connects. |
| Included in all Copilot subscription tiers | Runtime | Confirmed when the installed agent connects. |
Authentication, ownership, and limits.
Glueprint is the environment around the agent. Credentials, model access, and vendor-specific behavior stay where their owner designed them.
Watch every GitHub Copilot prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.
Run several GitHub Copilot sessions side by side, each in its own git worktree, with diffs, history, and a three-pane conflict resolver alongside.
Tile GitHub Copilot next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Promote it to an assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake.
Wake it on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.
Messages, sessions, and output tokens computed from session logs — compare GitHub Copilot against Claude Code, Codex, and your other ACP agents.
Remote viewing rides AES-256-GCM envelope encryption. The relay routes; it cannot read.
Common questions
Can I run GitHub Copilot with Glueprint?
Yes. GitHub Copilot is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the GitHub Copilot CLI you already installed and drives it over JSON-RPC 2.0 — adding live sessions, inline approvals, worktrees, and remote control.
Do I need a separate GitHub Copilot subscription or API key?
No. Glueprint doesn't resell model access. GitHub Copilot authenticates exactly the way its vendor designed — its own login, subscription, or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.
Can I run GitHub Copilot from my phone?
Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams GitHub Copilot sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run GitHub Copilot next to Claude Code and Codex?
Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics.
Is my session content private?
Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.