The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.
Lua — LSP setup
- Builtin server:
lua-ls—lua-language-server - Extensions:
.lua - Install hint:
https://github.com/LuaLS/lua-language-server
Install
See https://github.com/LuaLS/lua-language-server.
- macOS:
brew install lua-language-server - Linux: download a release from GitHub, or
pacman -S lua-language-server(Arch) / AUR - Windows: download a release from the GitHub releases page and add its
binto PATH
Confirm it resolves:
command -v lua-language-server
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": { "lua-ls": { "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)
For Neovim config development, point the server at the Neovim runtime and set the Lua runtime version so vim globals and stdlib resolve:
{
"lsp": {
"lua-ls": {
"initialization": {
"Lua": {
"runtime": { "version": "LuaJIT" },
"workspace": {
"library": ["/usr/share/nvim/runtime/lua"]
},
"diagnostics": { "globals": ["vim"] }
}
}
}
}
}
Alternatives
None.
Troubleshooting
- PATH:
lua-language-servermust be on PATH; reopen the shell after install. - Undefined
vimglobal: addvimtoLua.diagnostics.globalsand setLua.workspace.library(see above) for Neovim work. - Wrong runtime version: set
Lua.runtime.version(LuaJIT,Lua 5.4, etc.) to match your interpreter, or stdlib functions report as undefined.
Verify
bun ../../scripts/verify-lsp.ts path/to/file.lua