Execution harness · your own GitHub Copilot login
Run your chats on GitHub Copilot
Pick GitHub Copilot as the harness in any thread and the round runs on the Copilot CLI under your GitHub account — the mesh tools, nodes and context you already have, driven by a different engine.
What installing does
Getting the plugin gives you access to it, and your harness picker offers the harness from the package — nothing is copied into your home (installations that still copy apps place it at {you}/Harness/Copilot).
It never appears for users who haven't opted in, because it needs a personal GitHub Copilot
login: there is no shared key and nothing is billed to the mesh.
- Get the plugin — the harness appears in your thread's harness picker.
- Pick it in a thread, then run
/loginto connect your GitHub account. - Chat as usual — same threads, same tools, same mesh content.
Uninstalling removes only a legacy home copy; it does not revoke your access, so the picker keeps offering the harness. Switch a thread to another harness to stop using it — no history is lost.
Good to know
- The harness runtime is this package's
MeshWeaver.AI.Copilotmodule, which the deployment must load, with the Copilot CLI installed beside the portal; theFeatures:Ai:Clis:Copilotflag alone does not load the module. Getting the package is your personal picker opt-in. - It is a harness, not an agent: it changes what executes the round, not which agent you talk to.
- Nothing is shared. Your account, your login, your picker.