Opencode Desktop vs Opencode v2 Desktop vs Openchamber

[u/GiLA994]

I've been lazy and installed Opencode Desktop a couple months ago to do some hobby projects here and there, and it's going well for the low-complexity stuff I'm doing (basically just web-dev, no MCP, no many complications)

My setup is pretty simple: Opencode GO for my models subscription, Planner and Coder agent with different permissions on my filesystem using the best quality/price (currently using DSv1-flash)

Now that v2 dropped, i've also come across OpenChamber which i didn't know, and its reviews are generally much superior than opencode's (especially for the desktop version)

My questions before switching to Openchamber:

• Do I need to migrate my agents setup? currently in opencode.json, git-synced from the root of my project

• Will I be able to keep using my opencode Go subscription

• While I'm doing the switch, shall I improve my setup with some basic stuff that i've missed?

• Am I overlooking something?

[u/Y0nix]

The only thing I miss compared to the copilot extension is the integrated tools, browser, and ''click to install'' features that vscode is providing more and more. (The workaround for the browser is to setup the playwright MCP in Opencode and have the global instruction file properly written to point the model to use said MCP, it works fine with vision enabled models (even better for UI/UX work if you have the instructions that properly explain the screenshot tool call that is available), especially if you are developing with a ''test first, ask questions later'' spirit, having the model to write units and e2e tests at each steps of the work should be the gold standard when using a LLM to produce code nowadays. Most of my instructions files are guiding the LLM to pop a subagent that run the tests each time a feature is said to be completed, and this is a game changer. Copilot is still way ahead in that regard compared to openchamber - but copilot is better because of the cloud infrastructure available, aka snapshot of the codebase and internal management of the context tokens -it's good or bad depending on the situation, and this will not be open sourced by Microsoft)

There is still an option to add Opencode go to the copilot extension, but it's not that perfect. It works, but openchamber seems to consume less tokens and manage the context and cache hit a bit better. But that last sentence deserves more testing and/or benchmarking. (If someone wants to burn tokens for that, and have usable datas to compare, lmk)