IDE Integration — VS Code Extension & Global LSP Server

Codeveira integrates directly into VS Code, JetBrains, and Neovim via the Language Server Protocol. Open code review comments appear as inline squiggles in the relevant files. A single Docker container (the global LSP server) serves all developers — no Node.js installation required on developer machines.

How it works

The LSP proxy (lsp container) listens on TCP port 7777. When a developer's VS Code connects, the proxy spawns an isolated server.js --stdio child process for that connection. The child holds the developer's personal API token and diagnostic cache — completely separate from other connections.

Developer 1 VS Code ─┐
Developer 2 VS Code ─┤  TCP :7777  ──→  lsp container  (proxy.js)
Developer N VS Code ─┘                       │
                                   ┌──────────┴──────────┐
                                   │  per-connection      │
                                   ├─ server.js (dev 1)  │
                                   ├─ server.js (dev 2)  │
                                   └─ server.js (dev N)  │
                                          │ HTTP :3000
                                     Rails API (app container)

docker compose up -d

docker logs codereview-lsp-1
# Expected output:
# [Codeveira LSP proxy] listening on 0.0.0.0:7777
# [Codeveira LSP proxy] CODEVEIRA_URL=http://app:3000

cd extensions/vscode
npm install
npm run build
npx vsce package
# Produces: codeveira-1.0.1.vsix

code --install-extension codeveira-1.0.1.vsix

{
  "codeveira.url": "https://codereview.company.com",
  "codeveira.apiToken": "<your-api-token>",
  "codeveira.repositoryId": "3",

  // Global LSP server (recommended for teams)
  "codeveira.lspHost": "codereview.company.com",
  "codeveira.lspPort": 7777,

  // Optional: how often to poll for new diagnostics (seconds)
  "codeveira.pollIntervalSeconds": 60
}

Diagnostic severity

AI reviewer comments include an emoji prefix that maps to LSP severity. Human comments without a prefix default to Info.

Hover over a squiggle to see the full comment: reviewer name, date, CR identifier, reply count, and AI suggestion hint if one is available.

Quick Fix actions

Click the lightbulb icon (or press Ctrl+. / Cmd+.) on a squiggle line to open Quick Fix:

• Resolve comment — marks the comment as resolved in Codeveira via the API. The squiggle disappears.
• Apply AI suggestion — replaces the flagged line with the AI-generated single-line fix, then resolves the comment automatically. Only shown when the AI reviewer provided a suggestion field.

CR sidebar

Click the Codeveira icon in the VS Code Activity Bar (left panel) to open the Code Reviews sidebar. It shows all open reviews for the configured repository.

Available commands

Find Usages, Go to Declaration & Go to Symbol

Standard+. The same LSP server that delivers review diagnostics also backs three standard LSP requests — textDocument/definition, textDocument/references, and textDocument/documentSymbol — so every LSP-compatible editor gets native UI for free. No extension update is required to use them.

Behind this, a dedicated indexer Docker container — separate from app, sidekiq, and lsp — parses every changed file with tree-sitter on each push and writes a symbol index to Postgres. Only files touched by the new commit(s) are re-parsed, so browsing stays fast without a full-repo re-index on every push.

Supported languages: JavaScript, TypeScript/TSX, Ruby, Python, Go, Java, Kotlin, PHP. Files in any other language are simply skipped — everything else continues to work normally.

The indexer container runs in isolation on purpose: a parsing failure there never affects review creation, comments, or notifications, and its memory/CPU limits (INDEXER_MEM_LIMIT, INDEXER_CPUS) are configured independently so a large indexing backlog can't starve the rest of the stack. See Settings for the full environment variable reference.

New commits are indexed automatically. If a repository was added before this feature existed, or results look stale, trigger a full rebuild from the repository's Edit page → Rebuild symbol index (admin only).

This same index also powers Ctrl+click (declaration) and Alt+click (Find Usages) directly in the web Repository Browser — no editor required.

Port and firewall

The LSP server uses raw TCP on port 7777 — not HTTP. Open it in your server's firewall:

# UFW (Ubuntu / Debian)
ufw allow 7777/tcp

# firewalld (RHEL / CentOS / Fedora)
firewall-cmd --add-port=7777/tcp --permanent
firewall-cmd --reload

The bundled nginx container (see Domain & HTTPS) already proxies this TCP connection with no configuration needed. If you're running your own reverse proxy instead, nginx's stream module can do the same — see the nginx.conf.example in the repository root for the stream {} block, which must be added to /etc/nginx/nginx.conf at the top level (not inside http {}).

JetBrains (IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider)

The Codeveira JetBrains plugin is available for download. It connects to the same global LSP server on TCP port 7777 using IntelliJ's built-in LSP client (requires IntelliJ 2024.2+).

Install the plugin

1. Download codeveira-jetbrains-1.0.1.zip from the Download page.
2. In your IDE go to Settings → Plugins → ⚙ → Install Plugin from Disk…
3. Select the downloaded .zip file and click OK.
4. Restart the IDE when prompted.

Configure credentials

Go to Settings → Tools → Codeveira and fill in:

Using the plugin

Open any file in the project — the LSP connection is made lazily on first file open. Diagnostics appear as squiggles within a few seconds.

Neovim

Neovim supports LSP natively via nvim-lspconfig. Copy extensions/neovim/codeveira.lua from the repository (or the snippet below) to your Neovim config and call setup():

-- init.lua (or after/plugin/codeveira.lua)
require('codeveira').setup({
  host          = 'codereview.company.com',
  port          = 7777,
  token         = 'YOUR_API_TOKEN',
  repository_id = '3',
})

The plugin auto-detects nc, ncat, or socat for the TCP connection (install any one of them). Default keymaps on attach:

Diagnostics appear via vim.diagnostic. Use :lua vim.diagnostic.open_float() at any time to read the full comment text.