LSP

Symbiotic Code integrates with your Language Server Protocol (LSP) to help the LLM interact with your codebase. It uses diagnostics to provide feedback to the LLM: after the agent edits or writes a file, any errors reported by the language server are added to the tool result so the agent can fix them.

Built-in LSP Servers

Symbiotic Code comes with several built-in LSP servers for popular languages:

LSP Server	Extensions	Requirements
astro	.astro	`typescript` dependency in project; auto-installs `@astrojs/language-server`
bash	.sh, .bash, .zsh, .ksh	Auto-installs `bash-language-server`
biome	.ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, .cts, .json, .jsonc, .vue, .astro, .svelte, .css, .graphql, .gql, .html	`biome` installed in the project or on your `PATH`
clangd	.c, .cpp, .cc, .cxx, .c++, .h, .hpp, .hh, .hxx, .h++	Auto-downloads from GitHub releases
clojure-lsp	.clj, .cljs, .cljc, .edn	`clojure-lsp` command available
csharp	.cs	`.NET SDK` installed; auto-installs `csharp-ls`
dart	.dart	`dart` command available
deno	.ts, .tsx, .js, .jsx, .mjs	`deno` command available and a `deno.json`/`deno.jsonc` file
dockerfile	.dockerfile	Auto-installs `dockerfile-language-server-nodejs`
elixir-ls	.ex, .exs	`elixir` command available; auto-downloads elixir-ls
eslint	.ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, .cts, .vue	`eslint` dependency in project
fsharp	.fs, .fsi, .fsx, .fsscript	`.NET SDK` installed; auto-installs `fsautocomplete`
gleam	.gleam	`gleam` command available
gopls	.go	`go` command available; auto-installs `gopls`
haskell-language-server	.hs, .lhs	`haskell-language-server-wrapper` command available
jdtls	.java	`Java SDK (version 21+)` installed; auto-downloads JDTLS
julials	.jl	`julia` and `LanguageServer.jl` installed
kotlin-ls	.kt, .kts	Auto-downloads from GitHub releases
lua-ls	.lua	Auto-downloads from GitHub releases
nixd	.nix	`nixd` command available
ocaml-lsp	.ml, .mli	`ocamllsp` command available
oxlint	.ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, .cts, .vue, .astro, .svelte	`oxlint` dependency in project
php intelephense	.php	Auto-installs `intelephense`
prisma	.prisma	`prisma` command available
pyright	.py, .pyi	Auto-installs `pyright`
ruby-lsp (rubocop)	.rb, .rake, .gemspec, .ru	`ruby` and `gem` commands available; auto-installs `rubocop`
rust	.rs	`rust-analyzer` command available
sourcekit-lsp	.swift, .objc	`swift` installed (`xcode` on macOS)
svelte	.svelte	Auto-installs `svelte-language-server`
terraform	.tf, .tfvars	Auto-downloads from HashiCorp releases
texlab	.tex, .bib	Auto-downloads from GitHub releases
tinymist	.typ, .typc	Auto-downloads from GitHub releases
typescript	.ts, .tsx, .js, .jsx, .mjs, .cjs, .mts, .cts	`typescript` dependency in project
vue	.vue	Auto-installs `@vue/language-server`
yaml-ls	.yaml, .yml	Auto-installs Red Hat `yaml-language-server`
zls	.zig, .zon	`zig` command available; auto-downloads zls

LSP servers are automatically enabled when one of the above file extensions are detected and the requirements are met. Auto-installed servers are stored in ~/.local/share/symbiotic/bin/.

You can disable automatic LSP server downloads by setting the SYMBIOTIC_DISABLE_LSP_DOWNLOAD environment variable to true. Servers that are already installed or available on your PATH still work.

To use ty instead of pyright for Python, set SYMBIOTIC_EXPERIMENTAL_LSP_TY=true. ty must be on your PATH or in your project’s virtual environment.

How it works

When Symbiotic Code opens a file, it:

Checks the file extension against all enabled LSP servers.
Finds the project root for each matching server (for example the nearest lockfile, go.mod, or Cargo.toml).
Starts the appropriate LSP server for that root if not already running.

If a server fails to start, it isn’t retried for that root until Symbiotic Code restarts.

LSP tool (experimental)

Set SYMBIOTIC_EXPERIMENTAL_LSP_TOOL=true (or SYMBIOTIC_EXPERIMENTAL=true) to give the agent an lsp tool for code navigation: go to definition, find references, hover, document and workspace symbols, go to implementation, and call hierarchy. It’s controlled by the lsp permission.

Configure

You can customize LSP servers through the lsp section in your Symbiotic Code config.

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": {}
}

Each LSP server supports the following:

Property	Type	Description
`disabled`	boolean	Set this to `true` to disable the LSP server
`command`	string[]	The command to start the LSP server. Required unless `disabled` is `true`
`extensions`	string[]	File extensions this LSP server should handle. Required for custom servers
`env`	object	Environment variables to set when starting server
`initialization`	object	Initialization options to send to the LSP server

Configuring a built-in server replaces how it is started: your command is used instead of the built-in detection and auto-install, and built-in initialization options are not sent. The server keeps its built-in extensions and root detection unless you override extensions.

Let’s look at some examples.

Environment variables

Use the env property to set environment variables when starting the LSP server:

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": {
    "rust": {
      "command": ["rust-analyzer"],
      "env": {
        "RUST_LOG": "debug"
      }
    }
  }
}

Initialization options

Use the initialization property to pass initialization options to the LSP server. These are server-specific settings sent during the LSP initialize request:

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": {
    "pyright": {
      "command": ["pyright-langserver", "--stdio"],
      "initialization": {
        "python": {
          "pythonPath": ".venv/bin/python"
        }
      }
    }
  }
}

Initialization options vary by LSP server. Check your LSP server’s documentation for available options.

Disabling LSP servers

To disable all LSP servers globally, set lsp to false:

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": false
}

To disable a specific LSP server, set disabled to true:

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": {
    "typescript": {
      "disabled": true
    }
  }
}

Custom LSP servers

You can add custom LSP servers by specifying the command and file extensions:

symbiotic.json

{
  "$schema": "https://config.symbioticsec.ai/config.json",
  "lsp": {
    "custom-lsp": {
      "command": ["custom-lsp-server", "--stdio"],
      "extensions": [".custom"]
    }
  }
}

Custom servers are started in your current working directory.

Basics

Customize

Security

Configuration

Built-in LSP Servers

How it works

LSP tool (experimental)

Configure

Environment variables

Initialization options

Disabling LSP servers

Custom LSP servers

​Built-in LSP Servers

​How it works

​LSP tool (experimental)

​Configure

​Environment variables

​Initialization options

​Disabling LSP servers

​Custom LSP servers

Built-in LSP Servers

How it works

LSP tool (experimental)

Configure

Environment variables

Initialization options

Disabling LSP servers

Custom LSP servers