Skip to content

add support for Windows platform in Copilot CLI path resolution#1

Closed
YoavLax wants to merge 1 commit intomicrosoft:mainfrom
YoavLax:windows-support
Closed

add support for Windows platform in Copilot CLI path resolution#1
YoavLax wants to merge 1 commit intomicrosoft:mainfrom
YoavLax:windows-support

Conversation

@YoavLax
Copy link
Copy Markdown

@YoavLax YoavLax commented Jan 29, 2026

Add Windows support for Copilot CLI detection

Problem

The Copilot CLI detection logic only worked on Unix/macOS systems. Windows users would get "Copilot CLI not found" errors even with Copilot installed.

Solution

Added Windows support by returning "copilot" on Windows platforms and letting the Copilot SDK resolve it from PATH. This matches the pattern used in other working implementations.

Changes:

  • src/services/instructions.ts: Added Windows check in findCopilotCliPath()
  • src/services/evaluator.ts: Added Windows check in findCopilotCliPath()

Implementation

if (process.platform === "win32") {
  return "copilot";
}

@0902cs231028-sys
Copy link
Copy Markdown

Sure buddy I'm having my end sem examination, I would be free within 3-4 days to get back on project ,I'm quite happy about that people trying to use and test it, I'm sorry that it was limited to only my college id as i didn't thought others would bother using it but happy to be proven wrong.

digitarald added a commit that referenced this pull request Feb 24, 2026
@digitarald
Copy link
Copy Markdown
Collaborator

Hey @YoavLax — thanks for flagging this and for the contribution! 🙏

We've since landed comprehensive Windows support in main as part of the vnext consolidation (PR #15). The current implementation in src/services/copilot.ts goes beyond returning "copilot" and includes:

  • Platform-aware CLI discovery using where on Windows
  • The node + npm-loader.js approach to bypass .cmd/.bat shim issues
  • CopilotCliConfig with cliArgs support for flexible spawning
  • Windows-specific VS Code extension path resolution

Since this is fully covered now, I'm closing this PR. Really appreciate you surfacing the issue early — it helped inform the direction we took!

@digitarald digitarald closed this Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants