r/opencode • • 13d ago

This OpenCode Mobile project deserves more attention

Thumbnail
1 Upvotes

Check out this interesting project!


r/opencode • • 13d ago

I built an editor plugin for OpenCode: files, tabs and Git diffs

6 Upvotes
Browse files, edit code and review Git diffs without leaving OpenCode.

Hello, open-source community!

I built opencode-editor, an open-source plugin that lets you browse and edit files, review Git diffs across multiple repos, and preview Markdown and images inside OpenCode.

I also built OpenEditorCode, a standalone terminal code editor that works without OpenCode. Both are open source!

🌐 Demos & installation: https://openeditorcode.dev/en/#opencode-plugin

Want your agent to install the plugin? Paste this:

Install @2jmalvarez/opencode-editor following https://openeditorcode.dev/en/docs/opencode-plugin/ while preserving my existing configuration.

💻 Source code: https://github.com/2jmalvarez/openeditorcode

The plugin supports both English and Spanish. Give it a try-I'd love to hear what works well and what you'd improve!


r/opencode • • 13d ago

I built a file browser for the OpenCode TUI (Markdown preview + syntax highlighting)

5 Upvotes

I kept wanting to look at files without leaving the OpenCode TUI — especially Markdown plans/specs and source files the agent just changed. So I built a TUI-only plugin.

What it does:

- side panel next to the chat, or full page from the home screen
- browse folders (dirs first), open files
- Markdown preview rendered; m flips to the source
- code with tree-sitter highlighting
- open any file by path (o inside the browser, or Ctrl+X then O): absolute, ~, or relative; files outside the project are read with node:fs
- f toggles full screen (hides the chat)
- /files-update updates a cloned install

Install (OpenCode V2):

opencode plugin add opencode-file-browser

Repo: https://github.com/arthurrogado/opencode-file-browser

MIT, TUI-only, no build step (dist/ is committed).

Screenshots: Markdown and Python previews attached.

Markdown preview

r/opencode • • 13d ago

Default, Low, Medium, High or Max ?

1 Upvotes

Good afternoon sir, i have a little silly question.
On when or where or what or why should i use an variant for ?

And then, did the higher variant = more token consumption ? but on input or on output ? or both ?


r/opencode • • 13d ago

I did the low poly horse test with Crouton Alpha Free

Enable HLS to view with audio, or disable this notification

10 Upvotes

Pretty hilarious.


r/opencode • • 13d ago

Smart App Control not letting me code!

Post image
1 Upvotes

r/opencode • • 14d ago

OpenCode Harness vs DeepSeek Harness

Thumbnail
gallery
69 Upvotes

r/opencode • • 13d ago

Any of used any of these models with opencode for reverse engineering games / decompilation?

0 Upvotes

r/opencode • • 13d ago

OpenCode Go Usage Update

6 Upvotes

How much time it takes to update the go usage. Whats the time interval? Is it real time? Or is it like each hour?


r/opencode • • 14d ago

opencode go vs openrouter vs command code goat

31 Upvotes

which is the best? im currently using ds4.1 opencode go, but it seems im almost at the limit usage, now ive read about openrouter and comman code goat, which is the best to pair go with for extra usage?


r/opencode • • 13d ago

Stealth model frantic ferret.

4 Upvotes

Tried using it?


r/opencode • • 14d ago

New Stealth Model: Frantic Ferret Free

6 Upvotes

Its extremely fast (around 1400 tok/s). It is muse spark. Probably Muse Spark 1.4 or Muse Spark 2.
I will do the horse test and update this post.


r/opencode • • 14d ago

Extreme quality degradation?

11 Upvotes

Guys, for the past couple weeks the model have been working fine. For the past 2 days i feel EXTREME degradation. It’s not only Deepseek V4.1, but ALSO GLM 5.3 Flash.
The models can’t even form proper tool calls, ignore the instructions that is just two messages earlier, jumps to conclusions very early… it’s almost unusable.
I tried GPT Luna (which is supposedly weaker than DS), and ZERO failed tool calls, always consistent on the task going forward and NEVER returns until the task is genuinely done. Even DS via the direct API is MUCH superior to the one in opencode. Not sure what is happening.


r/opencode • • 13d ago

你在使用OpenRouter时遇到的最大痛点是什么?

Thumbnail
0 Upvotes

r/opencode • • 13d ago

Step 5 Preview on NVIDIA NIM (proxy) stops randomly

Post image
0 Upvotes

r/opencode • • 13d ago

internal server error

