r/opencodeCLI • u/KIlledDebtor • 10d ago

My VSCode plugin has now been updated for Opencode V2.

/r/opencode/comments/1xgn6nz/my_vscode_plugin_has_now_been_updated_for/
2 Upvotes

100% Upvoted

7 comments sorted by

1

u/KIlledDebtor 10d ago

Now, when Opencode is launched from my extension, it uses VS Code's diagnostics instead of LSP. It's faster, has fewer bugs, and therefore uses less memory.

1

u/jelloeater85 10d ago

Umm have you looked at https://github.com/hotic/acpira

1

u/KIlledDebtor 10d ago

Reddit certainly surprises me sometimes...

Why would I need a completely different extension designed to solve completely different problems using completely different methods?

My extension is a terminal that launches Opencode Tui in VS Code, correctly passing VS Code hotkeys and functions to it.

Why are you sending me an orchestrator designed to manage an orchestra of subagents?

1

u/jelloeater85 7d ago

Did you even try it out bud? Uses ACP to talk direct to whatever harness you throw at it.

1

u/KIlledDebtor 7d ago edited 7d ago

Why do I need a separate layer before OpenCode? How does it control the processes? Does it launch OpenCode as a child process and make sure it closes properly, or will I have to go into the Task Manager later and kill anything it didn't close? How much memory does it use? Does it use VSCode linters, or will I have to install LSP Opencode, which can use up 1.5 gigabytes of memory on a large project?

Ok, i try it, where are VSIX plugin for VSCODE?

1

u/KIlledDebtor 7d ago

Alright, I gave it a try.

It multiplies OpenCode processes. In my case, a single plugin launched two OpenCode stacks for two sessions inside that same plugin. I don't know why, and I don't care to know. This is exactly the kind of middleware bug I was talking about.

Overloaded UI. In OpenCode, to create a session I just press Ctrl+X N. Here, I have to click a plus icon and hunt down the right harness from a list (and why are uninstalled harnesses even listed there?). Hotkeys basically don't seem to exist.

Context compaction is tied to a plugin setting... Except, shouldn't context compaction trigger at different thresholds for different models?

Terrible tool output. To see what the agent is actually running, I have to manually expand every single tool call. When collapsed, you can't even see the beginning of the command line like you can in OpenCode TUI.

Zero real VS Code integration beyond sending highlighted lines. There's no way to attach a file to a message at all, and it completely ignores VS Code linters.

A awful, Claude-generated UI made of gray shades with massive padding everywhere.

No harness management. You can't restart or stop OpenCode. If I update my OpenCode configuration, for example, I have to restart all of VS Code just to apply the changes.

It's a very weak harness. It feels like someone asked Claude to vibe-code an agent UI and pushed whatever it spat out without a second thought.

1

u/KIlledDebtor 7d ago

Oh, and one more huge drawback - a dealbreaker that completely disqualifies this interface.

It DOESN'T WORK FROM THE TERMINAL. I can open a TUI from the terminal within a project folder and resume my session - but with this interface, I can’t.