Rovo Dev to support Language Server Protocol (LSP)?

[Palo Otčenáš]

Is there a plan to start supporting Language Server Protocol (LSP) in Rovo Dev?

Similar to LSP in Claude Code or LSP in OpenCode 

[Jovana Dunisijevic]

Hey @Palo Otčenáš 

Yes, our engineering team has been experimenting with using the Rovo Dev CLI as a language server, but this work is still early and not part of the official, supported product surface yet.

[Palo Otčenáš]

So how the command `acli rovodev lsp` useful?

acli rovodev lsp --help
Downloading new Rovo Dev version...

Usage: acli rovodev lsp [OPTIONS]

Run Rovo Dev CLI as a language server.

[Jovana Dunisijevic]

@Palo Otčenáš 

In short, `acli rovodev lsp` lets you run Rovo Dev CLI as a Language Server, so it can plug into your IDE and give you live, in‑editor assistance instead of only working from the terminal.

When you run `acli rovodev lsp` , Rovo Dev starts a Language Server Protocol (LSP) process. Any IDE or editor that supports LSP (VS Code, IntelliJ, etc.) can connect to it. Once connected, you get:

Real‑time diagnostics:
- Rovo Dev analyses the file you’re editing and surfaces problems directly in the editor
- These aren’t just syntax errors – it can flag logic issues or patterns based on broader code understanding.

Inline fixes and suggestions:
- For many diagnostics, you’ll see Quick Fix actions (e.g. “Apply suggested fix”) you can apply directly in your IDE.

Context from your Atlassian stack:
- The LSP instance can still use Rovo Dev’s access to your Jira and Confluence context (for example, if you reference a Jira issue or paste a link in a comment).

Current state:

- It’s exposed as an advanced / experimental capability today and requires manual LSP setup in your IDE (e.g. configuring an LSP extension in VS Code and pointing it at `acli rovodev lsp`).
- The “productized” experience is still on the way