> 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/sonarqube-server/10.5/user-guide/sonarlint-connected-mode.md).
# SonarQube for IDE Connected Mode
SonarQube for IDE Connected Mode connects SonarQube for IDE to your SonarQube Server 10.5 project and provides benefits that neither product gives you alone.
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.5 documentation. For a list of all 10.5 pages, see the [SonarQube Server 10.5 page index](https://3691828591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feu7dHWcqP9Cr3eUAzwWg%2Fuploads%2FjUvEoDEUUE0rAURT5wZJ%2Fsonarqube-server-10.5-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.5 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
SonarQube for IDE is your first line of defense in keeping your code clean. Connected Mode binds your SonarQube Server project to a local project so that SonarQube for IDE can catch issues immediately, right in the IDE, before you even commit them.
[SonarQube for IDE](https://www.sonarsource.com/products/sonarqube/ide/) is a free IDE extension that integrates with SonarQube Server using Connected Mode. Like a spell checker, SonarQube for IDE highlights issues as you type. When an issue is identified, SonarQube for IDE provides you with clear remediation guidance so you can fix it before the code is even committed. In many cases, it also provides a *quick fix* that can automatically fix the issue for you.
{% tabs %}
{% tab title="INTELLIJ" %}
SonarQube for IDE integrates with most JetBrains IDEs including IntelliJ IDEA, CLion, GoLand, WebStorm, PHPStorm, PyCharm, Rider, Android Studio & RubyMine.
* [Feature overview](https://www.sonarsource.com/products/sonarqube/ide/features/jetbrains/)
* [Installation](/sonarqube-for-intellij/getting-started/installation.md) instructions
* Supported [Rules and languages](/sonarqube-for-intellij/using/rules.md)
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-intellij/connect-your-ide/setup) and list of [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-intellij/connect-your-ide/connected-mode) benefits.
* [Download](https://plugins.jetbrains.com/plugin/7973-sonarlint)
{% endtab %}
{% tab title="VISUAL STUDIO" %}
SonarQube for IDE provides Visual Studio developers with a comprehensive in-IDE solution for improving the quality and security of the code they deliver.
* [Feature overview](https://www.sonarsource.com/products/sonarqube/ide/features/visual-studio/)
* [Installation](/sonarqube-for-visual-studio/getting-started/installation.md) instructions
* Supported [Rules and languages](/sonarqube-for-visual-studio/using/rules.md)
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-visual-studio/connect-your-ide/setup) and list of [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-visual-studio/connect-your-ide/connected-mode) benefits.
* Download for [Visual Studio 2026 and 2022](https://marketplace.visualstudio.com/items?itemName=SonarSource.SonarLintforVisualStudio2022)
{% endtab %}
{% tab title="VS CODE" %}
SonarQube for VS Code will automatically identify and fix quality and security issues as you code with enhanced linting capabilities directly in your VS Code IDE.
* [Feature overview](https://www.sonarsource.com/products/sonarqube/ide/features/vs-code/)
* [Installation](/sonarqube-for-vs-code/getting-started/installation.md) instructions
* Supported [Rules and languages](/sonarqube-for-vs-code/using/rules.md)
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-vs-code/connect-your-ide/setup) and list of [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-vs-code/connect-your-ide/connected-mode) benefits.
* [Download](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarlint-vscode)
{% endtab %}
{% tab title="ECLIPSE" %}
SonarQube for Eclipse will automatically identify and fix quality and security issues as you code with enhanced linting capabilities right in your Eclipse IDE.
* [Feature overview](https://www.sonarsource.com/products/sonarqube/ide/features/eclipse/)
* [Installation](/sonarqube-for-eclipse/getting-started/installation.md) instructions
* Supported [Rules and languages](/sonarqube-for-eclipse/using/rules.md)
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-eclipse/connect-your-ide/setup) and list of [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-eclipse/connect-your-ide/connected-mode) benefits.
* [Download](https://marketplace.eclipse.org/content/sonarlint)
{% endtab %}
{% endtabs %}
**Shared code quality and security expectations**
When using SonarQube for IDE, the Sonar Quality Profile is used by default and users can customize their ruleset. If you’re using a different [Quality profiles](/sonarqube-server/10.5/instance-administration/quality-profiles.md) in SonarQube Server, new issues might be raised in SonarQube Server even though your commit looked clean in SonarQube for IDE. With Connected Mode, the same quality profile is applied in both your IDE and in SonarQube Server, and you’re notified in your IDE when your local instance isn’t meeting the project’s [Quality gates](/sonarqube-server/10.5/user-guide/quality-gates.md) standards.
**More security**
When using SonarQube for IDE alone, taint analysis issues found by commercial editions of SonarQube Server aren’t raised in SonarQube for IDE for performance reasons (we don’t want to slow down your editing). In Connected Mode, you’ll see the taint analysis issues SonarQube Server raised in your project. You’ll get all of the context in your IDE that you need to triage and fix security problems thereby making sure the code you commit is safe.
**Using the Open in IDE feature**
When using Connected Mode with SonarQube for IntelliJ, Visual Studio, VS Code, or Eclipse, it’s possible to use the **Open in IDE** button to open most all issues in the code editor, speeding up the time it takes to find and fix the issue. Simply click the **Open in IDE** button from SonarQube Server to view it in your IDE; you’ll be prompted to set up Connected Mode if the project is not already bound.
Opening Security hotspots using the **Open in IDE** feature is available for all of the IDEs supported by SonarQube for IDE. Check out the SonarQube Server [Issues](/sonarqube-server/10.5/user-guide/issues.md) page and the [Issues](/sonarqube-server/10.5/user-guide/issues.md#opening-issues-in-your-ide) article for more details.
## SonarQube for IDE-SonarQube Server version support policy
SonarQube for IDE enables users to establish a connection to the latest SonarQube Server version and to the latest LTA (Long-Term Active) version. When a new LTA version is released, we still enable connecting SonarQube for IDE to the previous LTA version for a certain period of time (currently 12 months after the latest LTA release) to allow enough time for organizations to upgrade their SonarQube Server version.
For more information about long-term support of SonarQube Server, check out our page describing [Patched versions](/sonarqube-server/10.5/setup-and-upgrade/upgrade-the-server/active-versions.md) and, to review IDE-specific requirements, please check the respective pages of the documentation as listed in the next paragraph.
## Setting up Connected Mode
See the following links for instructions on setting up Connected Mode for each supported IDE:
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-intellij/connect-your-ide/setup) in SonarQube for IntelliJ
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-visual-studio/connect-your-ide/setup) in SonarQube for Visual Studio
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-vs-code/connect-your-ide/setup) in SonarQube for VS Code
* [Connected mode setup](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-eclipse/connect-your-ide/setup) in SonarQube for Eclipse
## Understanding SonarQube for IDE usage
SonarQube Server administrators can get an overview of SonarQube for IDE usage among users by going to **Administration** > **Security** > **Users.**
The **Last SonarLint connection** column indicates the last time the user used SonarQube for IDE in connected mode.
You can filter users based on their activity. The available options are:
* **All users**
* **Active users with SonarLint**: Users that used SonarQube for IDE in connected mode at least once in the past 30 days.
* **Active users without SonarLint**: Users that connected to SonarQube Server at least once in the past 30 days.
* **Inactive users**: Users that did not connect to SonarQube Server or use SonarQube for IDE in connected mode in the past 30 days.
## Smart notifications
Connected Mode allows SonarQube Server to send smart alerts to individuals or teams when new issues are discovered. With everyone in the loop, issues can be addressed promptly, improving the overall software quality and delivery. You’ll receive smart notifications in your IDE when:
* the [Quality gates](/sonarqube-server/10.5/user-guide/quality-gates.md) status of a project *open in your IDE* changes
* a SonarQube Server analysis raises new issues *that you’ve introduced in a project open in your IDE*
You can activate or deactivate smart notifications in SonarQube for IDE on the IDE side on a server-by-server basis.
## Reviewing issues in your IDE
Seeing an issue directly in the IDE can help you better understand its context. This is the purpose of the **Open in IDE** button that you’ll see as an authenticated user.
This feature is available if you’re using a compatible version and flavor of SonarQube for IDE. The project must be open in the appropriate IDE and bound to the server using connected mode. To set up SonarQube for IDE in Connected Mode, please check the SonarQube for IDE documentation for your IDE:
* [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-intellij/connect-your-ide/connected-mode) in SonarQube for IntelliJ
* [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-visual-studio/connect-your-ide/connected-mode) in SonarQube for Visual Studio
* [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-vs-code/connect-your-ide/connected-mode) in SonarQube for VS Code
* [Connected mode](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-for-eclipse/connect-your-ide/connected-mode) in SonarQube for Eclipse
Keep in mind that the revision or branch analyzed by SonarQube Server may not be the same as what you have opened in the IDE. In this case, SonarQube for IDE will do its best to locate the issue in your local code.
## Troubleshooting unexpected analysis results
Unexpected analysis results
Observing different analysis results between SonarQube Server/SonarQube Cloud and SonarQube for IDE can have different causes.
**Some issues might be detected by a third-party**
Due to extensive resource requirements, taint vulnerability and some advanced bug detection rules are ignored by SonarQube for IDE. Please check the analyzer (PMD, Checkstyle, ESLint, PyLint, …). SonarQube for IDE will only run rules from Sonar analyzers including [custom rules extending Sonar analyzers](/sonarqube-server/10.5/extension-guide/adding-coding-rules.md). Third-party analyzers usually have their own IDE integration, so we have no plan to run them in SonarQube for IDE.
**Your test files might be mistaken as source files**
Test files can be defined on the server or in the IDE and when running in Connected Mode, these test sources will be used by SonarQube for IDE. Each SonarQube for IDE flavor has its own way of detecting which file is considered a test file; in SonarQube for IntelliJ, you must define your test files as a [Test Sources Root](https://www.jetbrains.com/help/idea/testing.html#add-test-root). To define test files on the server, please see the [Analysis scope](/sonarqube-server/10.5/project-administration/analysis-scope.md) page to set the scope of your analysis.
**Some complex rules are not run in SonarLint**
Due to extensive resource requirements, taint vulnerabilities and some advanced bug detection rules are ignored by SonarQube for IDE. Please check the [SonarQube for IDE roadmap](https://www.sonarsource.com/products/sonarqube/ide/roadmap/) for a list of features and enhancements on the horizon.
**Only line-level issues are reported**
Some rules are able to report issues at the project level. Such issues, are not displayed in SonarQube for IDE, only in [Security-related rules](/sonarqube-server/10.5/user-guide/rules/security-related-rules.md).
**When analyzing Java files, the analyzer might need some context for some issues to be found**
In IntelliJ, there is no incremental compilation of the .class files found in the compiler output folder; these are only produced or refreshed when the project is built. The workaround is to simply build your project with the green hammer (when using IntelliJ) in the top-right toolbar. The project should be built on a regular basis to keep the compiled files up-to-date and overcome this [known limitation](https://sonarsource.atlassian.net/browse/SLI-488).
---
# 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.sonarsource.com/sonarqube-server/10.5/user-guide/sonarlint-connected-mode.md?ask=&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.