A fork of the nanocode minimal coding agent (originally ~260 lines of Java) that adds optional Language Server Protocol support via Eclipse JDT Language Server. When a Java workspace is detected, the agent can download and start JDT LS, exposing three new tools to the LLM: java_definition (go-to-definition), java_hover (type info and Javadoc), and java_diagnostics (compiler errors). This gives the model classpath-aware, compiler-backed answers instead of relying solely on grep and file reads. The post walks through the architecture, practical prompt examples, trade-offs (JDT weight, token costs, trust model), and includes LspProbe.java for testing LSP without an LLM API key.

8m read timeFrom shaaf.dev
Post cover image
Table of contents
Does LSP fits the same architecture?What this fork adds (in practice)Examples (prompts that now “make sense”)Trade-offs worth saying out loudLinks

Sort: