I’m trying to use Sonar Pro in VSCode through the Cline extension, but the experience is very poor. It responds with an explanation, and when I ask it to execute or apply the changes, it just repeats the same response without actually modifying any files. It gets stuck in a loop instead of behaving like an autonomous coding agent.
With Claude 3.7 Sonnet the exact same workflow works fine, so I assume it’s either a configuration issue or a limitation on the Sonar Pro side.
Expected behavior:
– It should apply changes directly to files instead of just repeating instructions.
– It should act as an agent and not require manual confirmation every time.
– It should avoid response loops and actually perform actions.
Key question:
Does the Sonar Pro API support tool-calling / agent-style actions, or is it only exposed as a standard chat completions endpoint?
If it’s chat-only, Cline might not be able to trigger file editing actions like it does with Claude.
Environment:
-
Cline v3.32.7
-
VSCode Version: 1.104.0
-
Electron: 37.3.1 (Build ID: 12342881)
-
Chromium: 138.0.7204.235
-
Node.js: 22.18.0
-
V8: 13.8.258.31-electron.0
-
OS: Linux x64 6.14.0-33-generic
Has anyone managed to get Sonar Pro working as a proper agent via API key in Cline? Any specific configuration or flags to enable agent capabilities?