Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[.NET] CreateProcess fails when Copilot CLI is installed via npm (copilot.cmd)

Open
#866 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp, node.js
Domain
devtools

Research direction

Start with StartCliServerAsync and the existing ResolveCliCommand entry point described in the issue, then reproduce the failure on Windows with a globally npm-installed Copilot CLI. Compare the .NET process launch behavior with the Python SDK fix and verify that the SDK can start the copilot.cmd installation while preserving the existing .js handling.

Written by the indexing model from the issue text.

Description

Problem

On Windows, when the Copilot CLI is installed via npm, the only executables on PATH are copilot (extensionless) and copilot.cmd. There is no copilot.exe.

The .NET SDK's StartCliServerAsync uses ProcessStartInfo with UseShellExecute = false, which calls CreateProcess under the hood. CreateProcess cannot resolve .cmd/.bat files — it only finds native executables (.exe, .com). This results in:

System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'copilot'
with working directory '...'. The system cannot find the file specified.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at GitHub.Copilot.SDK.CopilotClient.StartCliServerAsync(...)

Running copilot in a terminal works fine because PowerShell/cmd.exe use PATHEXT to resolve .cmd wrappers. But the SDK's CreateProcess does not.

Output of where.exe copilot on affected machines:

C:\ProgramData\global-npm\copilot
C:\ProgramData\global-npm\copilot.cmd

This was already fixed in the Python SDK

PR #338 fixed the same issue for the Python SDK by using shutil.which() to resolve the full CLI path before spawning the subprocess.

Suggested fix for .NET

The SDK already has ResolveCliCommand which handles .js files by prepending node:

private static (string FileName, IEnumerable<string> Args) ResolveCliCommand(string cliPath, IEnumerable<string> args)
{
    if (cliPath.EndsWith(".js", StringComparison.OrdinalIgnoreCase))
    {
        return ("node", new[] { cliPath }.Concat(args));
    }
    return (cliPath, args);
}

A similar approach for .cmd files (prepending cmd.exe /c) would work. Alternatively, resolve the PATH using PATHEXT-aware logic before passing to ProcessStartInfo.

Environment

  • SDK: GitHub.Copilot.SDK 0.1.32 (NuGet)
  • OS: Windows 11
  • CLI install method: npm (global)
Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 9h
Merged PRs (30d)
131

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.