Based on the Hacker News discussion about Claude Code's new LSP support, here are the 5 most prevalent themes of opinion:
1. Implementation is Confusing and Undercooked Users are frustrated by the lack of official documentation and inconsistent availability of the feature. The process is unclear, and even when followed, it doesn't always work.
CharlesW: "It's strangely difficult to find official information about this... this functionality was released/announced prematurely"tomashubelbauer: "I am on the latest version of Claude Code and nothing comes up when I follow this and search for 'lsp'. Looks like this feature is quite undercooked at the moment."anamexis: "I very much agree that the whole plugins/marketplace system seems half-baked in Claude Code."
2. IDEs are Losing Their Value as AI Tools Emerge Many long-time IDE users, particularly JetBrains subscribers, are questioning their loyalty. They feel their IDEs are no longer essential as AI agents can handle core development tasks directly from the CLI, making the IDE's advanced features less critical.
jarjoura: "It's a shame that my company tied itself to claude-code way too fast... OpenCode has been truely innovating in this space and is actually open source... I fear it's too late to walk back."trq_: "I literally just use the CLI for my git operations anyway."throwaway314155: "I was hoping LSP support would be implemented... But this has been an obvious built in for agents for some time now."
3. JetBrains is Losing Ground Due to Slow AI Integration A significant number of comments criticize JetBrains for failing to integrate its powerful refactoring tools with the emerging AI agent ecosystem. Users feel the company is clinging to a human-centric paradigm and being too slow to adapt.
spullara: "I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding."reactordev: "They had a pretty big moat that they let vscode eat away at. I don’t think they saw any of this coming and are struggling to make sense of it."WahyuS002: "It really does feel like the Innovator's Dilemma playing out for JetBrains... If they don't expose their internal refactoring tools to agents soon, the friction of switching to VS Code/CLI becomes negligible."
4. LSP is Crucial for Improving Agent Capabilities (Especially Refactoring)
Commenters are enthusiastic about LSP support because it promises more reliable and semantic code manipulation, like accurate renaming and finding references, which is difficult with simple text-based tools like grep.
ascorbic: "The same reason you want an LSP in your editor: so you get inline docs and error messages, autocomplete, jump to definition, refactoring actions etc."BeetleB: "As part of a bigger refactor, you want to rename some variables. With an LSP hook, the LLM can make the change (more) reliably."eterm: "Not only can analyzers act as basic linters, but transformations are built right in to them. Every time claude does search-and-replace to add a parameter I want to cry a little, this has been a solved science."
5. The AI Tooling Ecosystem is Moving Extremely Fast There's a general sense of awe at the rapid pace of development, both from the Claude team and the broader ecosystem of open-source tools like OpenCode. This leads to quick obsolescence of older opinions and a dynamic landscape.
nextworddev: "It’s breathtaking how fast Anthropic / Claude Code team ships."reilly3000: "The commit history on that changelog blew me away."dvtkrlbs: "I've been using OpenCode [1] which had this future for at least 6 months. I sometimes baffled by the slow progress of closed source software."theptip: "To be blunt, any opinions... formed 6 months ago are not really relevant to the conversation today given how fast this is all moving."