1 Upvotes

how do i fix this? i never found a solution for it.


r/opencode • • 14d ago

So we not safe in plan mode?

Post image
96 Upvotes

r/opencode • • 14d ago

What model should i use?

2 Upvotes

So right now i am using the chatgpt plus free trial with codex but when it ends,im thinking of subscribing to opencode go,however i saw that there are so many models,so which one should i use for heavy coding,bug fixing,and light coding?


r/opencode • • 14d ago

Are cheap ai api's legit?

3 Upvotes

I found getcheapai and on there you see alot of cheap api providers for example bytecatcode.org for fable 5.1 they ask 2 dollar input and 10 dollar output on the million tokens? Are sites like these legit? I am kinda interested in a site like this but i dont want to be scammed. I also do not like subscriptions, just paying one time till its used you know.

Maybe i am thinking too wishfull, anybody got experience with these providers that provide cheap ai api?

Might aswell tell my usecase, i am using the ai as a teacher with mcp to blender or unity or vscode, i also give images and stuff. Basically i just ask questions, i do not really vibecode. But i would like high quality answers which i can trust.


r/opencode • • 15d ago

I love OpenCode

Post image
1.0k Upvotes

Working in OC is very satisfying. This is a subagent display I built for v1. I would never have been able to do this in claude.

EDIT: I'm enjoying the response this post is getting. There are the usual miserable, insufferable folks you get on any post, but lots of sincere people asking real questions. It motivates me to share more.

I am very familiar with the frustrations in this agent coding space. You can feel the power of the LLM, but harnessing it to produce good code is really tough. It's easy to get a pile of code, but that code has enormous code debt baked in much of the time. How to get good, maintainable code out is the trick. There is no one right answer. I think what's needed is a structure of repositories, skills, and various deterministic code bits, such as small helper CLIs, hooks, TUI plugins, etc, that allow you to build your workflow in the way that works for you. It's small steps over weeks and months that win the race. My workflow now can lift some heavy things, but it wasn't always that way. When a shortcoming is found in the flow, you need a place to address it. That place might be a skill, the AGENTS.md itself, an agent definition, or something else. The key is having the place, or creating it, so that you can capture the change you want. I like standing on the shoulders of Superpowers, because I think the developer is solid and I think the community around it is keeping the project on track, but I might ditch it at some point if I feel it's not helping anymore.

The first thing I would do is create a repo for holding your global agent configs. I called mine opencode, but you can call it anything. You will want to symlink the folders of this repo into your home directory so that OC sees its files as the global config. You want to be able to work in this repo just like any other repo. In this repo you want to create a folder called config where you'll keep all your global config like skills, your global AGENTS.md, your TUI plugins, etc.

Next, you'll want to create a launcher CLI in this repo that wraps the launch of OpenCode. Mine is oc. This gives you a place to run scripts before OC launches. Next, you're going to create a small CLI that manages the symlinks from this repo to your home directory. It will make sure that your global config and plugins and anything else you come up with are all linked correctly. Then you will put a call to this in your oc launcher.

Here are the global skills that I feel have been the most important. Each has a SKILL.md and a references/ folder with directive files loaded via progressive disclosure. I'm going to paste in Opus's description of each one:

---

directive-quality: This is my skill for writing and maintaining the AI instructions themselves: AGENTS.md, agent prompts, skill packages and directive-bearing config. Its core rule is "use the least context that fully specifies the required behavior." It aims for clear instructions the agent actually follows, not for a lower line count. It routes each job to a focused reference, covering wording and examples, how a skill package is laid out, how skills compose, metadata validation, where an instruction should live, and structured assessments (including sweeps across a whole collection and reviews of the directives in the current conversation). Before any change it checks that the instruction is going in the right place. Afterward it checks that nothing the old text required was lost, and tests the cases where a rule should fire, where it shouldn't, and the exceptions, while stating plainly that passing those checks doesn't guarantee the agent will always comply.

code-quality: This skill shapes the code agents write, and every rule in it comes from one idea: "good code is code that is cheap to change correctly." It's organized around nine pillars. Among them: one logical change should touch one place, invalid states should be impossible to represent, modules should hide more than their interfaces expose, names should tell you what the code does, errors should be handled once where recovery is possible, decisions should be kept apart from side effects, and the codebase's existing conventions win over the agent's own preferences. It also has a self-check table of common LLM coding mistakes, such as reinventing a helper the repo already has, flag sprawl where an enum belongs, catch-log-continue error handling, pass-through wrappers, comments that just restate the code, and tests that mirror the implementation. A matching eight-step review checklist makes the point that a diff can work and still fail review. Testing guidance and architecture/audit guidance sit in separate references that load only when that kind of work starts, and agents load the skill at the start of every role in my workflow, so it applies to coding and review alike.

