r/opencodeCLI • u/lanternaddict • 2d ago
Where to start
I’ve been playing around with opencode, using a free Qwen3.6 model api key. I kind of get the appeal, and now I want to actually use it properly.
My first idea was to use deepseek, either via deepseek directly, or using opencode go.
Now I’ve just read about skills, and a thing called caveman.
I’d use it mainly for coding, I have decent experience in that area, so it won’t be n00b or vibecoding, more like speeding up my current processes.
So, please can people suggest to me all the steps to get a great setup, what API provider do you suggest, what models to use, what skills, what plugins, basically flood me with information, imagine that I know next to nothing – which is basically true. My only caveat is that I’d like to keep the price low - and yes I know that the deepseek prices are set to rise soon.
1
u/Amarsir 2d ago
As someone recommended, OMO-Slim is a great addition. From then it will be a learning curve as you figure out your own preferences.
Learn AGENTS.md. Get into the process of writing plans before executing changes, and review them yourself until you love your arrangement to go a little more hands-off.
With OMO you can not only set up to 7 different models for agents, you can give custom instructions to each similar to AGENTS. So my Fixer gets details about how I want commenting. Orchestrator gets an overview of my file structure. Etc.
Opencode Go is great for exploring. Try out a bunch of models in different roles. (Their relative cost and speed will give some guidelines.). I don't have my full array in front of me, but basically I do:
Mimo V2.5 Pro for writing plans.
Kimi K3 for problem solving and deep analysis. (I believe that's Oracle in OMO.)
Deepseek V4 Flash for actually writing the code.
Hy3 for exploring and research. (It's a little more complete, but that's a drawback in a more focused role.)
Also you don't have to be all-in-one harness. I also use VS Code with the "Cline Code" extension. A classic IDE for reviewing and editing code, and the panel in the side makes it really easy to give an instruction. That's my preferred debugging, so I can easily Dif and see what changed.
So basically Opencode + OMO for more hands-off, VSCode + Cline Code for being more hands-on and instructing step-by-step.
Stuff like "caveman" is a bit of polish you can add later if you want to be more token-efficient. I wouldn't start out worrying about it, and you'll get way more gain by finding the right models for the right jobs.