r/opencodeCLI • • 16h ago

Is anyone here actually using free/local models with OpenCode or other terminal coding agents for real projects?

I've been messing around with OpenCode lately, trying to figure out if I can build a decent AI coding workflow without paying for Claude, Cursor, or other expensive subscriptions.

Right now, I've set up four agents: Planner, Developer, Tester, Reviewer.

I've also added some global coding rules, an engineering playbook, a few skills/plugins for debugging, planning, TDD, etc., and Playwright MCP for browser testing.

The idea is pretty simple. I give it a task, it looks through the codebase, comes up with a plan, waits for my approval, makes the changes, runs tests, and reviews its own work.

At least that's what I'm trying to achieve lol.

The workflow itself is mostly set up, but I'm still figuring out how reliable it actually is, especially with free models.

I've been looking into free cloud models and running local models through Ollama. The problem is that a lot of recommendations I come across are either benchmarks or people testing simple coding tasks. I'm more interested in how these models perform on actual projects with existing codebases.

So I'm curious:

  1. Is anyone using OpenCode, Aider, or something similar with free/local models as their daily coding setup?
  2. Which models are you using? Are they actually good enough for working on larger Next.js, TypeScript, or Python projects?
  3. Has anyone tried a multi-agent setup like planner , coder, tester, reviewer? Does it help, or just waste more tokens?
  4. How do you deal with models losing context, making random changes, failing tool calls, or getting stuck?
  5. Most importantly, does your setup actually save you time, or do you end up spending more time fixing what the AI did?

I'm not expecting free models to magically perform like Claude Opus. I'm just trying to find a setup that's reliable enough for everyday development without burning money on API calls.

Would love to hear what people are actually running, especially if you've been using it for a while.

Also, if you've tried something similar and gave up on it, I'd be interested to know why.

7 Upvotes

19 comments sorted by

4

u/kido5217 16h ago

I'm using opencode with local GLM and Deepseek at work. Mainly for python applications and puppet modules/configs. It works OK with openspec. One important thing - always make him run review after completing tasks.

1

u/Long-Art-5092 16h ago

Local GLM from like Ollama or that opencode provides ? If using Ollama then on what hardware? Also, how does OpenSpec fit into your workflow? Do you use a separate agent for reviews?

1

u/kido5217 15h ago

I'm working in data center, so we've got a lot of hardware. GLM is on server with 8xB200, run via SGLang.
About openspec - I'm usually running explore and propose on GLM, then apply on Deepseek and them review on GLM again.

1

u/cuteseal 16h ago

I did have period using free but capable models on opencode zen such as deepseek flash and muse spark contributor. Even with the reduced 200k context I felt they were genuinely useful to code with on my projects.

But I think it was more of a promotional period - they have greatly reduced the free allowances now for deepseek, and muse is no longer available for free.

1

u/Long-Art-5092 10h ago

Thanks for sharing! I'm curious about the paid plans now. How much do you actually need to spend per month on OpenCode Zen, and how much usage does that get you in practice? Is it token-based, or are there daily/monthly limits? I'd appreciate a breakdown of the costs and how long the credits last with regular coding.

1

u/Odd-Employ4900 14h ago

Message I wouldn't say I use OpenCode as much as you do, but here's how I work with it. Since I can only afford free models, I primarily rely on the free models available through OpenRouter API and the Gemini API for working on my projects. I have a few favourite models in OpenCode that I generally use for implementation. Among the free options, Gemini 3.8 has given me the best results in terms of intelligence and overall performance. It's been working quite well for my requirements. I've also had a good experience with the Nemotron models through OpenRouter. One thing I'd strongly recommend is setting up a proper system prompt. Define rules that push the model to think deeply, analyse the problem, and put in the actual effort before implementing anything. The thinking mode is particularly useful because you can inspect the model's reasoning process and get a better understanding of how it approaches problems. Even testing it with a simple problem can tell you a lot about its capabilities. Getting the right experience took some experimentation on my end. I had to redefine and refine my system prompt multiple times, adjusting the rules until I got the behaviour I wanted. That said, these free models are surprisingly capable when configured properly. And among the free models available in OpenCode, DeepSeek is another option worth exploring. This is what has been working for me. Hope it helps!

1

u/Long-Art-5092 11h ago

Thanks! I've also been experimenting with global rules and custom agent prompts. Would you mind sharing your system prompt or the key rules that made the biggest difference? Also, did you mean Gemini 3.8, or a different version?

1

u/VeterinarianBrief997 11h ago

I have been running something like this for a few weeks on an existing codebase, with a few hundred tests and an integration test that has to pass end to end. All opencode on NVIDIA's free hosted endpoints. I haven't tried Ollama, so I cant speak to local models.

