Configuration

SharpLsp workspace configuration

SharpLsp has two configuration surfaces:

workspace-level server settings in sharplsp.toml;
client and UI settings under sharplsp.* in VS Code.

They are not interchangeable. In particular, FSI arguments and inlay-hint display settings are VS Code settings, not TOML fields.

sharplsp.toml Location

Place sharplsp.toml beside your solution or project. SharpLsp starts at the workspace root and walks upward; the first file found is used. In single-file mode it starts from the server's current directory.

The schema uses deny_unknown_fields. A misspelled or unsupported key is a startup error.

Complete TOML Schema

[server]
log_level = "info"
debounce_ms = 150

[csharp]
enabled = true
solution_path = ""

[fsharp]
enabled = true

[diagnostics]
analyzers_enabled = true
solution_wide_analysis = true
project_filter = []

[analyzers]
dead_code = true
monorepo = false

[profiler]
max_concurrent_sessions = 5
default_trace_duration = 30
default_trace_format = "speedscope"
default_counter_providers = ["System.Runtime"]
default_counter_interval = 1
output_directory = ".sharplsp/profiles"

Every field is optional. Omitted fields use the values shown above.

Settings That Affect Runtime Behavior

Field	Behavior
`csharp.enabled`	Starts or skips the C# sidecar
`csharp.solution_path`	Selects a `.sln` or `.slnx`, absolute or relative to the workspace
`fsharp.enabled`	Starts or skips the F# sidecar
`diagnostics.solution_wide_analysis`	Enables the C# startup solution scan
`diagnostics.project_filter`	Limits that C# scan to matching project names
`analyzers.dead_code`	Enables SharpLsp's C# and F# dead-code analyzers
`analyzers.monorepo`	Treats unused public symbols as dead and reports them as errors
`profiler.max_concurrent_sessions`	Caps simultaneous profiler sessions

If solution_path is empty, SharpLsp uses workspace discovery. A workspace containing multiple solutions is ambiguous and may load none until you select one. If a configured path does not name a file, the server logs a warning and falls back to workspace discovery.

Disabling a language prevents its sidecar from starting. Syntax-only host behavior may still exist for C#, but semantic requests for the disabled language return no useful result.

Accepted but Not Yet Applied

The following fields are parsed and retained for compatibility, but changing them does not currently change the named behavior:

server.log_level;
server.debounce_ms;
diagnostics.analyzers_enabled;
all profiler.* defaults except max_concurrent_sessions.

For VS Code logging, use sharplsp.logging.level, which is forwarded to the host as RUST_LOG. Profiler commands currently use their request defaults and write under .sharplsp/profiles.

Common VS Code Settings

Setting	Purpose
`sharplsp.logging.level`	Host log filter
`sharplsp.lspPath`	Trusted-workspace override for the server binary
`sharplsp.csharpSidecarPath` / `sharplsp.fsharpSidecarPath`	Trusted-workspace sidecar overrides
`sharplsp.server.extraArgs`	Extra trusted-workspace server arguments
`sharplsp.fsi.extraArgs`	Arguments passed after `dotnet fsi`
`sharplsp.inlayHints.parameterNames`	Reserved parameter-name hint toggle; not yet applied
`sharplsp.inlayHints.typeInference`	Reserved inferred-type hint toggle; not yet applied
`sharplsp.inlayHints.pipelineTypes`	Reserved F# pipeline hint toggle; not yet applied
`sharplsp.nuget.includePrerelease`	Include prerelease packages in search
`sharplsp.hotReload.onSave`	Trigger hot reload on save
`sharplsp.testLens.enabled`	Show test CodeLens actions
`sharplsp.solutionExplorer.autoReveal`	Follow the active editor in the tree

Member-sort ordering and the debug-adapter path are also configurable in the VS Code Settings UI.

The three inlay-hint settings are registered and readable by the extension, but no production path currently uses them to filter returned hints. Changing them therefore has no effect yet.

.editorconfig

Roslyn and FCS read project/compiler settings through their normal workspace inputs. SharpLsp does not currently run arbitrary third-party analyzer packages merely because an .editorconfig severity exists; see Diagnostics for the implemented sources.