Playbooks · Coding tasks
Copilot CLI now configures MSBuild itself
Written November 11, 2026
Copilot CLI's C++ language server now generates compile_commands.json for MSBuild projects at startup — but the rollout looks gated. Carry both.
What changed
The Microsoft C++ Language Server for GitHub Copilot CLI now bundles its MSBuild compile commands extractor and invokes it automatically. An agent no longer needs to discover and run a separate configuration skill before it can get precise code intelligence for your project. Previously, setting up go-to-definition, find references, and other language server features for an MSBuild-based C++ project required you to either provide your own compile_commands.json file or have Copilot locate and run a configuration skill before it could generate a compilation database. That extra discovery step added setup time and consumed tokens before Copilot could start working with your code.
Now the extractor is bundled directly with the language server, so it is always available. Copilot invokes the extractor when starting the language server on project open, with no manual or agent-driven setup skill required. Compilation database generation for MSBuild projects is deterministic, which the changelog says reduces setup token usage. No figures for time saved or tokens saved are published anywhere, so treat those benefits as design intent, not measured results.
The rollout conflict
The sources disagree on whether the feature is actually on for you, and that disagreement is the story. The changelog presents the feature as available now, but the configuration page in Microsoft's repository carries a note that automatic MSBuild configuration is disabled by default, and says the feature is available only if an experiment is enabled for you through feature flagging. The npm package page says automatic MSBuild generation is available to some Windows x64 users and requires no opt-in. The two documents fit together if the rollout is staged: the feature is probably being exposed gradually to eligible Windows x64 users, and the repository note may simply be older than the npm page. That cannot be confirmed from the sources, so do not assume it will fire on your machine.
To check, launch Copilot CLI from the project directory and run /lsp show to see whether the "cpp" server is up, then run /lsp logs to see whether extraction is running or has failed. If nothing happens, you may not be in the rollout. Generate the file with the skill or the manual extractor instead.
What you need first
The automation covers only the compilation database. You still need the usual onboarding: an active GitHub Copilot subscription, a Copilot CLI build with session-directory support, npm, and the cpp-language-server plugin, installed with /plugin install cpp-language-server@copilot-plugins, plus acceptance of the license terms and a GitHub login. The language server is a preview, and the README says it was tested with prerelease 1.0.106-5.
Other build systems are unchanged. For CMake projects, use the generate compile commands skill by asking Copilot CLI to "load project". For custom build systems, supply your own compile_commands.json or follow the guide to create a custom build extractor skill.
The one concrete knob
The npm documentation gives the timeout setting as msbuild_extractor_timeout_seconds, with an example value of 180, set in %LOCALAPPDATA%\mscppls\state.json. If the extractor times out on a large solution, raise the timeout in that file and restart the server. An existing database without a recognised MSBuild extractor stamp is reused and never overwritten, so a hand-built or CMake-generated compile_commands.json is not clobbered.
Limits
- The rollout state is unresolved. The changelog says the feature is available now; the repository config page says it is disabled by default behind a feature flag. Both are carried here.
- No time or token savings are measured anywhere. Do not quote any.
- The language server is a preview and may change.
Related playbooks
- Copilot CLI 1.0.106: /code, /settings, GPT-6.1 Terra
- Copilot CLI 1.0.108: index, PDFs, Ctrl+C
- Copilot CLI 1.0.109: CIDR sandbox rules
- Copilot CLI 1.0.110: the November 12 build
Sources
- GitHub Changelog, C++ language server now auto-configures MSBuild builds — the bundled extractor and the automatic invocation.
- WindowsForum, Copilot CLI C++ Language Server Adds Automatic MSBuild Configuration, With Limited Rollout — the rollout conflict, the timeout setting, and the preview status.
Back to: Coding playbooks hub · Also: Copilot CLI 1.0.108: index, PDFs, Ctrl+C · VS Code 1.146 retires the Local harness · Copilot CLI 1.0.109: CIDR sandbox rules