Developer Tools
Cortex for Visual Studio
Use Cortex with a Visual Studio solution under your organization's policy.
Cortex for Visual Studio brings coding conversations and security scans into the solution workflow. The Cortex tool window provides an assistant alongside the editor, with results that connect security issues to the affected code.
Get started
Section titled “Get started”Install the signed Cortex extension using the button above or your approved source, restart Visual Studio, and open a solution. Open the Cortex tool window and sign in with your organization account.
Product capabilities
Section titled “Product capabilities”Coding conversations support questions, explanations and follow-up work. Separate chat sessions help organize topics. The Tools menu includes commands to open Cortex, sign in or out, scan the active file and open the Pervaziv dashboard.
Security scans expose findings in a results panel. Selecting a finding connects it to its location in the editor, and supported AI fix suggestions open a diff for review before application. This keeps investigation and remediation close to the current solution.
Project reporting
Section titled “Project reporting”The dashboard entry point opens the wider Pervaziv reporting experience for historical scan data and project analysis. DevSecOps documents those product areas, while Account & Billing manages the shared account and plan.
Work alongside the solution
Section titled “Work alongside the solution”Use the tool window for questions that benefit from remaining near the editor: explain an unfamiliar section, discuss a defect, review a security concern or ask how a proposed fix affects the current code. Separate sessions preserve different lines of investigation without mixing every question into one thread.
An active-file scan provides a concrete starting point for remediation. Navigate from a finding to the affected location, inspect the suggested change in a diff and run the checks appropriate to the solution. A suggestion that looks reasonable still needs validation against the intended behavior.
Editor feedback and broader reporting
Section titled “Editor feedback and broader reporting”The editor experience keeps the immediate code investigation close to the developer. The dashboard supplies project-level and historical reporting. Use those views together when a local finding needs dependency, posture or revision context beyond the active file.
The Visual Studio extension has its own published commands and compatibility requirements. Cortex’s wider platform includes connected workflows and other clients, but do not assume that a VS Code command or browser control exists in the Visual Studio tool window.
Product background
Section titled “Product background”Availability and support
Section titled “Availability and support”Use the commands and features exposed by the installed Visual Studio extension. The VS Code client has its own command reference and may provide additional interfaces.
If the extension does not activate, verify the supported Visual Studio version, enable it in Manage Extensions, and sign out and in again before contacting support with the sanitized extension version and request ID.