Install and configure LSP servers for GitHub Copilot CLI, replacing brute-force grep/decompile with real code intelligence.
Ever watched GitHub Copilot CLI extract a JAR file to a temporary directory, grep through .class
files, and piece together an API signature from raw bytecode? The agent is resourceful, but without a language server, that’s the best it can do.
The Language Server Protocol (LSP) is the standard that powers go to definition, find references, and type resolution in editors like VS Code. It works just as well in the terminal. The LSP Setup skill automates the installation and configuration of LSP servers for Copilot CLI, so the agent gets precise, structured answers about your code instead of relying on text search heuristics.
In this post, you’ll learn how the skill works under the hood, see the configuration format it generates, and get set up for any of the 14 languages it supports today.
The problem: heuristic code understanding #
Without an LSP server, the agent in GitHub Copilot CLI reverse-engineers API information through text search and binary extraction. For a Java project, that might look like:
find ~/.m2/repository -name "*httpclient*.jar"
mkdir /tmp/httpclient && cd /tmp/httpclient
jar xf ~/.m2/repository/org/apache/httpcomponents/httpclient/4.5.14/httpclient-4.5.14.jar
grep -r "execute" --include="*.class" .
For Python, the agent might cat
files inside site-packages
. For TypeScript, it walks node_modules
. These text-based approaches work for simple cases, but they’re doing pattern-matching over raw text rather than true semantic analysis, so they miss generics, overloads, and transitive types, and can’t see compiled bytecode at all. That’s exactly the gap a language server close.
An LSP server solves this structurally. When the agent sends a textDocument/definition
request for a symbol, the language server returns the exact source location, fully resolved type, and signature.
How the LSP Setup skill works #
When triggered, the skill executes a seven-step workflow:
1. Language selection
The agent uses ask_user
with a set of choices to determine which language the user needs LSP support for. This drives all subsequent steps.
2. Operating system detection
The agent runs uname -s
(or checks $env:OS
/ %OS%
on Windows) to determine the target platform. Install commands vary by operating system. For example, brew install jdtls
on macOS versus down from eclipse.org on Linux.
3. LSP server lookup
The skill includes a reference file (references/lsp-servers.md
) with curated data for 14 languages: install commands per operating system, binary names, and ready-to-use config snippets. The agent reads this file and selects the matching entry.
4. Configuration scope
The agent asks whether the config should be:
User-level:~/.copilot/lsp-config.json
—applies to all repositoriesRepository-level:lsp.json
at the repository root or.github/lsp.json
—scoped to a single project
Repository-level configuration takes precedence when both exist.
5. Installation
The agent runs the appropriate install command. For example:
npm install -g typescript typescript-language-server
brew install jdtls
rustup component add rust-analyzer
6. Configuration
The agent writes or merges an entry into the chosen config file. The format uses a lspServers
object where each key is a server identifier:
{
"lspServers": {
"java": {
"command": "jdtls",
"args": [],
"fileExtensions": {
".java": "java"
}
}
}
}
Key rules the skill enforces:
command
must be on$PATH
or an absolute pathargs
typically includes"--stdio"
for standard I/O transport (some servers likejdtls
handle this internally)fileExtensions
maps each extension (with leading dot) to alanguage identifier- Existing entries in the config file are preserved — the agent merges, never overwrites
7. Verification
The agent runs which <binary>
(or where.exe
on Windows) to confirm the server is accessible, then validates the config file is well-formed JSON.
Supported languages #
The skill comes with a set of predefined language servers for several programming languages. If the coding agent faces one that it is not mapped out already, it will search for an appropriate server and walk you through manual configuration.
What changes after setup #
Once an LSP server is configured, the CLI agent can:
Resolve types across dependencies— no more grepping through JAR files ornode_modules
Jump to definitions in third-party libraries, even when source isn’t checked into the repositoryFind all references to a symbol across the projectRead hover documentation for any function, class, or type
This means the agent spends less time on tool calls and produces more accurate code on the first pass. For you, that’s less time waiting while the agent decompiles a JAR file or greps through node_modules to answer a question your IDE already knows, and fewer wrong turns built on a misread signature. The agent reasons about your code with the same structured understanding you get from go-to-definition in your editor, so you can hand it bigger, gnarlier tasks and trust the result.
Get started #
Download the skill: visit theAwesome Copilot LSP Setup skill pageand click theDownload button to get a ZIP file.Extract the ZIP to~/.copilot/skills/
by running:
unzip lsp-setup.zip -d ~/.copilot/skills/
Restart GitHub Copilot CLI: if Copilot CLI is already running, type/exit
first. Then relaunchcopilot
so it picks up the new skill.Ask the agent to set up a language server: for example,“set up LSP for Java”or“enable code intelligence for Python”.Verify: after the skill installs and configures the LSP server, restart Copilot CLI one more time (/exit
, then relaunch), run/lsp
to check the server status, and try go-to-definition on a symbol from one of your dependencies.
The skill is part of the Awesome Copilot project. It’s open source, so contributions and feedback are welcome!
Tags: #
Written by #
Related posts #
Making secret scanning more trustworthy: Reducing false positives at scale
Alerts are more trustworthy and actionable when noise is reduced. See how we improved the verification step with context-aware LLM reasoning.
From one-off prompts to workflows: How to use custom agents in GitHub Copilot CLI
Custom agents let GitHub Copilot CLI understand your stack and team workflows, turning one-off terminal prompts into repeatable, reviewable processes.
We are committed to empowering every developer by building an open, secure, and AI-powered platform that defines the future of software development.