🎉 SonarQube CLI is now in Open Beta and it's available to everyone!

Sonar Updates
, , ,
1

We’re excited to announce the public release of SonarQube CLI, now officially in Open Beta!

This represents a significant advancement for how you interact with your SonarQube Cloud or Server instances, both within your automation pipelines and in your agent-based workflows. One install. One authentication step. Every SonarQube capability available through one tool.

What is SonarQube CLI?

SonarQube CLI is the unified, automation-native command-line tool for the SonarQube ecosystem, providing a single, coherent command structure for all your verification needs.

In the era of agentic development, this CLI will allow you to integrate SonarQube capabilities with every place modern development actually executes: AI agent environments, git hooks, platform automation scripts, and CI pipelines.

What’s available today?

:file_folder: Project Queries

Find projects quickly with free-text search and pagination:

sonar list projects

:magnifying_glass_tilted_left: Issue explorer

Query SonarQube issues and filter them by severity, branch, or pull request

sonar list issues

:bar_chart: Analyze a file for quality and security issues

Runs the SonarQube analysis on a file of a project using the SonarQube Agentic Analysis available for SonarQube Cloud projects

sonar verify

:locked_with_key: Secrets Scanning

Analyze files and piped inputs for leaked secrets and credentials:

sonar analyze secrets

:robot: Set up Claude Code integration

Seamlessly configures SonarQube for Claude Code and sets up hooks and skills that can be used by the agent.

sonar integrate claude

How to get started

Full documentation and installation instructions are available at: cli.sonarqube.com

We’d love to hear what you think. Whether you run into an issue, have a feature request, or just want to share how you’re using it, your feedback directly shapes what we build next. You can use this feedback form to let us know your first impressions.

Stay tuned for what’s coming next. :rocket:

The Developing Experience squad

2

Thanks for the update Farah!

May I ask you to summarize the differences between this new CLI tool and the IDE plugins? (E.g. “SonarQube for IDE” in VSCode). Advantages, disadvantages. Is it worth working with both approaches? or should I replace the IDE plugin with the CLI tool and run it in the “pre-commit” setup?

Thanks!

4

Hello Juan, thank you for this question.
We believe SonarQube for IDE and SonarQube CLI serve different workflows and are optimized for different engineering needs.

We designed the CLI to mainly support two groups of engineers: The ones using heavily AI agents for code generation in their terminal, and the ones who want to automate their workflows through scripting.

For this first group, the CLI enables deterministic, agent-driven verification as early as possible in the generation loop, helping catch issues like secret leaks before they ever reach a prompt.

For the second group, it fits naturally into shell scripts and automated pipelines without requiring an IDE to be open.

We expect SonarQube for IDE to be still the preferred interface for engineers generating code in the IDE to get a richer experience with an interactive UI that easily highlights issues, offers rules description and fixes with Quick Fixes and AI CodeFixes. In the IDE, analyzers are run when you make changes to have near to real time analysis while the CLI analysis relies on a manual trigger, except from hooks, to invoke analysis by the developers and agents.

Of course, we’re happy you can use any of our products and adapt them to your needs and we’d be glad to hear about your main use case for SonarQube CLI.

6

Hello,

Will the the CLI support the community build as well?

Thank you,

Justin