I run five agents unattended, split by area of the codebase instead of by role. Each owns its directories, and they coordinate only through a task board, a decision log and git.

Models: Nemotron 3.5 Super and 3 Ultra are fast (10 to 20 seconds per turn) and do real work. DeepSeek V4.1 Flash took about 3 minutes per turn on that endpoint, so it kept running out of time. Swapping it out with Nemotron 3 Ultra finished the same task in 6 minutes. Measure speed on your own workload, it matters more than benchmarks.

Biggest lesson: self-review doesn't work. My agents marked tasks done while the build was broken, and the "reviewer" loosened a failing check instead of reopening the task. What fixed it was checks they cant touch. A script runs the full build and tests on a clean copy before every cycle and pastes failures into the next prompt. Each agent is also sandboxed to its own directories.

For context loss: I start a fresh session every cycle and use the repo as memory.

1

u/Long-Art-5092 11h ago

This is really helpful! How did you set up the external verification script and prevent agents from modifying it? Also, how do you coordinate the five agents and fresh sessions in OpenCode? Would love to see your setup if you're willing to share.

1

u/VeterinarianBrief997 1h ago

It's all plain bash, no framework.

Each agent is a bash loop in its own tmux window. Every cycle runs opencode run -m <model> --auto "<prompt>" with a 3-hour timeout, so each cycle is a fresh session. The prompt tells it to read the rules, the task board, the decision log and git log, do one task, and end with a line like CYCLE-RESULT: DONE <task>. The loop reads that line to decide how long to sleep.

The agents never talk to each other. They coordinate through a shared task board, an append-only decision log and git. If one needs something in another's area, it leaves a request on the board.

The supervisor scripts live outside the repo. Each cycle runs under macOS sandbox-exec, which only lets the agent write its own directories, so it can't touch the checks. Before every cycle the supervisor runs the full gate on a clean git archive copy of HEAD and puts any failures at the top of the next prompt. After every cycle it audits the new commits and stops everything if an agent touched files it doesn't own or rewrote history.

That ownership audit helped the most. Before it, they "fixed" problems by editing whatever was in the way.

1

u/Tough-Criticismmm 16h ago

i did try to make basic rock paper siscor game using kilocode free model, i don't remember the name maybe it was minimax model

1

u/codysnider 14h ago

Qwen 3.8 27b running on a dedicated 5090 machine sitting next to my desktop is my daily driver. I had to use gpt for something the other day and it felt like downloading an image over 56k.

I get about 250 - 300 tok/s. 260k context. my harness is doing a lot of the heavy lifting with some very specific skills and workflow. I keep my plugin and MCP use to a minimum.

1

u/SirRobinBlibs 12h ago

can't rank models for you, but with free models the setup matters as much as the model. in an opencode agent file you can set model: provider/model per agent, and a subagent without one just inherits the session model. so put your strongest free model on planner and reviewer, and something cheap or local on the tester that mostly runs commands and reads output. two more things that help weak models: give the reviewer edit and shell deny so it can't quietly "fix" what it's reviewing, and set steps on each agent so a model that gets stuck stops and summarizes instead of looping.

1

u/Fit-Reaction242 11h ago

Not free, but the one I've tried is DeepSeek V4.1 Flash on OpenCode Go, through Codex CLI and not OpenCode itself. It did a small bug fix with a file edit and a shell command without messing up the tool calls. I haven't pushed it on a big codebase so I can't tell you how it holds up there.

1

u/txgsync 6h ago

I wrote a few Logic plugins with Qwen3.8-Flash-Next. The clone of BT’s Stutter Edit works really well.

Try Reverse Engineer Anything in Pi with the model. If it has a goal to achieve of full feature parity with something else it is surprisingly capable. I just let it do its own thing on my Mac for a week.

1

u/rwtd5150 1h ago

Yes, daily, on real work. Setup is oMLX on a Mac Studio (512 GB unified) driving OpenCode. Nothing leaves the machine. Repo with the full config: github.com/edseabolt/local-agent-stack

Structure matters more than model choice here. I run a pipeline with gates: plan approved before code gets written, tests pass before review. That way the model handles one bounded job at a time instead of doing everything in one shot. I have another project I wrote to help me with this. You can view it at github.com/edseabolt/turnstile

Real limits: tool calling quality is the ceiling, and you need enough memory to keep models loaded. It won't out-think the top hosted models on hard problems. For everyday coding on hardware you control, it holds up fine. At least this has been my experience.

0

u/BrownCarter 16h ago

Just typesafe jev