You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks. SkillSpector does not currently support Copilot as a provider, although we now support locally authenticated CLI providers. To help us scope this correctly, which Copilot surface are you looking to use: a Copilot CLI workflow, an editor-hosted Copilot session, or an API endpoint? The authentication and automation constraints differ, so that would help us assess the appropriate provider path.
The surface we would be looking for would be through the copilot-cli. That would allow us to run it locally and within a GitHub Actions-based pipeline since it also supports the copilot cli natively/
The requested Copilot CLI integration is now in progress in PR #572, which proposes a copilot_cli semantic-scan provider using the locally authenticated CLI. The PR is open for review and has not merged, so this issue remains open.
Activity
Spectorian commentedon Jul 17, 2026
Thanks. SkillSpector does not currently support Copilot as a provider, although we now support locally authenticated CLI providers. To help us scope this correctly, which Copilot surface are you looking to use: a Copilot CLI workflow, an editor-hosted Copilot session, or an API endpoint? The authentication and automation constraints differ, so that would help us assess the appropriate provider path.
jdesulme commentedon Sep 2, 2026
The surface we would be looking for would be through the copilot-cli. That would allow us to run it locally and within a GitHub Actions-based pipeline since it also supports the copilot cli natively/
rng1995 commentedon Sep 21, 2026
The requested Copilot CLI integration is now in progress in PR #572, which proposes a
copilot_clisemantic-scan provider using the locally authenticated CLI. The PR is open for review and has not merged, so this issue remains open.rng1995 commentedon Oct 4, 2026
PR-state snapshot checked on 2026-10-04:
Keeping this issue open: the relevant implementation is not merged. Check/review status is a point-in-time snapshot, not a claim of merge readiness.