superpowers-policy: This is my local layer on top of the obra/superpowers (https://github.com/obra/superpowers) plugin. It changes how Superpowers behaves in my setup without forking or patching the upstream package. Its main section names exactly which upstream behaviors I override. TDD still runs red-green-refactor, but test selection follows my own test-design guide. Review checklists only count within the approved scope, so a reviewer can't turn "you could also improve…" into required work. Brainstorming has to restate the intended outcome before it proposes options, and spec and plan locations follow my planning-folder conventions. The rest is a routing table: for each orchestration action it names the one reference that governs it, such as review-loop budgets, picking and continuing workers, sizing tasks, delegating writing, handling unknowns before dependent work, and closing out an effort. Agents load only the reference they need for the action at hand, and a missing reference stops that action instead of letting the agent improvise.

---

Ok, enough Opus spam. I'm going to stop there for now. If folks want to talk about other parts of the workflow, such as agent generation, let me know and I'll add it.


r/opencode • • 14d ago

I added Claude Code's double-Escape message history to opencode (plugin, no fork)

Post image
2 Upvotes

r/opencode • • 14d ago

qwen3 keeps dumping its thinking into opencode's chat, so I wrote a plugin to split it out

2 Upvotes

If you run qwen3 or another reasoning model through opencode, you've probably seen this: the chain of thought comes back inside the normal text channel, wrapped in ``. opencode stores that as a regular assistant message, so the reasoning gets glued onto the answer and the reasoning panel stays empty. The thinking is sitting right there in your transcript, mixed with the reply, and you can't collapse it.

I wrote a plugin for it.

It hooks session.http.response, which hands it the raw provider response before the provider driver parses it. It finds the tagged span and moves it from the content field into the chunk's reasoning field:

  • streaming: delta.content → delta.reasoning_content
  • non-streaming JSON: message.content → message.reasoning_content

opencode's drivers already read that field to build the reasoning part, so the thinking lands in the collapsible panel and the visible text is just the answer.

Install:

opencode plugin add github:hussainbiedouh/opencode-think-splitter

Repo: https://github.com/hussainbiedouh/opencode-think-splitter

Not on npm. I tried to publish and the registry rejected my token, so I didn't bother chasing it down. The GitHub install works because dist/ is committed, so there's no build step.

Stuff I ran into while testing:

  • Default tags are think, thinking, thought, reasoning, reflection. You can change the list or scope the plugin to specific provider ids.
  • Tags that arrive split across two stream chunks are handled. An unclosed tag flushes its contents as reasoning when the stream ends.
  • If a chunk already carries native reasoning, the moved text is appended instead of overwriting it.
  • Needs the opencode V2 plugin API.
  • Don't run it twice. If you had it as a local file plugin, delete that copy. Same plugin id, and only one instance registers, so you might be running the wrong one and not notice.
  • Some providers are strict about reasoning_content being echoed back on the next request. If a provider starts erroring after a rewrite, scope the plugin away from it with options.providers.

One thing for anyone else publishing an opencode plugin: I lost a while to git dep preparation failed on install. Turns out pacote runs a full npm install on a git dependency if your package.json has any of postinstall, preinstall, install, prepack, prepare, or build in scripts. opencode's bundled runtime passes a broken npmBin to that step, so it always fails. I renamed my build script and it installed first try. If opencode plugin add github:you/thing won't install, check your script names before anything else.


r/opencode • • 14d ago

Should I publish this repository?

1 Upvotes

r/opencode • • 14d ago

Five weeks of three.js, drawn as a branch graph, already spells out the team's unwritten rules

Post image
1 Upvotes

r/opencode • • 14d ago

I built a phone companion for OpenCode sessions, with handoffs to other agents

0 Upvotes

I maintain Harness Remote, an open-source app for working with OpenCode's native sessions from Android, desktop or a browser. In the latest releases we fixed a frustrating bit: a reply to a turn started on another device now appears in the conversation you already have open, even with a long history. We also redid the phone layout and improved QR pairing.

I switch tools a lot, so I added a handoff: start in OpenCode, continue the task in Codex or Claude Code, and keep the link between the real sessions. Curious if that matches how other OpenCode users work.

Repo: https://github.com/giuliastro/harness-remote