GitHub Copilot

GitHub Copilot CLI integration for GitHub-heavy teams using Conductor OSS.

Agent guide

GitHub Copilot is useful when a team already relies on GitHub-centric tooling and wants that CLI available as a native Conductor default for the repositories that need it.

Binary: github-copilotAliases: copilot, gh-copilotBest for GitHub-heavy teams

Primary binary

github-copilot

Known aliases

copilot, copilot-cli, gh-copilot

Good fit

GitHub-heavy teams, CLI parity, and built-in plugin coverage.

​

Set up GitHub Copilot in Conductor

1. Install the GitHub Copilot CLI

   # install github-copilot CLI in your environment
   
2. Authenticate with GitHub

   Complete the GitHub sign-in flow required by the CLI before selecting Copilot for a workspace.

3. Launch Conductor

   npx --yes --registry=https://registry.npmjs.org conductor-oss@latest
   

   Set GitHub Copilot as the default only for the repositories where that GitHub-centric workflow is the right fit.

4. Configure the project default

   projects:
     my-app:
       agent: github-copilot
   

​

Model selection in Conductor

GitHub Copilot model availability depends on your GitHub account entitlements, organization policy, and the Copilot CLI version installed locally.

• leave agentConfig.model unset when the Copilot CLI should keep using its default
• add an override only if your Copilot workflow exposes an explicit model switch and a repository needs that pinned
• keep Copilot defaults repo-specific instead of task-specific whenever possible

​

Why teams pick GitHub Copilot

• strong fit for GitHub-heavy delivery flows
• keeps the CLI inside one orchestrated board
• avoids a generic shell fallback for a supported runtime