> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/c++-agent/c++-agent-for-windows-beta.md).

# C++ Agent for Windows (Beta)

{% hint style="warning" %}
The Windows / MSVC C++ agent is in beta. CLI flags and APIs may change between versions.
{% endhint %}

The MSVC agent instruments Visual Studio and MSVC builds for SeaLights code coverage and Test Impact Analysis. It injects instrumentation through MSBuild targets without modifying `.vcxproj` files. The self-contained `SL.Agent.Cpp.exe` runs without a .NET runtime.

This agent differs from the Linux/GCC agent. The Linux/GCC agent uses compiler flags and `LD_PRELOAD`.

### Prerequisites

Confirm your environment meets these requirements before you begin:

* Windows 10 or Windows Server 2016 or later
* Visual Studio 2017 or later with toolset v141 or later, MSVC, and MSBuild on `PATH`
* Google Test v1.10 or later for test event capture and Test Impact Analysis. Earlier versions collect coverage data only.
* No .NET runtime installation. The agent runs as a self-contained `.exe`.

### Workflow overview

1. Download the agent
2. Inject MSBuild targets and rebuild
3. Run your tests with coverage
   * Capture test events
4. Parameter reference


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/c++-agent/c++-agent-for-windows-beta.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.