The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.
C# — LSP setup
- Builtin server:
csharp—csharp-ls - Extensions:
.cs - Install hint:
dotnet tool install -g csharp-ls
Install
Requires the .NET SDK. Install the tool globally:
- macOS:
dotnet tool install -g csharp-ls - Linux:
dotnet tool install -g csharp-ls - Windows:
dotnet tool install -g csharp-ls
Global .NET tools land in ~/.dotnet/tools — ensure that directory is on PATH (Windows: %USERPROFILE%\.dotnet\tools).
Confirm it resolves:
command -v csharp-ls
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": { "csharp": { "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)
None commonly required. csharp-ls picks up the nearest .sln or .csproj; keep the solution restorable (dotnet restore).
Razor / Blazor
Razor and Blazor files use a separate builtin server:
- Builtin server:
razor—roslyn-language-server --stdio - Extensions:
.razor .cshtml - Install hint:
dotnet tool install -g roslyn-language-server --prerelease(requires v5.8.0+; see dotnet/razor)
dotnet tool install -g roslyn-language-server --prerelease
command -v roslyn-language-server
Enable it in a project/user config:
{ "lsp": { "razor": { } } }
Alternatives
- OmniSharp — legacy C# language server (not builtin). Still works but is being superseded by the Roslyn-based servers; prefer
csharp-ls/roslyn-language-server.
Troubleshooting
- PATH:
csharp-ls/roslyn-language-serveron PATH (~/.dotnet/tools); reopen shell after install. - No .NET SDK: install the SDK (not just the runtime) before installing the tool.
- No symbols: run
dotnet restore; an unrestored solution yields empty results. - Razor needs v5.8.0+: older
roslyn-language-serverbuilds lack the--stdioRazor support — install with--prerelease.
Verify
bun ../../scripts/verify-lsp.ts path/to/File.cs