Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

34,689 görüntüleme • 10 ay önce •via X (Twitter)

25 Yorum

dax profil fotoğrafı
dax10 ay önce

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

Rhys profil fotoğrafı
Rhys10 ay önce

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

dax profil fotoğrafı
dax10 ay önce

interesting hadn't thought to try that

Rhys profil fotoğrafı
Rhys10 ay önce

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

Rhys profil fotoğrafı
Rhys10 ay önce

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

vogel profil fotoğrafı
vogel10 ay önce

I really need to look into this more

winston profil fotoğrafı
winston10 ay önce

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

Daniel Rollins profil fotoğrafı
Daniel Rollins10 ay önce

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.

Kevin Courbet profil fotoğrafı
Kevin Courbet10 ay önce

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

Q profil fotoğrafı
Q10 ay önce

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

Henry Ng. profil fotoğrafı
Henry Ng.10 ay önce

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 profil fotoğrafı
David Hapunkt10 ay önce

How can you add this to OpenCode?

koushik profil fotoğrafı
koushik10 ay önce

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

Noam Lewis profil fotoğrafı
Noam Lewis10 ay önce

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 profil fotoğrafı
Ragnsan Valla10 ay önce

O shit. Pls share!!

Jaga santagostino profil fotoğrafı
Jaga santagostino10 ay önce

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

Tommy D. Rossi profil fotoğrafı
Tommy D. Rossi10 ay önce

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

Kyle profil fotoğrafı
Kyle10 ay önce

i nee to try that out

Q profil fotoğrafı
Q10 ay önce

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

Galin Denev profil fotoğrafı
Galin Denev10 ay önce

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

Yang Zhao profil fotoğrafı
Yang Zhao10 ay önce

Why can’t we just implement an Agent Skill to do the same in CC?

Andrew Gazelka profil fotoğrafı
Andrew Gazelka10 ay önce

why not just use claude code mcp

Carlos Lebron profil fotoğrafı
Carlos Lebron10 ay önce

22s for 379 updates is solid. Claude Code must’ve gone on a coffee break

Rhys profil fotoğrafı
Rhys10 ay önce

@nikitabier can you just ban this guy for using AI replies for a week I’ll Venmo you $20 if you do

Ram A P profil fotoğrafı
Ram A P10 ay önce

That’s some serious renaming magic, must've waved a wand 🪄

Benzer Videolar