lsp-ai

App Listed Dormant

LSP-AI is an open-source language server that serves as a backend for AI-powered functionality, designed to assist and empower software engineers, not replace them.

Checked · Sources

Downloads
2,314
Dependents
Not applicable
Stars
3,210
Forks
116
Contributors
7
Commits
219
Latest release
0.7.0 ·

About

From the project README ·

Empowering not replacing programmers.

| Documentation | Blog | Discord |


LSP-AI is an open source language server that serves as a backend for AI-powered functionality in your favorite code editors. It offers features like in-editor chatting with LLMs and code completions. Because it is a language server, it works with any editor that has LSP support.

The goal of LSP-AI is to assist and empower software engineers by integrating with the tools they already know and love, not replace software engineers.

A short list of a few of the editors it works with:

  • VS Code
  • NeoVim
  • Emacs
  • Helix
  • Sublime

It works with many many many more editors.

NOTE: This project is currently used daily by many users and has reached a stage where it has all the features I want for it. Development is not necessarily done, but no new features are currently being developed for it.

Features

In-Editor Chatting

Chat directly in your codebase with your favorite local or hosted models.

in-editor-chatting

Chatting with Claude Sonnet in Helix

Custom Actions

Create custom actions to do code refactoring, code completions and more!

custom-actions

Using Claude Sonnet to perform refactoring with chain of thought prompting in Helix

Read the full README

Code Completions

LSP-AI can work as an alternative to Github Copilot.

https://github.com/SilasMarvin/lsp-ai/assets/19626586/59430558-da23-4991-939d-57495061c21b

On the left: VS Code using Mistral Codestral. On the right: Helix using stabilityai/stable-code-3b

Note that speed for completions is entirely dependent on the backend being used. For the fastest completions we recommend using either a small local model or Groq.

Documentation

See the wiki for instructions on:

The Case for LSP-AI

tl;dr LSP-AI abstracts complex implementation details from editor specific plugin authors, centralizing open-source development work into one shareable backend.

Editor integrated AI-powered assistants are here to stay. They are not perfect, but are only improving and early research is already showing the benefits. While several companies have released advanced AI-powered editors like Cursor, the open-source community lacks a direct competitor.

LSP-AI aims to fill this gap by providing a language server that integrates AI-powered functionality into the editors we know and love. Here’s why we believe LSP-AI is necessary and beneficial:

  1. Unified AI Features:

    • By centralizing AI features into a single backend, LSP-AI allows supported editors to benefit from these advancements without redundant development efforts.
  2. Simplified Plugin Development:

    • LSP-AI abstracts away the complexities of setting up LLM backends, building complex prompts and soon much more. Plugin developers can focus on enhancing the specific editor they are working on, rather than dealing with backend intricacies.
  3. Enhanced Collaboration:

    • Offering a shared backend creates a collaborative platform where open-source developers can come together to add new functionalities. This unified effort fosters innovation and reduces duplicated work.
  4. Broad Compatibility:

    • LSP-AI supports any editor that adheres to the Language Server Protocol (LSP), ensuring that a wide range of editors can leverage the AI capabilities provided by LSP-AI.
  5. Flexible LLM Backend Support:

    • Currently, LSP-AI supports llama.cpp, Ollama, OpenAI-compatible APIs, Anthropic-compatible APIs, Gemini-compatible APIs and Mistral AI FIM-compatible APIs, giving developers the flexibility to choose their preferred backend. This list will soon grow.
  6. Future-Ready:

    • LSP-AI is committed to staying updated with the latest advancements in LLM-driven software development.

Roadmap

There is so much to do for this project and incredible new research and tools coming out everyday. Below is a list of some ideas for what we want to add next, but we welcome any contributions and discussion around prioritizing new features.

  • Implement semantic search-powered context building (This could be incredibly cool and powerful). Planning to use Tree-sitter to chunk code correctly.
  • Support for additional backends
  • Exploration of agent-based systems
Runs on
CUDA, Metal
What shows it
  • CUDA: lsp-ai feature cuda
  • Metal: lsp-ai feature metal
Native code
Required
  • Binds native code: tree-sitter, tree-sitter-language, llama-cpp-sys-2 (feature cuda)
  • Build uses a native toolchain: cc
Python bindings
No Python binding crate found
License
MIT

Compare with similar projects

Order: strongest tier first, then most downloads, then name, with unmeasured values last. A library counts downloads over 30 days. An app counts binary downloads per release. An app with none counts its crate downloads over 30 days. ML Rust runs this catalogue, so its closest project always gets a row.

lsp-ai beside the projects that share a topic with it
ProjectDownloadsDependentsStarsLatest releaseRuns on (GPU)Native codeLicense
lsp-ai This page App Listed Dormant

LSP-AI is an open-source language server that serves as a backend for AI-powered functionality, designed to assist and empower software engineers, not replace them.

2,314 binary downloads per release Not applicable 3,210 0.7.0 CUDA, Metal Binds native code: tree-sitter, tree-sitter-language, llama-cpp-sys-2 (feature cuda). Build uses a native toolchain: cc MIT
agent App Listed

Ship your code, on autopilot. An open source agent that lives on your machines 24/7 and keeps your apps running. 🦀

19,860 binary downloads per release Not applicable 1,859 0.3.88 GPU support unknown Binds native code: tree-sitter, tree-sitter-language, tikv-jemalloc-sys (feature jemalloc) Apache-2.0
code2prompt App Listed

A CLI tool to convert your codebase into a single LLM prompt with source tree, prompt templating, and token counting.

