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
+1, especially after the release of github/copilot-sdk. Open-sourcing it would provide better insight into the internal workings and help drive the development of Copilot forward.
Currently, the Copilot SDK for .NET (and other languages) requires a separate Copilot CLI executable to be installed and run as a server process. This approach feels like a distribution/wrapper, as every SDK user has to manage and maintain a separate executable binary or install cli manually. This adds installation friction and increases system complexity if you want to extend and build some functionality on top.
It would be a significant improvement to offer a single statically linked library instead of github copilot cli executable, directly embedding all CLI functionality. This would:
Eliminate the need to download/install/call out to external binaries or use jsonRPC server layer.
Make integration cleaner for .NET apps by providing a GitHub Copilot NuGet package. This would mean just interop calls with the library using [LibraryImport].
The Copilot SDK readme claims "Agents for every app." However, the following use cases contradict this:
How to produce a real-world consumer Windows application with GitHub Copilot SDK if the user needs to be installed copilot cli as a dependency?
How to ship the server api with GitHub Copilot SDK if the user needs to be installed copilot cli executable as a dependency?
How to ship the client-side Blazor app with GitHub Copilot SDK if the user needs to be installed copilot cli executable as a dependency?
Unfortunately, GitHub Copilot CLI is not open-sourced, so we don't know if they can provide a clean, statically linked library.
Activity
nathfavour commentedon Sep 29, 2025
+1
divinity76 commentedon Dec 18, 2025
Btw OpenAI Codex CLI is an excellent open-source alternative to the closed-source GitHub CoPilot CLI: https://github.com/openai/codex
nblog commentedon Jan 27, 2026
+1, especially after the release of github/copilot-sdk. Open-sourcing it would provide better insight into the internal workings and help drive the development of Copilot forward.
martasp commentedon Jan 28, 2026
Currently, the Copilot SDK for .NET (and other languages) requires a separate Copilot CLI executable to be installed and run as a server process. This approach feels like a distribution/wrapper, as every SDK user has to manage and maintain a separate executable binary or install cli manually. This adds installation friction and increases system complexity if you want to extend and build some functionality on top.
It would be a significant improvement to offer a single statically linked library instead of github copilot cli executable, directly embedding all CLI functionality. This would:
Eliminate the need to download/install/call out to external binaries or use jsonRPC server layer.
Make integration cleaner for .NET apps by providing a GitHub Copilot NuGet package. This would mean just interop calls with the library using [LibraryImport].
The Copilot SDK readme claims "Agents for every app." However, the following use cases contradict this:
How to produce a real-world consumer Windows application with GitHub Copilot SDK if the user needs to be installed copilot cli as a dependency?
How to ship the server api with GitHub Copilot SDK if the user needs to be installed copilot cli executable as a dependency?
How to ship the client-side Blazor app with GitHub Copilot SDK if the user needs to be installed copilot cli executable as a dependency?
Unfortunately, GitHub Copilot CLI is not open-sourced, so we don't know if they can provide a clean, statically linked library.
github/copilot-sdk#248 (comment)