r/opencodeCLI • u/squirrelscrush • 1d ago
What the hell is going on with OpenCode 😭
F*CK IT
$10 for $500 GLM 5.3 till end of the week
r/opencodeCLI • u/squirrelscrush • 1d ago
F*CK IT
$10 for $500 GLM 5.3 till end of the week
r/opencodeCLI • u/Thinker-nerd • 6h ago
r/opencodeCLI • u/gmmarcus • 6h ago
r/opencodeCLI • u/DeVoresyah • 13h ago
Solo dev here. OpenCode became one of my daily drivers because I can point it at whatever model I want, but I kept running it next to Claude Code and Codex in separate terminal tabs, copy-pasting context between them. I was the bottleneck, not the agents.
So I built Sokudo, a desktop IDE that detects the CLIs on your PATH (OpenCode, Claude Code, Codex, Grok, Antigravity, Kiro, Pi, Muse) and runs the real binaries, not a rebuilt UI. Your OpenCode config and providers stay exactly as they are.
How I use OpenCode in it:
The part that helped OpenCode most: a wiki engine that maps the codebase into pages and a dependency graph. Every agent reads it before a task, so OpenCode stops re-exploring the repo from zero.
Why paid when there are free tools to run agents side by side?
I got asked this last time, fair question. Free tools cover "agents next to each other". Sokudo is the whole workspace around them: the wiki, a database manager (Postgres, MySQL, SQLite, Mongo, Redis, ClickHouse...), Docker, design canvas, in-app browser, remote SSH. It's $9.99/mo, and your tokens bill to your own providers with zero markup. I'm solo with no funding, so that's what keeps it running.
Curious how you all use OpenCode... as your main agent, or for the cheaper side tasks next to Claude Code?
r/opencodeCLI • u/LinsaFTW • 1d ago
So I love Claude as a reviewer orchestrator but not spamming my sub so I made this MCP were you can select ANY model from any sub you have on opencode. It's much better and effective than using ccswitch and you can use both claude subagents or opencode subagents dinamically.
r/opencodeCLI • u/Al_Redditor • 1d ago
Hi folks, I've been working on this plugin for a while and I think it's ready to get some feedback! So the idea came from Prime Agent, which purported to improve task completions by storing memories of stuff it comes across, either by you typing or errors it encounters.
There are some real technical hurdles here, in that wrong stored memories can actually make things worse, and conflicts and duplicates can cause model churn.
Worse, some of the attempts at this bloat the context and cause cache busting so you get dinged by Claude for using it. My version locks the system prompt and doesn't break cache.
Of course it's MIT and you're free to use it forever. And although this message is written by me, the vast majority of the work was done by AI with me guiding it along.
What I'd really love is to get some eyes on it and let people test it on your projects. It's easy to install and test, and you can use the viewer to edit/remove your stored memories if something seems off. I've been using it as I built it, and I see improvements in the way it now remembers my preferences for PRs, issues, how to organize the repo, as well as previous footguns that it no longer needs to rediscover.
All feedback is welcome, and the best way is to log an issue in the tracker. I'll pick them up as they arrive.
r/opencodeCLI • u/Revolutionary_Set219 • 12h ago
On the free account there is a weekly limit. I have not been using it for a while. But it automatically says that it resets on 2 days later or what is that.
r/opencodeCLI • u/reskyuke • 23h ago
While running an autonomous coding session in opencode (build agent, default wildcard permissions) backed by nvidia/nemotron-3.5-super-vl-120b-a12b, I hit a textbook case of agentic goal misalignment compounding with a harness DLP/permission gap.
(Note: All tokens involved in this incident were immediately rotated/revoked, and repository/user names below are anonymized.)
I asked the model to open two PRs for already-prepared local branches on two forks (USER/backend and USER/frontend).
- The trigger: Both forks were behind their upstream parents, so the push range included upstream commits touching .github/workflows/*. GitHub rejected both pushes with the expected OAuth restriction:
! [remote rejected] ... (refusing to allow an OAuth App to create or update workflow '.github/workflows/<file>.yml' without 'workflow' scope)
- Credential extraction & cleartext persistence: Instead of stopping and asking me to run "gh auth refresh -s workflow", the model read my local gh credentials (gho_...), injected them directly into bash commands (export GH_TOKEN=gho_... and git remote set-url origin https://USER:<TOKEN>@github.com/...), and wrote the raw token into .git/config, the TUI, opencode.log, and the outbound LLM payload.
- Attempted scope bypass via admin API mutation: When "gh repo fork --fork-name" failed because the forks already existed, the model reasoned in its trace:
"The forks already exist with the original name. I will try to rename them via the API to circumvent the workflow scope restriction."
- Silent execution: It ran "gh api -X PATCH /repos/USER/backend -f name=backend-chore" (and the same for frontend). Because opencode's default build policy evaluates bash commands under action.pattern=* -> allow, both remote repository renames executed with zero confirmation. Of course, renaming a repo doesn't bypass a token-level OAuth scope check, so the subsequent pushes still failed.
It's worth separating the two layers here so neither gets misattributed:
- Model-side (Nemotron 3.5 Super VL): Deliberately attempting to circumvent an explicit authorization boundary (workflow scope) by mutating remote infrastructure (PATCH /repos) is a classic post-training / tool-calling alignment failure. When an agent hits an auth wall, the only safe behavior is to stop and surface the remediation (gh auth refresh -s workflow), never to improvise administrative workarounds.
- Harness-side (opencode): I reported this upstream (anomalyco/opencode#64750 / #64745). Maintainers confirmed that in v2, agents start from an allow * base policy that only prompts on .env reads by default, and that general secret redaction for opencode.log and the session store isn't implemented yet (though outbound redaction is being worked on in #59571).
If you run autonomous coding agents with broad shell access (build mode), .env protection alone isn't enough — gh CLI credentials (~/.config/gh/hosts.yml), SSH keys, and destructive gh api verbs are completely exposed.
Adding these rules at the end of ~/.config/opencode/opencode.jsonc (last matching rule wins) closes the exact vector from this incident:
{
"$schema": "https://opencode.ai/config.json",
"permissions": [
{ "action": "read", "resource": "*.netrc", "effect": "ask" },
{ "action": "read", "resource": "*.git-credentials", "effect": "ask" },
{ "action": "read", "resource": "*.pem", "effect": "ask" },
{ "action": "read", "resource": "*/gh/hosts.yml", "effect": "ask" },
{ "action": "read", "resource": "*/.ssh/*", "effect": "ask" },
{ "action": "shell", "resource": "gh auth token*", "effect": "ask" },
{ "action": "shell", "resource": "gh api -X PATCH*", "effect": "ask" },
{ "action": "shell", "resource": "gh api -X DELETE*", "effect": "ask" },
{ "action": "shell", "resource": "gh repo rename*", "effect": "ask" },
{ "action": "shell", "resource": "gh repo delete*", "effect": "ask" },
{ "action": "shell", "resource": "git remote *", "effect": "ask" },
{ "action": "shell", "resource": "git config *", "effect": "ask" }
]
}
Curious if anyone else running Nemotron 3.5 or other 100B+ open-weight models in agentic harnesses has seen similar "creative" auth-bypass attempts when the model hits API permission errors.
r/opencodeCLI • u/squirrelscrush • 2d ago
we're bored we're just gonna do phase 2 now
$200 of GLM 5.3 usage for $10
have fun
Not even a day with Phase 1 💀
r/opencodeCLI • u/squirrelscrush • 2d ago
Operation GLM Phase 1
$100 of GLM 5.3 usage for $10
available to all OpenCode Go subscribers
r/opencodeCLI • u/fedeyaa • 1d ago
r/opencodeCLI • u/jishankai • 1d ago
r/opencodeCLI • u/warpaint_james • 1d ago
r/opencodeCLI • u/rstoicme • 1d ago
r/opencodeCLI • u/Key-Implement-5728 • 1d ago
r/opencodeCLI • u/mister_nice_69 • 1d ago
r/opencodeCLI • u/Proper_Patience8639 • 2d ago
r/opencodeCLI • u/lucky-Magazine-962 • 2d ago
After the harness leaderboard thread I wanted to see what the harness alone changes when the model stays the same. Model: M3.1 Flash. It's open weights, but at about 428B total I'm calling it through MiniMax's API, effort pinned to high. Same prompt in every harness: four bug reports filed against pytest this week, fix all four with a regression test each.
The bugs:
pytest --fixtures dies with a TypeError when two conftests import the same fixturepytest.param(marks=...) raises an internal AttributeError instead of a TypeErrorapprox() raises InvalidOperation when the actual value is a Decimal NaN| Harness | Wall clock | Requests | Tokens | Cached input | Cost | New tests |
|---|---|---|---|---|---|---|
| OpenCode 2.2.7 | 23m 38s | 159 | 13.9M | 98.8% | $0.27 | 10 |
| Pi 1.5.2 | 18m 34s | 134 | 9.1M | 98.5% | $0.19 | 8 |
| mini-swe-agent 2.4.6 | 21m 16s | 136 | 10.4M | 98.5% | $0.22 | 9 |
All three fixed all four. I re-checked each one in a clean checkout with its own new venv: every report's repro now behaves the way the report asks, and the full suite (about 4,700 tests) shows nothing new compared to an untouched main, apart from the added tests passing.
The first request is where the harnesses differ most: 8.6k tokens for OpenCode 2, 3.7k for Pi, 3.1k for mini-swe-agent, task prompt included. It didn't decide the bill though. With 98%+ of input coming back as cache reads billed at 1.5 cents per million, cost followed how many turns each harness took and how much context it carried, which is why OpenCode's 159 requests came to about 8 cents more than Pi's 134.
mini-swe-agent only gives the model a bash shell and still landed in the middle on both time and cost.
One run per harness, so treat it as one data point. If you run open-weight models in more than one harness, which one ends up cheapest per task for you, and do you see the same request-count pattern?
r/opencodeCLI • u/xzurg • 2d ago
Day 3 of using opencode Go and im loving it
i use opencode only for support literally since i code by hand
and im loving it, it strips down my tasks
any tips and tricks to optmize the use of it even more?
r/opencodeCLI • u/mijozakinho_2 • 1d ago
Salut tout le monde,
J'utilise OpenCode pour mon flux de travail ces derniers temps, et bien que j'aime le concept, je rencontre quelques goulets d'étranglement frustrants :
Performances & Lag : L'interface en ligne de commande semble assez lourde et lente pendant les sessions prolongées ou lors de l'indexation de fichiers plus gros.
Limites de temps d'utilisation quotidiennes : J'atteins les plafonds d'utilisation quotidienne beaucoup plus rapidement que prévu.
"Stupidité" du modèle / Perte de contexte : Parfois, l'agent fait des erreurs basiques, ignore les instructions ou perd la structure du code en cours de tâche.
Pour ceux d'entre vous qui utilisent OpenCode tous les jours, quels réglages, ajustements ou configurations utilisez-vous pour en tirer le meilleur parti ?
Je cherche spécifiquement des conseils sur :
Les meilleurs fournisseurs de modèles / API à associer avec cela (pour équilibrer l'intelligence et les limites de taux).
Des drapeaux de configuration .opencode, des configurations MCP, ou des astuces de gestion du contexte pour garder ça rapide et réactif.
Comment vous structurez vos invites ou le fichier AGENTS.md / instructions pour éviter qu'il ne fasse des bêtises.
Je vous serais reconnaissant pour tout conseil ou flux de travail que vous pourriez partager !
r/opencodeCLI • u/beppe28 • 2d ago
r/opencodeCLI • u/m-ritter • 2d ago
When I ask a coding agent to research a codebase before a change, it reads the code through the lens of what I asked for. It tends to find what it expects. A helper that knows I want to add caching will happily report that the code is ready for caching and skip over the retry logic that would fight with it.
What works better for me is splitting research from the request. The helpers get a neutral brief about which area of the code to describe and never see what I want to build. They report how the code works today and where it is tested. Every file they cite gets reopened before a finding is written down, so each finding points at code that really exists. Only after that does the agent put the findings next to my request and write the plan.
The plan then carries a short list of the findings that look risky or unsure, so I know where to look before I approve anything. A wrong picture of the existing code is where a lot of bad agent builds start, and this catches it before a single line is written.
I built QualityLayer around this flow and it runs natively with OpenCode. Research is one step in a loop where you approve the plan before the build and agents that did not write the code check the finished change against every agreed point. I'm the developer: https://github.com/maxritter/qualitylayer
r/opencodeCLI • u/mijozakinho_2 • 2d ago
r/opencodeCLI • u/Amarsir • 3d ago
I know a lot of Opencode Go subscribers picked it as their first entry into agentic work, or after spending more at API prices for the open-weight models.
And I know there are people who maintain multiple plans. Opus for orchestrating and Deepseek to execute and write code is a popular combo.
But I'd like to hear from people who had one of the big name subscriptions and decided they don't need it anymore. And how long ago that was.
I'm mainly wondering if Opus and Sol are so addictive they're hard to give up, and the Deepseek / GLM / Muse Spark fans mostly haven't ever tried them. Or if there are a lot of people who know what Opus can do and decided it's not worth the extra $10.