2,317 binary downloads per release Not applicable 7,756 4.3.0 GPU support unknown Binds native code: libgit2-sys, libz-sys MIT

OpenTelemetry components and utilities for Langfuse LLM observability

2,119 downloads over 30 days 2 4 0.7.2 GPU support unknown No native code found Apache-2.0 OR MIT
blazr App Listed

Inference server for LLMs, speech and embeddings: OpenAI-compatible routes with streaming, plus speech synthesis (TTS) and transcription (ASR). Serves Llama, Mistral, Qwen, Mamba2, MLA+MoE and hybrid models from SafeTensors, AWQ, GPTQ and GGUF.

8 binary downloads per release Not applicable 7 0.7.1 CUDA, WebGPU Binds native code: ring (feature distributed) Apache-2.0
opentau App Listed Dormant

Using Large Language Models for Repo-wide Type Prediction

Not measured Not applicable 121 Not measured Not measured Not measured Apache-2.0
tensorzero App Archived

TensorZero is an open-source LLMOps platform that unifies an LLM gateway, observability, evaluation, optimization, and experimentation.

35 downloads over 30 days Not applicable 11,705 0.0.0 GPU support unknown No native code found Apache-2.0
Why ListedNo archive, New or Featured rule places it, so it is Listed.

What it lacks for Featured

What else the check found

  • The last activity is on 7 Jan 2025, 671 days ago. That reaches the 365 days the rules expect, so the project is dormant. Dormancy rule
  • The oldest outside issue waits 777 days for a reply, past the limit of 270. No maintainer replied in 365 days. Rot signals rule

Not measured: Unpatched vulnerabilities past the grace window.

Exact rules: Listed, Featured app. The check on applied thresholds version 9.

Every rule outcome, as the check records it
  • expected-interval: app: E = 365 days
  • dormancy: last activity 2025-01-07, 671 days ago, E = 365: dormant
  • rot: oldest unanswered issue 777 days (limit 270), no maintainer reply in 365 days
  • featured: not featured: dormant and not stable
  • listed: listed: no archive, new or featured rule applies
Crates3 crates

Measurements and sources

Each signal row shows the raw value, its source and the fetch date. The Sources list gathers every distinct source on this page. Movement needs more history.

Sources6 sources
Adoption2,314 binary downloads per release4 not measured
Adoption measurements
SignalValueSourceFetchedCounts
Active dependentsNot measuredYes
New dependents (365 days)Not measuredYes
Peak active dependentsNot measuredYes
Active dependents as a share of the peakNot measuredYes
Binary downloads per release2314GitHub releasesYes
MaintenanceLatest human commit: 22 months ago4 not measured
Maintenance measurements
SignalValueSourceFetchedCounts
Latest human commit2025-01-07GitHub repositoryYes
Latest release2024-09-24GitHub releasesYes
First release2024-06-07crates.io database dumpYes
Latest version0.7.0crates.io database dumpNo
Days the oldest outside issue waits for a reply777GitHub repositoryYes
Maintainer replies over 365 days0GitHub repositoryYes
Repository archivedfalseGitHub repositoryYes
Repository gonefalseGitHub repositoryYes
Release commit or manifest in the repotruecrates.io packageNo
Published docsNot measuredYes
Latest release fails cargo checkNot measuredYes
Build check dateNot measuredYes
Build check toolchainNot measuredYes
SecurityNot measured
Security measurements
SignalValueSourceFetchedCounts
Unpatched vulnerabilities past the grace windowNot measuredYes
RustSec unmaintained advisoryNot measuredYes
Deprecation noticeNot measuredYes
Deprecated requirementNot measuredYes
Distribution11 releases, 47 downloads over 30 days6 not measured
Distribution measurements
SignalValueSourceFetchedCounts
Releases11crates.io database dumpNo
Downloads over 30 days47crates.io database dumpNo
Binary downloads over the last 3 releases6943GitHub releasesYes
Homebrew installs on request over 365 daysNot measuredYes
Repology repository familiesNot measuredYes
Docker pull growth over 90 daysNot measuredYes
Docker pulls at the growth baselineNot measuredYes
Every version a prereleasefalsecrates.io database dumpYes
Every version 0.0.xfalsecrates.io database dumpYes
Every version yankedNot measuredYes
Crate deleted from crates.ioNot measuredYes
Repository3,210 stars, 116 forks, 7 contributors, 219 commits. Stars alone never qualify a project.
Repository measurements
SignalValueSourceFetchedCounts
GitHub stars3210GitHub repositoryYes — one part of the repository route
GitHub forks116GitHub repositoryYes — one part of the repository route
Contributors with a GitHub account7GitHub contributorsYes — one part of the repository route
Commits on the default branch219GitHub repositoryNo
Repository's main crate left out of the entrynonecrates.io database dumpYes
Facts that never count
Facts that never count measurements
SignalValueSourceFetchedCounts
LicenseMITcrates.io database dumpNo
Runs on, from listed crates and their direct dependenciesCUDA, Metalcrates.io database dumpNo
What shows each backendCUDA: lsp-ai feature cuda; Metal: lsp-ai feature metalcrates.io database dumpNo
Native code, from listed crates and their dependenciesBinds native code: tree-sitter, tree-sitter-language, llama-cpp-sys-2 (feature cuda). Build uses a native toolchain: cccrates.io database dumpNo
Python bindings, from direct dependencies of listed cratesNo Python binding crate foundcrates.io database dumpNo
Crates that depend on a listed crate directlyNot measuredNo

Corrections and review history

Report a correction

No correction applies to this entry.

Judgments

A judgment enters only through an approved issue and a merged pull request.

No judgment applies to this entry.