Providers
GitHub Copilot
Configure GitHub Copilot in Happier, including local CLI login, auth detection, and machine-specific setup.
Happier can run GitHub Copilot CLI through the local copilot binary on your machine.
Requirements
- Copilot CLI installed locally
- binary available on
PATH(or configured through Happier’s CLI path settings)
Install Copilot
If you use hstack, you can install Copilot with the providers installer:
hstack providers install copilot
copilot --versionOr install manually:
npm install -g @github/copilot
copilot --versionLocal authentication in Happier
Happier shows Copilot’s machine-local auth state in:
- Settings → AI provider settings → GitHub Copilot
From there you can:
- check whether Copilot is authenticated on the selected machine
- open the native
copilot loginflow directly inside Happier - refresh the auth status with Check now
Happier currently detects Copilot auth from:
COPILOT_GITHUB_TOKENGH_TOKENGITHUB_TOKEN- the local GitHub CLI auth state when available
For the shared user guide, see Provider authentication.
Notes
- Copilot auth in Happier is machine-local. If you log in on one machine, another machine still needs its own local login.
- If you prefer token-based auth, Happier can detect that and show it as an environment-backed method.
Troubleshooting
If Copilot is not detected:
- Verify
copilot --versionworks. - Restart Happier.
- Re-open the provider settings page and use Check now.