Streamline C++ Code Intelligence Setup in Copilot CLI
Senior Product Manager
C++ developers can now bring IDE-style semantic intelligence into Copilot CLI with less setup. The C++ language server plugin supports richer code navigation, diagnostics, symbol understanding, and code changes by using the same build context your compiler does.
That build context usually comes from a `compile_commands.json` file, which tells the language server how each source file is compiled. Instead of manually wiring that file together, the C++ language server plugin now provides a setup LSP skill that can help generate or refresh compile commands for common project types, including CMake and MSBuild. For custom build systems, teams can still provide their own` compile_commands.json` file or create a project-specific skill that captures their build setup once and makes it repeatable.
To get started with the C++ language server for Copilot CLI, please download via the Copilot Plugins marketplace and follow the Quick Start guide in the repo to accept EULA and configure` compile_commands.json`:
/plugin install cpp-language-server@copilot-plugins
Whether your project uses CMake, MSBuild, or a custom build pipeline, the goal is the same: make it easier for you to configure the C++ language server for Copilot CLI so Copilot can provide better navigation, diagnostics, explanations, and code changes, even when you’re outside the IDE.
As you try out the Microsoft C++ language server across different project types and build environments, we’d love to hear about your experiences. Let us know your thoughts through our survey: [\[Fill out form\]](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR3y0EFonU1lFoDzxL3GpYptUNDg0MzRWVkUyU0wxOU5BNEZXTkdFTFA3NC4u)
Configuring the language server
The language server needs a `compile_commands.json` file to understand your project. If you do not already have one generated via your build, you can utilize the skill to generate this for you.
To generate compile commands, type “regenerate compile commands” or “load project” in Copilot CLI, based on your desired configuration and platform (if necessary).
[](https://devblogs.microsoft.com/cppblog/wp-content/uploads/sites/9/2026/06/Video-Project-37-1.gif)
See “Recommended configuration path by project type” section below for suggestions based on your project build configuration.
Note: If your configuration changes, the skill should be re-invoked to regenerate your `compile_commands.json` to keep the LSP server in sync. The LSP server will automatically watch for changes to the `compile_commands.json` file.
Recommended configuration path by project type
#### CMake projects
For CMake-based projects, if you don’t have a `compile_commands.json` already generated from your CMake builds. the recommended path is to use the skill to onboard the project to generate `compile_commands.json`. You can also generate a `compile_commands.json` by passing `-DCMAKE_EXPORT_COMPILE_COMMANDS` set to “`TRUE`” when configuring CMake.
CMake has native support for compile command generation and the skill can help configure the project, so the language server has the compilation database it needs.
#### MSBuild projects
For MSBuild-based projects, users have two options.
For teams that want a guided setup, the skill can still help onboard the project by producing the configuration needed for the language server.
However, if you’d like to generate your own compile commands, you can refer to this sample application for an example of how to generate compile\_commands.json from MSBuild projects. While the sample application is designed to work out-of-the-box for many projects, it may require adaptation for complex projects.
#### Custom build systems
Custom builds often use hermetic, vendored, or wrapper-based toolchains that standard discovery cannot always detect.
For teams with custom toolchains, a project-specific skill can capture the setup once and make it repeatable. The detailed guidance provided in the cpp-language-server repo covers when custom configuration is needed, what settings to pin, and how to structure a skill so Copilot can regenerate compile commands reliably. It is especially useful for repositories where the default extractor produces incomplete output, picks up the wrong toolchain, or needs to run through a repo-provided build environment.
Getting started with the Microsoft C++ language server
The Microsoft C++ language server is available as a Copilot CLI plugin and runs on Windows, Linux, and macOS. An active GitHub Copilot subscription is required.
To get started, install the C++ language server plugin from the Copilot Plugins marketplace and follow the Quick Start guide:
/plugin install cpp-language-server@copilot-plugins
The Microsoft C++ language server requires a small amount of setup so it can understand your project the same way your compiler does:
1. Authenticate with GitHub Copilot CLI 2. Provide or generate a `compile_commands.json` file for your project
Share your feedback
Let us know your feedback and if there’s anything else you’d like to see. Help us improve the Microsoft C++ server for Copilot CLI by filling out this short survey: [\[Fill out form\]](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR3y0EFonU1lFoDzxL3GpYptUNDg0MzRWVkUyU0wxOU5BNEZXTkdFTFA3NC4u).
To report a problem or suggest an improvement, open an issue in our GitHub repo.
Category
- C++
- ```bash huggingface.co/Qapdex/SLM-ATP-Hybrid-Projector ```
- Model: /models/quantized_q4km.gguf Prompt: Hallo Max new tokens: 256 Warmups: 2, Runs: 10, Threads: 2, n_ctx: 512 -ogs: /home/bitnet_benchmark_logs Measuring cold load + first token. Cold run time: 0.103463 s Warmup runs (2)... Warmup 1: 0.110238s Warmup 2: 0.336900s Timed runs (10)... 0.108162 Run 1: 0.108162s 0.110827 Run 2: 0.110827s 0.110450 Run 3: 0.110450s 0.106787 Run 4: 0.106787s 0.129034 Run 5: 0.129034s 0.125900 Run 6: 0.125900s 0.131224 Run 7: 0.131224s 0.132762 Run 8: 0.132762s 0.114159 Run 9: O.114159s 0. 121013 Run 10: O.121013s Summary Runs: 10 Median time per run: 0.1176 s Mean time per run: 0.1190 s Min: 0.1068 s Max: 0.1328 s Tokens generated per run: 256 Tokens per second (median): 2177.13 Tokens per second (mean): 2150.69
- [](https://devblogs.microsoft.com/cppblog/feed/ "RSS Feed")
Share
Author
Senior Product Manager
C++ Product Manager working on Copilot, CMake, and Linux experiences in Visual Studio and VS Code
2 comments
Join the discussion.
Leave a commentCancel reply
Sort by :
Newest
Newest Popular Oldest
Read next
June 16, 2026
Boosting Adobe Photoshop’s Performance with MSVC and SPGO
Eric Brumer
June 25, 2026
Save the Date: Pure Virtual C++ 2026
Marian Luparu
Stay informed
Get notified when new posts are published.
Email \*
Country/Region \*
I would like to receive the C++ Team Blog Newsletter. Privacy Statement.
Subscribe
Follow this blog