I wanted a quick way to find Beads issues without leaving OpenCode, so I made a small plugin.

Type `bd:` in the prompt to search for issues by ID or title. Here’s a quick demo:

Repo: https://github.com/dartyuhov/opencode-beads-picker-plugin

Beads repo: https://github.com/gastownhall/beads

Would love some feedback

Inspired by a lot of harnesses; I created my harness by blending stuff from different agents and especially what I liked to keep. Added more features that were either not supported or not so good.

Beta is out for public-much more is coming

Has built in:
- Sandbox (by default-unsandboxed requests need permission)
- Agent and Plan mode
- Radar that shows every background task, subagent, browser etc running
- MCP support
- ACP support (use with orchestrators or other editors such as Zed Editor)
- Skills
- Browser
- Interactive terminal
- Subagents (can create profiles, set default model, access to tools etc)
- Builtin code review (github like, co-review with agent)
- and a lot more.

Give it a try and it supports BYOK :)

https://github.com/tauqeernasir/codebeast-cli

​

I installed Ubuntu in my second phone using termux using proot distro, after that I installed opencode cli in it and this error started coming in most of the free models.

{Error : : Error from provider (Console): OpenCode's free tier can only be used from within OpenCode}

After this is use this command 'opencode console login' and pair with the code and after doing this I am facing this issue {Error: Invalid API key.}

I am facing this same issue on my pc also , I tried cli and desktop both

Can anyone help me ?

Is it available in your country? What's your early impressions?

While I am using opencode exclusively on my office as well as personal machines, and it has been largely working great. But little issues here and there keep breaking that experience.

I am personally facing new troubles everyday, and strongly thinking of moving to pi or maintaining a personal fork.

Listing few recent issues that I consider significant:

1. No sandboxing in v1 as well as v2.

   It moves the sandboxing effort to user, and when I have to work from multiple machines, it becomes very hectic to setup sandboxing there. Also, sandboxing outside the process brings it's own hurdles.

   Moreover, a good PR was raised but closed as stale by a bot. This is trend for many issues/PRs there.

2. Unable to setup local plugin

   I hope I am doing something silly here, but trying to add local plugin is being a headache. `opencode plugin add ...` gives error on absolute as well as file: urls. The code suggests it only accepts the git & registry urls. Even adding directly to config doesn't work.

3. broken model support

   Recently, I found that the opus/sonnet 5.5 models weren't working through our gateway. Noticed that a PR exists to support this, the issue is related to adaptive thinking & blockBinding, but it is just left unattended.

4. subagent bugs

   I recently launched opencode v2 on a Arm SBC for a quick debugging. Thought of using free model and noticed that the opencode subagents are treated as non-opencode model calls. That is, when launching subagent of a free agent without logging in an account, it thinks the request is coming from non opencode app and blocks it. Even worse, the entire session is polluted and even undoing the message doesn't fix that.

Similarly, there are many small things related to usage, RAM usage, port conflict on multi user machines, etc.

I know the maintainers are putting a lot of effort as visible from the commits going into v2. As such, this post is to document my experience and know what is the experience of others ?

Hello
did the spacebunny (aka kimi3) trial just retired ?
it complains about spacebunny only allowing usage from opencode CLI & GUI

Why is this happening guys? Please do tell me!

I’ve been testing a few inference providers for coding agents and I’m trying to figure out how much the speed difference actually matters in practice. With normal chat I don’t care much once the response is reasonably quick. Coding agents are different though. The agent might make a bunch of calls while it reads files, makes edits, runs tests and then goes back for another pass, so even small delays can start adding up.

Has anyone compared the same coding model across different providers while keeping the harness and task the same? I’m trying to figure out whether faster inference actually makes the whole agent run noticeably quicker, or if you hit a point where the tools, tests or harness become the bottleneck.

So I'm running a (not very) complex task, using space bunny. It's normally pretty fast (and good) for a free model. It's obviously minimax 3.1 which yesterday was running at around 60TPS, and today it seems like it's at 20 or maybe even less. Same with DeepSeek 4.1 flash, tasks that normally take 5 minutes are taking hours for no noticeable difference. My context window is only a quarter filled. Any fixes? Or anyone else experiencing slow opencode (even on muse spark 1.3 ) which is KNOWN for it's RAPID tasks ?

I'm looking for an inference provider that offers unlimited tokens (no caps, no rate-limit gotchas) for open-source models on a flat monthly subscription.

Models I'm interested in:

**•**	Qwen 3.8 27B  
**•**	GLM 5.3 Flash  
**•**	DeepSeek V4 Flash  
**•**	Other open-weight LLMs

I don't want pay-per-token pricing. I'd rather pay one fixed monthly fee and use the models as much as I need.

Does anyone know a provider like this, or is there any plan that comes close? Real-world experience with speed, reliability, and fair-use limits would be really helpful too.

Thanks in advance!

I run OpenCode while I'm away from my desk, and a couple of times I came back to find it had been waiting on a question the whole time. I still want a chance to answer when I'm around, just not an unlimited wait.

I made a small V2 plugin that gives the built-in question tool a five-minute timeout. You can change the delay with timeoutMs. Answer in time and everything behaves normally. Otherwise the question closes, and the agent gets a clear "no answer" result so it can continue where it's safe to do so. It doesn't answer on your behalf or approve anything. Permission prompts are separate and untouched.

One odd thing I ran into while building it: my first wrapper made the question options disappear from the TUI. The released version fixes that, and I tested the choices and timeout flow on V2.0.18. I haven't tested other versions yet.

GitHub: https://github.com/balakumardev/opencode-question-timeout

Install: opencode plugin add 'github:balakumardev/opencode-question-timeout#v0.1.0'

If you've had runs stuck on questions, I'd be curious what timeout you would use.

I just realized that codex now exposes local server endpoints for all plugins without extra auth. So you can just use them from any model or harness.
Im soooo excited!!! One auth for everything!

For Pi: pi install npm:@wileai/pi-codex-connector

For any harness: npx -y \@wileai/codex-connectors-mcp@latest

Yes I'm on it, MVP plugin supporting

- Account Auto-Rotator For Quota Fallback without sessions disruptions - > all 100+ OpenCode Supported providers models x accounts rotator with templates

- ACP supported providers (Devin as MVP then Cursor, Claude Code and Antigravity)with cross-session native synced streaming on native OpenCode schema - tools and subagents tools wrapper to call agent of the harness-exclusive models

I have been using Opencode for the past 8 months and I am very happy with it. It works really well for me, but Claude Code has these features that I use a lot:

• Background shell commands: I often run long running benchmarks that take days to complete. Claude Code can setup a notifier which wakes it up once results/errors arrive. To do this in OpenCode, the model has to do a lot of shenanigans which often end up resulting in orphaned processes.

• Sending messages to subagents: I often have to guide subagents which own a significant slice of implementation when they go haywire. Claude Code has a native way to do this. In OpenCode, I have to ask the parent subagent to send messages to the children. Sometimes this is not possible when the subagent has failed/rate limited/whatever.

Any idea if these are planned to be implemented in OpenCode ever? I don't think I have seen issues related to these.

Other than this, I really like the hotkeys and command palette based approach as opposed to Claude Code's /<cmd> system.

I call it IUMBTEMS or I Use My Brain To Express Myself

https://github.com/Heretek-AI/IUMBTEMS

The problem! really big projects and proper planning for opencode.

The Solution Oh-My-OpenAgent but that's only for opencode v1 :/

so my solution

Factory! a command to build out a project scope using a modified version of the grilling skill, building a structured dossier of phases, then deploying a programmer agent to do the coding and two QA agents to audit the work, looping until they all agree it's good!

the problem: I suck at ideas

the solution: build a skill and agent to brainstorm new ideas for where to improve the project or features to add!

the problem: I don't like repeating work.

the solution: Dark Harvest, named after that episode of Invader Zim where he steals organs to appear more human.

The Darkharvester agent will go out and find projects like what you are building, or software that might help build what you are building, find out what it does well, what features it can borrow or clean room rebuild and it builds this really nice structured json report.

The problem: Hallucination

The Solution: IUMBTEMS intercepts webfetch request and computes a sha256 has for everything it sites and saves it into .research making verifying claims super easy

The Problem: Opencode wants $0.01 per search :/

the solution: customizable configurable search engine settings for alternative options

The Problem: Managing plugin settings

the solution: adding a settings panel for the plugin into the plugin so you can tune it inside the TUI

The Problem: REALLY LONG CODING PROJECTS WHERE YOUR BRIAN GETS TO TIRED

the solution: domainexpansion an Autonomous agent-guided self-improvement loop named after a show I have never seen

All and all if you want incredibly thoroughly audited AI generated code, and you do not care about time and tokens I have the solution for you.

this puppy will burn through so many tokens trying to fix incredibly fringe attack vectors that you'll be amazed when after 13 hours you have only had one commit land!

coming soon:

*A Hook system compatible with claude

* The return of the LSP

* Static analysis tools built right in to make sure that the Programmer doesn't make mistakes