Skip navigation
OpenCode having LSP support is pretty cool
0:00 / 2:26

OpenCode having LSP support is pretty cool

Rhys

@RhysSullivan65K followers

Visit on X
390 likesDownloadOriginal post

34,689 views

OpenCode having LSP support is pretty cool Added a rename symbol tool to test refactors - 379 updates done correctly in 22s on my stress test Also tried with Claude Code to compare but gave up on waiting for it to complete

25 Comments

Comments from the original post on X (Twitter)

  • dax's profile picture

    @thdxr

    nice wanted to play with this at some point but hard to tell if adding more tools makes things net worse until we have better benchmarks demo is pretty compelling though

    39 likes

  • Rhys's profile picture

    @RhysSullivan

    Are you able to do it in the same way that you did the Stripe MCP demo a while back where you let it just guess what the right args need to be and it's only one tool? i.e callLSP - anecdotally I've found that's when I get the best results from them

    8 likes

  • dax's profile picture

    @thdxr

    interesting hadn't thought to try that

    4 likes

  • Rhys's profile picture

    @RhysSullivan

    here's a PR i've got of it if you wanna try it out: gonna run it on my localcode for a bit to see how it feels & having Claude generate a benchmark of ~12 test cases atm to see how it performs w/ LSP tool vs not having one

    5 likes

  • Rhys's profile picture

    @RhysSullivan

    tbh this PR doesn't really match the vibe of the single stripe tool w/ simple inputs

    4 likes

  • vogel's profile picture

    @ryanvogel

    I really need to look into this more

    4 likes

  • winston's profile picture

    @winstondu

    @beyang this was what I was talking about — not just diagnotics but actually have lsp as a built in tool!

    1 like

  • Daniel Rollins's profile picture

    @deej_io

    This is ace. Honestly, back when I first heard OpenCode had LSP support, this is kind of what I expected. I assumed it meant for efficiently finding symbols and references, and renaming. So I was surprised it still using grep/sed for those things.

    1 like

  • Kevin Courbet's profile picture

    @LonePasserby

    Have you ever used Claude Code extensively, like invested in it with skills, plugins, commands etc? Just gauging whether I should give Open Code a go

    1 like

  • Q's profile picture

    @yeon_gyu_kim

    I built one on here: with full lsp tools support and async subagents

  • Henry Ng.'s profile picture

    @duocdev

    I think we should better promt or only run the lsp check on done, some day ago, gpt5.1codex rejected to continue implementing because of types error

  • David Hapunkt's profile picture

    @nichtsalsdavid

    How can you add this to OpenCode?

  • koushik's profile picture

    @koushik

    for me it just eslint as lsp and not typescript wonder why

  • Noam Lewis's profile picture

    @TheNoamLewis

    Did you try adding a similar tool as mcp to Claude? It's not as convenient to configure manually versus out of the box, but it's interesting to compare

  • Ragnsan Valla's profile picture

    @ragnsanvalla

    O shit. Pls share!!

  • Jaga santagostino's profile picture

    @kandros5591

    I've always wondered why this feature wasn't copied already by other, seems a nobrainer

  • Tommy D. Rossi's profile picture

    @__morse

    instead of passing the character index I would pass the name to replace. that's easier for the LLM

  • Kyle's profile picture

    @kylekane

    i nee to try that out

  • Q's profile picture

    @yeon_gyu_kim

    Thought he didn't know about mine but basically he saw mine and implemented this lool

  • Galin Denev's profile picture

    @galin_denev

    Where do these tools lsp_ come from? Dont have them in my opencode even though LSPs are loaded?