Let your coding agent guide the setup.

Help me set up covdbg for C++ coverage on Windows. Work with me one step at a time, explain what each step does, and check the result before continuing. Inspect the current workspace before proposing changes. Preserve existing files and ask only for information you cannot determine.

Start with https://covdbg.com/llms.txt and follow the current documentation links. Prefer the plain Markdown versions of guides. If you cannot access a reference, tell me rather than guessing commands or configuration keys. Do not request passwords, sign-in codes, or tokens in chat, and never put credentials in committed files.

Read https://covdbg.com/docs/getting-started/installation.md, https://covdbg.com/docs/getting-started/quick-start.md, and https://covdbg.com/docs/reference/configuration.md.

Check whether covdbg is installed and whether this is a Windows x64 environment. Guide me through installation if needed. Find the project's build and test commands, executable, and matching PDB files. Help me sign in with covdbg login in my browser. Create or carefully update .covdbg.yaml using documented keys, including our source and excluding third-party code. Explain any baseline needed for code the test binary never links. Run a small test under coverage, confirm the test result separately, and help me inspect the coverage database. Finish with the exact repeatable command and a summary of changed files.

Help me set up covdbg for C++ coverage on Windows. Work with me one step at a time, explain what each step does, and check the result before continuing. Inspect the current workspace before proposing changes. Preserve existing files and ask only for information you cannot determine.

Start with https://covdbg.com/llms.txt and follow the current documentation links. Prefer the plain Markdown versions of guides. If you cannot access a reference, tell me rather than guessing commands or configuration keys. Do not request passwords, sign-in codes, or tokens in chat, and never put credentials in committed files.

Read https://covdbg.com/docs/reference/licensing-faq.md and https://covdbg.com/pricing/.

Check covdbg whoami and guide me through covdbg login if needed, pausing while I complete browser sign-in myself. Explain public repository access, the personal allowance of one private repository at a time with switching allowed at any time, and when team seats are needed. Check which git remote this workspace uses before the first run and explain the personal repository slot and how to switch it before selecting it. Do not purchase seats or change account settings for me. Old --demo and --fetch-license options are removed; help replace any such flags in my local scripts. Verify sign-in without displaying credential values.

Help me set up covdbg for C++ coverage on Windows. Work with me one step at a time, explain what each step does, and check the result before continuing. Inspect the current workspace before proposing changes. Preserve existing files and ask only for information you cannot determine.

Start with https://covdbg.com/llms.txt and follow the current documentation links. Prefer the plain Markdown versions of guides. If you cannot access a reference, tell me rather than guessing commands or configuration keys. Do not request passwords, sign-in codes, or tokens in chat, and never put credentials in committed files.

Read https://covdbg.com/docs/integrations/mcp.md and https://covdbg.com/docs/getting-started/installation.md.

Check that covdbg and Claude Code are installed, covdbg is on PATH, and the workspace runs locally on Windows with matching PDB files. Inspect existing MCP configuration and the installed Claude Code CLI help. Guide me through registering the stdio server with claude mcp add covdbg -- covdbg mcp, using the appropriate supported scope without overwriting other servers. Explain which configuration changes you propose. Help me finish covdbg login in my browser if needed. Verify the connection through Claude Code, call covdbg's guide tool, then discover project targets. Do not start a long coverage run until we have checked the target and configuration. Explain that source returned by MCP is processed according to my AI client's settings.

Help me set up covdbg for C++ coverage on Windows. Work with me one step at a time, explain what each step does, and check the result before continuing. Inspect the current workspace before proposing changes. Preserve existing files and ask only for information you cannot determine.

Start with https://covdbg.com/llms.txt and follow the current documentation links. Prefer the plain Markdown versions of guides. If you cannot access a reference, tell me rather than guessing commands or configuration keys. Do not request passwords, sign-in codes, or tokens in chat, and never put credentials in committed files.

Read https://covdbg.com/docs/integrations/mcp.md and https://covdbg.com/docs/reference/configuration.md.

Use the covdbg MCP guide before measuring. Review our filters and baseline so the report covers our own code. Discover and run the relevant test suite, wait for completion, then inspect files and uncovered source context. If the test executable only launches the program under test, read the guide's children topic before enabling follow_children on the run. Choose one uncovered error path and explain why a test would help. Add a focused test with meaningful assertions using your coding tools. Run tests and measure coverage again. Report test success separately from coverage success, the measured change, and remaining gaps. Avoid changing production behavior just to improve a percentage. Close coverage sessions when finished.

Help me set up covdbg for C++ coverage on Windows. Work with me one step at a time, explain what each step does, and check the result before continuing. Inspect the current workspace before proposing changes. Preserve existing files and ask only for information you cannot determine.

Start with https://covdbg.com/llms.txt and follow the current documentation links. Prefer the plain Markdown versions of guides. If you cannot access a reference, tell me rather than guessing commands or configuration keys. Do not request passwords, sign-in codes, or tokens in chat, and never put credentials in committed files.

Read https://covdbg.com/docs/integrations/github-actions.md, https://covdbg.com/docs/guides/html-reports.md, and https://covdbg.com/docs/reference/licensing-faq.md. For Codecov, also read https://covdbg.com/docs/integrations/codecov.md.

Inspect our existing CI workflow and reuse its Windows build and test steps. For GitHub Actions use the documented liasoft/setup-covdbg action version. Guide me through creating and storing COVDBG_PROJECT_TOKEN in the CI secret settings myself; never ask me to paste it here. Explain the applicable repository and seat requirements. Collect coverage, export HTML to an artifact folder, and optionally export LCOV for Codecov if the repository uses it. Use the matching checkout for HTML export and explain that reports contain source text. Keep the test failure status separate from coverage collection. Show the workflow changes and validate them locally where possible; tell me what still needs a CI run.