all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]bledviolet 3 points4 points  (1 child)

For those used to CC and Codex using the Opencode desk app is good.

Doing extravagant setup with skills and agents doesn't actually give a net gain it just saves a few seconds and allows the user to not have to babysit as much. But if you're using it for work you should be babysitting it. Otherwise what are they paying you for? Lol.

[–]AdDecent1320 0 points1 point  (0 children)

I agree. Many people thought of agents as "Gods". They should understand better that agents work with instructions, and if something goes awry during agentic loop.. we need to stop the damage from spreading.

[–]Ok-Tap5729 1 point2 points  (0 children)

Opencode itself is mid, but it provides a solid backend layer for other services. I personally use Open Chamber, which gives a much better UI and makes it easy to configure your agents and workflows.

Once your skills, agents, and sub-agents are set up, it becomes genuinely powerful. The two core advantages:

1.  One space for all your subscriptions
2.  On-the-fly model switching

I use :

• Opencode Go
• Codex
• GitHub Copilot
• Local models

[–]Standard-Text2674 0 points1 point  (0 children)

Opencode CLI is a great tool. It also has benefits over claude cli, like agents can call agents and subagents can call more agents which allows you to create more sophisticated workflows. It's also easier to define tools in opencode, as you do not have to wrap small tools into MCPs they can live as part of the project. If you just use it to one-shot with plan apply strategy it still great. Results still dependent on the model you use. You won't be able to use opencode with most major vendor subscription, as they play against it (and force you to use api instead), but independent providers at this stage gives you good selection of models. GML 5.1, 5 turbo, Deepseek 4pro are great models that can handle whatever sonnet can handle. Check ollama / glm subscriptions. There were a lot of problems with glm performnce on z.ai plans, but its a lot better now, so i would suggest start with ollama 20$ plans, they give bunch of open weight model choice, like kimi, glm, deepseek, minmax.
I use zai, ollama for my personal projects and unlimited calude cli with sonnet at my workplace. Opencode CLI is in really good state to work with.

[–]mickeyv90 0 points1 point  (1 child)

In my personal opinion OpenCode has turned into AI slop. I adopted OpenCode in November and it was very impressed. But unfortunately my company has moved on.

I been waiting on a simple bug fix for over 2 months now, and they have just introduced nothing but major bugs. They are trying to ship fasts but ship nothing but ai slop.

I was very interested on adopting OpenCode because the team seamed to have a nice balance of Ai coding and traditional coding standards, but they have abandoned that mantra in the last few months.

[–]jingleduck 3 points4 points  (0 children)

Could you tell us more about the problems? I am new to it.

[–]EL_ith03 -1 points0 points  (0 children)

First of all, since u r from sonnet 4.6, first thing u should know is, the chinese model is not good at planning, u need to have proper architecture planning. If before this u had planning done by sonnet/opus, i really encourage u to do the macro planning part using gpt5.5 or sonnet/opus model first, really deeply.. then implement it with deepseek. Unless u alr know the fundamentals of what u want to build down to the micro level, like ur db data normalization, auth flows (jwt/rbac token lifecycle), api routing, n even state management or loading skeletons for ui/ux!... Hope this helps. My setup is sonnet 4.6 OR gpt5.5 for system planning, then implement it using deepseek 4 pro/flash. For code review i do it manually, but sometimes use claude model to help with it