C++ code understandingDeveloping C++ code can be complex. C++ project structure, style, and convention can vary widely from repository to repository, and critical context for a given task often spans multiple files. This can require C++ developers to open and navigate across several files to fully understand a given project and author new code.The GitHub Copilot team has focused on two areas to improve the C++ developer experience for code completions: Upgrades to the underlying completions model to better understand C++ syntax and patterns across diverse codebases. Enhancing workspace awareness for C++ so that Copilot can provide more relevant completionsThese improvements are designed to help the autocomplete-style inline GitHub Copilot code completions be even more productive with C++ coding, minimizing manual intervention.Model updates for code completionsThe GitHub Copilot team has upgraded the base completions model to the new GPT-4o Copilot model. This model has additional training on over 275,000 high-quality public repositories in over 30 popular programming languages (including C++) and improved latency. This base model is available across Visual Studio and VS Code by default.Updates to workspace awareness for C++ code completionsAdditionally, with the latest improvements to GitHub Copilot code completions, Copilot can detect even more relevant context in C++ projects in order to provide more accurate code suggestions in VS Code for your specific codebase. This is now available in the latest 1.26.3 release of the C/C++ extension.To access these improvements, ensure you are on 1.322.0 or later of the Copilot extension and 1.26.3 or later of the C/C++ extension with IntelliSense configured.What's Next?We are committed to delivering similar improvements to Visual Studio 2022 17.14, so stay tuned for updates.Our team is working hard on improving C++ integrations with Copilot, so please let us know any other enhancements you’d like to see. Share your thoughts with us on Developer Community for Visual Studio or on GitHub for VS Code to help shape what’s next and how we can improve. You can also reach us via email at visualcpp@microsoft.com or via X at @VisualC.