The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.
Java — LSP setup
- Builtin server:
jdtls—jdtls - Extensions:
.java - Install hint:
https://github.com/eclipse-jdtls/eclipse.jdt.ls
Install
- macOS:
brew install jdtls - Linux: Download from eclipse-jdtls/eclipse.jdt.ls releases, extract, and wrap the launcher as
jdtlson PATH (some distros package it asjdtls/jdt-language-server). - Windows: Download the release archive and add the
jdtlslauncher (bin/jdtls.bator the Python wrapper) to PATH.
Requires a JDK 17+ to run the language server itself (the project may target an older Java version).
Confirm it resolves:
command -v jdtls
Configure
Builtin — usually NO config needed (auto-resolved by extension). Configure only to set priority, init options, override extensions, or disable. Same JSON shape in every harness's project config (per-harness paths: the Configure step in SKILL.md):
{ "lsp": { "jdtls": { "priority": 100 } } }
For builtin ids in a PROJECT config, command is supplied automatically — only set priority/initialization/extensions/disabled (a project entry drops env). env, and a fully custom (non-builtin) server with its own command, must go in your harness's USER config (see the Configure step in SKILL.md).
Initialization options (only if commonly needed)
jdtls maintains a per-project workspace data directory and the first index is slow (it resolves the full classpath and builds). Point JAVA_HOME at a JDK 17+ if jdtls cannot find one (USER config only; a project entry drops env):
{ "lsp": { "jdtls": { "env": { "JAVA_HOME": "/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home" } } } }
Most settings (runtimes, format, import order) are passed via settings.java.* initialization options; defaults work for Maven/Gradle projects with a standard layout.
Alternatives
- No mainstream alternative.
jdtls(Eclipse JDT Language Server) is the de-facto standard and powers the official VS Code Java extension.
Troubleshooting
- PATH:
jdtlson PATH; reopen shell after install. - No JDK found: server exits immediately — set
JAVA_HOMEto a JDK 17+. - Slow / no completions at first: the initial classpath index can take a minute or more on large Maven/Gradle projects; wait for it to finish.
- Stale state: delete the jdtls workspace data dir to force a clean re-index if results go wrong after big dependency changes.
- Build tool required: keep
pom.xml/build.gradlevalid; a broken build descriptor breaks symbol resolution.
Verify
bun ../../scripts/verify-lsp.ts path/to/File.java