Visual Studio Integration Guide

Overview

Visual Studio is critical for .NET and Windows enterprise development. Copilot Agent Mode can edit files, run commands, and use build context, so policy attribution and command/network visibility matter.

Support level

Native Integration

What Cup’n’String detects

• Visual Studio processes
• Solution/workspace context where available
• Copilot/agent mode activity where observable
• Build, test, and terminal child processes

What it governs

• Agentic provider traffic
• Local service access
• Windows credential and secret exposure
• Network calls from build/test workflows

Recommended policies

• Enable Copilot-aware policy profile
• Audit agent mode activity
• Block unknown AI endpoints
• Protect local secrets and signing materials

Setup outline

1. Confirm the Cup’n’String agent is running on Windows.
2. Launch Visual Studio; the Windows Filtering Platform (WFP) hooks the process tree automatically.
3. Configure solution-level access control profiles in Cup’n’String.

Verification

Trigger a build or run an agent command within Visual Studio, then review the cost metrics and policy decisions mapped to the solution ID in your dashboard.

Troubleshooting

If credential shielding warnings appear, check that build scripts are not hardcoding secrets in command-line arguments.

Known limitations

Native policy depth depends on extension/admin control integration points.