clice README

The project's README from github.com/clice-io/clice. As one markdown file: README.md.

clice

clice

C++ Standard GitHub license CI Documentation Discord

A C/C++ language server written in modern C++, and more than a language server. Like clangd and ccls it is built on LLVM/Clang, but it is redesigned from the ground up to solve the problems their architecture has left unsolved for years. See What is clice?

The story behind clice and how it was built: clice v1.0 Released: Welcome to Modern C++.

Language Server

Command Line

The same engine answers from the command line:

Built with Modern C++

Getting Started

Install

Download the latest binary from the releases page, or build from source.

Platforms: Linux (x64, ARM64), macOS (x64, ARM64), Windows (x64, ARM64)

Release channels:

Channel Version Where to get it
Stable even minor, e.g. v1.0.0 releases page + VS Code Marketplace + Open VSX
Nightly odd minor, e.g. v1.1.2026112002 GitHub pre-releases + Marketplace and Open VSX pre-release channel (Switch to Pre-Release Version on the extension page)
Per-commit untagged artifacts on the latest green main CI runs

The versioning rule is the VS Code Marketplace convention: even minor = stable, odd minor = pre-release. Nightly patch numbers encode the UTC build time as YYYYMMDDHH (year, month, day, hour — e.g. 2026071902 is 2026-07-19 02:00 UTC), so newer is always higher; a nightly is published only when main gained commits, and only the newest 25 nightlies, none older than 30 days, are kept, besides the one Neovim's Mason registry installs. Every published binary is the exact one that passed the full test suites — releases promote CI builds rather than rebuilding.

For the freshest bits, every green main CI run attaches installable artifacts (binaries and platform vsix) to its run page, so a fix can be tried the moment it merges (GitHub login required for artifact downloads).

Each release also ships *.symbols packages: if clice crashes, attach the newest server log to an issue and the matching symbols let us reconstruct the exact stack. The log location is printed at startup in your editor's clice output panel (Session log directory: — by default under <workspace>/.clice/logs/).

Editor Setup

Editor Setup
VS Code Install the clice extension from the Marketplace
Cursor, VSCodium, Windsurf Install the clice extension from Open VSX
Neovim With nvim-lspconfig on Neovim 0.11 or later: vim.lsp.enable('clice')
Zed Load editors/zed as a local extension
Other Any LSP client works — point it at clice serve

Project Setup

clice reads a compilation database to understand your project. For CMake:

cmake -B build -DCMAKE_EXPORT_COMPILE_COMMANDS=ON

By default clice loads every compile_commands.json in the project root and its immediate subdirectories (e.g. build/). See project setup for other build systems, and the configuration guide for databases elsewhere and files without one.

[!NOTE] clice 1.0 is its first stable release. Bug reports via issues are welcome.

Documentation

Full docs at docs.clice.io/clice: the guide and configuration, every language feature and command, and the design.

Contributing

See building from source or join our Discord.

bazel build //:dist   # clice and the unit tests
pixi run test         # the unit tests and the cases

clice (clice-io/clice)

Searching Database…

1.8K ·GitHub
What is this?clice is a language server for C, C++, Objective-C and CUDA, built on Clang and LLVM. It is written in modern C++ and also ships a command-line tool that uses the same engine.
Is it an editor plugin or a command-line tool?Both. Editors connect to it as a language server, and the same engine also runs from the command line to index, query, lint, format and refactor whole projects.
How do I get it running?Download a binary from the releases page, or install the clice extension from the VS Code Marketplace or Open VSX. In Neovim 0.11+ with nvim-lspconfig, call vim.lsp.enable('clice'). Other LSP clients can point at 'clice serve'.
Does it need anything special from my project?Usually just a compilecommands.json. By default it loads every compilecommands.json in the project root and its immediate subdirectories, such as build/.
Is it stable yet?Yes, 1.0 is the first stable release. Even minor versions such as v1.0.0 are stable, while odd minors such as v1.1.x are nightly pre-releases. Bug reports go through GitHub issues.
Which operating systems and chips does it support?Linux, macOS and Windows, each on both x64 and ARM64.
What makes it different from clangd and ccls?It was redesigned from the ground up to isolate crashes. Compiles run in a pool of worker processes, so a crash costs one worker instead of the whole server. It also adds C++20 named module support and compilation contexts for headers.
Does it support C++20 modules?Yes. It supports full named C++20 modules from a compilecommands.json, scans dependencies and builds the needed modules on demand, and reuses PCH and PCM caches across sessions.
What can the CLI do besides serving the editor?clice index prebuilds the project index, query returns definitions, references and call graphs as JSON, and refactor renames symbols across the whole project. analyze and modularize help move code into C++20 modules.
Why did the author build it?The author says clangd and ccls left architectural problems unsolved for years, so clice was rebuilt from scratch on LLVM and Clang to address them.
Creator
clice-io
Size
25.8 MB
Stars
1.8K
Age
2y
Commits · 90 Days