{"version":"2.1.169","anchor":"lsp-diagnostics-setting","canonical_anchor":"lsp-diagnostics-setting","heading":"LSP diagnostics Setting","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169\/e\/lsp-diagnostics-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169","markdown":"### LSP `diagnostics` Setting\n\n**What**\n\nA new `diagnostics` boolean option on each LSP server entry in `lspServers` that controls whether `publishDiagnostics` notifications are automatically injected into the agent context after file edits.\n\n**Usage**\n\n`\/\/ In settings.json: { \"lspServers\": [ { \"name\": \"my-lsp\", \"command\": \"...\", \"diagnostics\": false } ] }` **Details** - Defaults to `true` \u2014 current behavior is unchanged unless you explicitly set `false` - Setting to `false` keeps LSP navigation features (go-to-definition, hover, completions) active while suppressing automatic error\/warning injection after edits - Useful when diagnostics are noisy or slow down the agent loop on large projects **Evidence** Settings schema addition (search for `\"Whether to push publishDiagnostics into the agent context after edits\"`) \u2014 added to `lspServers` schema at line ~11733"}