Conductor
SonarQube CLI integration runs automatically in every Conductor workspace when you configure a setup script.
Conductor orchestrates AI coding agent sessions such as Claude Code and OpenAI Codex, running each in an isolated Git worktree. A project-scoped SonarQube CLI integration writes agent files into the current working directory, so a newly created workspace may not contain those files unless they are committed or installed during workspace setup.
Use a Conductor setup script to run the integration automatically each time Conductor creates a workspace.
Prerequisites
The SonarQube CLI is installed and authenticated on the machine that runs the Conductor workspace.
The repository has been analyzed with SonarQube and has a project key.
sonaris available on thePATHused by Conductor setup scripts.
Add a setup script
Conductor runs a setup script each time it creates a workspace. Add the integration command there:
In the Conductor sidebar, hover over your project under Projects and select the gear icon to open Repo settings.
Under Repositories, select your repository, then select Scripts.
In the Setup script field, add this command:
sonar integrate <codex|claude|cursor> --project <YourProjectKey> --non-interactive
Replace <codex|claude|cursor> with the agent you run in Conductor, and <YourProjectKey> with your SonarQube project key.
Conductor runs setup scripts in a non-interactive shell from the workspace directory. The --non-interactive flag prevents prompts, and the explicit integration subcommand and --project flag give the CLI the information it needs without relying on interactive selection.
If your repository already has a setup script, append the integration command to the existing setup flow:
Share the script with your team
The settings UI saves the script to .conductor/settings.local.toml, which applies only on your machine. To give your whole team the same setup script, put it in .conductor/settings.toml instead:
Commit .conductor/settings.toml and merge it to your default branch. Conductor picks up shared repository settings only after they land there.
Use the right integration
Choose the integration that matches the agent you use in Conductor:
sonar integrate codex --project <YourProjectKey> --non-interactivesonar integrate claude --project <YourProjectKey> --non-interactivesonar integrate cursor --project <YourProjectKey> --non-interactive
If you use more than one agent in the same repository, add one command for each integration.
Verify the workspace
After Conductor creates a workspace, open a terminal in that workspace and run:
The status output should show the configured SonarQube connection and the installed integration features. If setup fails, confirm that the CLI is authenticated in the environment that runs the Conductor workspace. In non-interactive environments, you can authenticate with environment variables.
Related pages
Last updated
Was this helpful?