> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md).

# Sonar Vortex analysis

## Overview

Sonar Vortex verifies your agent's code inside the [agentic loop](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/agentic-loop.md) of the [Agent Centric Development Cycle](/agent-centric-development-cycle/readme.md). It performs Sonar's trusted, deterministic analysis right inside your agent, reusing the context from a previous SonarQube Cloud CI analysis to deliver results in record times. This lets AI agents verify code changes with minimal latency while maintaining full CI analysis precision.

## How it works

During a CI analysis, SonarQube collects and stores your project's context: its dependencies, compiled artifacts, type information, and build configuration, tagged by project key and branch. This is why your project must be analyzed in your CI pipeline on a long-lived branch before you can use Vortex analysis.

When your agent analyzes a file, that context is restored on demand, so the analysis runs with the same inputs as a full CI scan without recomputing any of them.

## Making verification automatic

For most agents, the SonarQube plugin configures hooks, custom instructions, or both, so that Vortex analyzes the files your agent edits without you having to ask.

For details, see the installation instructions for your agent in [Installing Vortex](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides.md).

## Supported languages

Sonar Vortex analysis is available for the following languages:

* Java
* JavaScript
* TypeScript
* C#
* C
* C++
* Python
* Dart
* Swift
* Kotlin
* Go
* Objective-C
* PHP
* PowerShell
* Shell
* Ruby
* Apex
* SQL
* VB.NET
* CSS
* HTML
* Terraform
* Docker
* Kubernetes
* Groovy

Taint analysis (injection vulnerabilities detection) is also supported for Java, JavaScript, TypeScript, C# and VB.NET. Secrets detection is supported for all files.

> **Note:** If your Java project was analyzed using [Automatic analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/automatic-analysis/), only basic analysis results are returned.

## Setup

For step-by-step setup instructions, see [Installing Vortex](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides.md).

## Related pages

* [Sonar Vortex context](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-context.md)
* [MCP Server](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/)
* [Tools](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/reference/tools)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.