2026-10-01
LSP hints are billed as agent context
Claude Code #95507: pyright-lsp hint/Unnecessary diagnostics inject into the conversation after Edit/Write and burn paid context; CLI default stays clean; VS Code fades them. No user-level taggedHints filter; `diagnostics` bool is all-or-nothing. Cousin #26634.
Claude Code #95507 is a clean operator harness catch: after Edit/Write, pyright-lsp (and similar) hint and Unnecessary-class diagnostics get injected into the agent conversation. Those hints are billed as context even when they are noise the human editor would fade. The CLI default path stays relatively clean; the VS Code path surfaces and then soft-fades the same diagnostics — so the cost shows up where the harness is chat-shaped.
There is no user-level taggedHints filter today. The `diagnostics` boolean is all-or-nothing: turn it off and you lose useful errors with the hints; leave it on and hint spam pads the paid window. Cousin #26634 is the older thread on the same family of diagnostic injection / context bloat.
Subscribe: /log/feed.xml