GitHub Copilot
Harriet provisions your organization's skills and connectors into GitHub Copilot — both the VS Code extension and the copilot command-line tool, which keep separate configuration files.
How it works
Skills land in Copilot's personal skills folder. CLI connectors are provisioned by default. To also provision the VS Code extension, turn on Provision VS Code connectors in the provider settings.
Copilot is additive — it sits alongside whichever other surface you have chosen.
Set it up
- Enable the target. Turn on GitHub Copilot in Settings.
- Install the Harriet Endpoint agent on each machine and sign in.
- Reload VS Code once the device has checked in.
If a surface is not installed on a machine, Harriet skips its configuration rather than creating directories the app does not own.
If your team uses VS Code Settings Sync, be aware that it replicates the user-level connector configuration across every machine signed into the same account — including machines Harriet does not manage. Because connector entries contain a per-device credential, the VS Code option is off by default and requires an explicit administrator opt-in. Neither Cursor nor Cline is affected: their configuration is not synced.
Harriet preserves comments, trailing commas and input definitions when updating VS Code configuration. Your own connectors are also preserved when user customization is allowed. If the file is invalid, sync reports an error and leaves it unchanged.
Two things to know
- Default VS Code profile. Connectors are written to your Default profile. If you work in a custom profile, copy the server block across — VS Code stores custom profiles separately.
- No Harriet gateway option. Copilot supplies its own models. Its bring-your-own-key support is per provider and does not accept an arbitrary endpoint, so unlike Cursor, Cline and Codex there is nothing to connect here.