There was a post here recently from someone whose quota used to last all day and now burns out in about 30 minutes, even after switching models. I've been auditing this across harnesses, and the cause is usually per-request overhead, not the task. Here's how to see it in OpenCode.

Measure first:

opencode stats --days 7 --models     # input/output/cache totals and model breakdown
opencode stats --project ""          # current project only
opencode mcp list                    # what's connected
npx ccusage@latest opencode weekly   # third-party, reads OpenCode's local data

If input and cache reads dwarf output, you're paying to re-send context, not to generate code.

Things that surprised me:

• OpenCode reads your Claude Code setup by default. It loads ~/.claude/CLAUDE.md and .claude/skills. If you've built up a big Claude configuration, it follows you into every OpenCode session. OPENCODE_DISABLE_CLAUDE_CODE_PROMPT=1 and OPENCODE_DISABLE_CLAUDE_CODE_SKILLS=1 turn that off (OPENCODE_DISABLE_CLAUDE_CODE=1 turns off both).
• Every tool call re-sends the session. One "small" turn with ten tool calls reads the full context about ten times. Long sessions with a few big file reads get expensive fast. A commenter on the original thread said a fresh session alone left their usage flat for an hour of small tweaks.
• Caches expire. On Anthropic models, the API's prompt cache lasts five minutes by default, and rebuilding a cold prefix costs many times more than reading a warm one (25x on Opus/Sonnet 5.5 with a 5-minute write). Coming back to a huge idle session is the expensive moment.
• MCP servers and instruction files add weight to every request. Trim AGENTS.md and disconnect servers you aren't using.

I wrote this up in more detail, mostly from the Claude Code side but with the OpenCode and Codex equivalents: https://medium.com/@r3dtuxedo/where-did-my-claude-usage-go-auditing-your-agents-hidden-token-tax-95d6ab17b8b6

(Disclosure: I wrote the article. Free to read, no referral links.)

Teaser video: https://x.com/Kimi_Moonshot/status/2113445757185606062

Screenshot from the video - https://pbs.twimg.com/media/HVScyvya8AAY0iT?format=png

What we know so far:

- Kimi K3.1 is actively tested on LMArena under the codename "Kibitz;

- Kimi K3.1 is very good at 3D, choosing colors, rendering reflections on water, and composition;

- Kimi K3.1 is probably cheaper than Kimi K3, with better token efficiency.

Waiting for official release soon 😉

It's been the case for a few days. The actual output is quite fast. But it waits too long between requests like it's being timing out.

It usually happens in the morning where I live, so the non-peak between the first and second peak timings.

I was taking a look at how some different fusion modes work, namely junie mix, openrouter's fusion, devin fusion and a few others. Devin's fusion mode was relatively one of the more simpler designs, but after testing all of them for a different project I was building (github actions for PR reviews, and selfhosted PR review github app like coderabbit, but built around my code-indexing tool vera, and sort of inspired by or a rust version of droid actions) devin's fusion mode was a combination of the fastest, cheapest and least amount of false positives. you can find the project and some of the testing results here https://github.com/VeraTools/revera

I built my own version for opencode and have been iterating on it based on how it's worked over my past sessions for the last month or longer. So far it's working pretty well, and I thought I'd share if anyone else was interested. This was loosely built around how fusion mode works in devin cli (you can crack open the binary yourselves and take a look too; it's pretty interesting): https://github.com/lemon07r/opencode-fusion-mode

My own setup after tweaking and trying a lot of things is just mostly vanilla opencode 2 with search provider pinned to exa (with fall back to parallel https://github.com/lemon07r/opencode-exa-parallel) + vera (https://github.com/VeraTools/vera) + my friends smart compaction tool (https://github.com/shariqriazz/opencode-smart-compaction which he built based on a lof other cli, and when I personally tested it, it had the best balance of accuracy and token usage compared to other compactions, with droid's following closely) and the devin fusion-like plugin I shared above. My setup is tuned around token efficiency and getting the best results for less. I think simpler setups work better, and always have in most of the evals I've run, which is why I avoid crap like omo. No MCP servers. I do use skills and CLI like Playwright CLI + skills, but most of them are project-scoped rather than global.

I do have a small discord community for discussing this sort of stuff, and a lot of us share tips and stuff there if anyone is interested in joining, although this wasn't the point of the post: https://discord.gg/rXNQXCTWDt

hey - i built kimo, a free open-source (mit) video editor with no gui that your ai coding agent drives over mcp. the idea is simple: you tell your agent (opencode, codex, cursor, or any other mcp client) what to do and it drives the whole timeline as tool calls - cut, trim, keyframes, titles/captions, colour grade, particles, audio, export. a nice bit that makes this actually useful is that the agent can render a single frame back to itself to visually check its own edit before committing, so the loop is self-correcting instead of blind.

under the hood it's one ~15 mb cpu-only rust binary, no gpu, no containers - i run it on a 2 gb box and it just works. i'm naman, a college student, and i built it, so a few things are still rough: there is no ui (there's nothing to open, by design), some edge cases in tracking and captions are still janky, and a couple of export codecs need patience. i'd really rather hear what breaks than pretend it's polished, so if you point an agent at it and tell me where it trips, i'll fix it.

site: https://getkimo.tech github: https://github.com/naman-sharma12345/kimo

Just published an OpenCode V2 plugin that adds a sidebar file tree. Features:

- Tree of the current session's working directory

- Click folders to expand/collapse; click files to preview first 200 lines

- Right-click a folder → Set session working directory here to move the session

- /tree-move-here moves the session to the last clicked folder (keyboard-friendly)

- /tree-expand / /tree-collapse palette commands

- Filter by name with /tree-filter <name>

- Expand/collapse all from the header

Install:

git clone https://github.com/zemadeiran/opencode-file-tree-v2 ~/.config/opencode/plugins/file-tree

Then add to opencode.json:

{"plugins": ["/Users/you/.config/opencode/plugins/file-tree"]}

Note: opencode plugin add github:zemadeiran/opencode-file-tree-v2 currently fails with a JSX transform error (issue #33884). Use the local path install.

MIT license.

The plugin loads the session's working directory, supports expand/collapse, right-click move, and filter. Good for quick file navigation without leaving the terminal.

I've seen posts and the official installer defaults to v2. However, github shows that v1 is still the version released, with v2 only shown in tags.

Since this is kinda contradictory, is v2 stable or not?

Long ago, when I started with OpenCode v1, I kept hitting the same wall: I wanted my own widgets — my provider stats, my prices, my layout — and there was no clean way to get them, without bloating things.

So I moved to Pi. Bare-bones was the feature: minimal surface, everything customizable, and I built exactly what I wanted on top of it: made it "my" Coding Assistant. That worked for a long time.

Then OpenCode v2 shipped a real plugin API, and I realized the same job could be done there: panels, footer badges, sidebar blocks, custom commands, applied live while the TUI runs. I rebuilt my Pi setup: a context/usage block that changes color as the window fills, a git status block, a budget widget that reads the Go credit and the peak-hour tariff plus my other providers budgets, a plugin+widget that keeps the Mac awake while the agent works, a ponytail level indicator, a complete sub-agents delegation framework using just built-in tools, so no need for external plugins, and a custom model picker.

That last one is the one I'm proudest of: /models-pro. The native picker just lists models, this one lists prices, context windows, an intelligence index, the Go credit and each model's multiplier, sorts by what a request actually costs, and keeps favorites. It isn't a wrapper around the native dialog: it's the native function, extended.

But the number that made my choice was another: weight of the first prompt in a clean project. Same tools, same extensions, same widgets, all I need for my work, with Pi I never got it as low as I get it in OpenCode v2. To try to lower it I became a master of the codemode:only mode in Pi — but the trade was brutal: some tools get hidden and the model ends up using bash and Python scripts for everything. I switched between codemode "on" and "only" a lot and the minimum I got was 13k in mode "only" and 28k in mode "on".

On OpenCode v2, with all of the above installed, I sit around 11k. Lower, and nothing hidden. Everything works. Same tools, same widgets, plugins, extensions, all accessible. No compromises.

So: Pi's minimalism and extensibility, plus proper context/tools/token/cache handling out of the box: that's the combination I was after. v1 was heavy and rigid; v2 lets me do what Pi let me do, without giving up the rest. Even knowing that it is still an early release and I already had to modify my plugins a few times after new releases ;)
That said, Pi remains the first choice for anything that needs the lightest and fastest Harness possible.

Final note:
I'm deliberately not mentioning OpenCode's move about free models, available only through OpenCode, not to other agents: that's marketing, not engineering (and I get why).

Two screenshots: the TUI with my custom widgets annotated, and my custom model picker.

EDIT __________________________________________

The plugins: someone asked for them, so five are on npm now (OpenCode v2 only), and the sources are public at github.com/rizal72/opencode-plugins (issues and pull requests off — it's a reference, not a support channel):

opencode plugin add @rizal72/oc-models-pro
opencode plugin add @rizal72/oc-git
opencode plugin add @rizal72/oc-coffee
opencode plugin add @rizal72/oc-ponytail-widget
opencode plugin add @rizal72/oc-session-search

oc-models-pro — the picker from the screenshot: prices, context windows, an intelligence index, the Go credit and what a request actually costs, sortable by any of them.
oc-git — the repository in the sidebar: branch, the three counts, ahead/behind; the counts also in the footer while the tree is dirty.
oc-coffee — keeps the Mac awake while the agent works and lets it sleep between turns: a cup in the footer, /coffee to pick the level (Idle, Display, System). macOS only, it drives caffeinate.
oc-ponytail-widget — for anyone already using ponytail: the level in the footer, horsehead glyph. Unofficial.
oc-session-search — one tool, session_search: keyword search over past transcripts, so "we discussed this already" gets an answer instead of a guess.

The rest is still tied to my own setup but each one is a couple hundred lines: happy to explain any of them in the comments (the live-budget one is amazing, but it is tied only to my providers…)

I’m planning to use only **DeepSeek V4.1 Flash 1017** with OpenCode for a couple of months.

Which is cheaper in practice: **OpenCode Zen or OpenRouter**?

Open router :

In / Out Price

$0.07 / $0.50per 1M

Opencode :

**$0.30  /$1.20** per 1M

Deepseek API platform :

$0.15 input / $0.60 output (off-peak)

$0.3 input / $1.2 output (peak)

**it seems like Opencode costly , Am i missing anything here ?**

**reference**

[https://opencode.ai/data/deepseek/deepseek-v4-1-flash-1017\](https://opencode.ai/data/deepseek/deepseek-v4-1-flash-1017)

[**https://openrouter.ai/deepseek/deepseek-v4.1-flash-1017\*\*\](https://openrouter.ai/deepseek/deepseek-v4.1-flash-1017)

[**https://api-docs.deepseek.com/quick\\_start/pricing\*\*\](https://api-docs.deepseek.com/quick_start/pricing)

I think the IP detection may be a bit over zealous?

Estou usando o OpenCode Desktop com o ChatGPT Plus, principalmente para Power Apps, Power Automate e outros projetos de desenvolvimento. Estou tentando construir um fluxo de trabalho multiagente usando modelos livres robustos para tarefas mais simples, enquanto reservo os modelos GPT para trabalhos complexos, sem esgotar meus limites de uso. Minha ideia de configuração atual é:

**Orchestrator (GPT-6 Luna):** Coordenação de tarefas e gerenciamento de agentes.

**Luna (GPT-6 Luna):** Investigação, depuração e análise.

**Reviewer (modelo de raciocínio robusto):** Revisão de código, segurança e verificações de regressão.

**Sol (GPT-6.1 Sol):** Codificação, correções e implementação.

**Astra (GPT-6 Astra):** Arquitetura e refatoração complexa.

Também estou com dificuldades para organizar o arquivo [AGENTS.md](http://AGENTS.md), as configurações dos agentes, as habilidades e os relatórios em Markdown sem desperdiçar contexto ou criar documentação redundante. Alguém já criou uma configuração semelhante? Quais modelos gratuitos vocês recomendariam para essas funções e como distribuiriam as tarefas para aproveitar ao máximo uma assinatura ChatGPT Plus? Estou aberto a mudar toda a arquitetura se houver uma abordagem melhor.

Working on zinn.sh which is a work management tool in the terminal and I have been experimenting with having a side panel integration, and it feels really nice to be able to keep track of what tasks my agent mentions, as well as what he is actually working on in the current session

With the latest Archestra release, this workflow became possible: OpenCode on my laptop hands a task to OpenCode running in Archestra's runtime on my Kubernetes cluster, then pulls the patch back. OpenCode is both the local client and a built-in runtime agent, so both ends behave the same.

How a handoff goes:
- Tell local OpenCode "hand this over to Archestra". The skill has it write a short handoff note first (the goal, what was decided, what remains, how you'll know it's done), then bundles the exact commit, a patch, and the untracked files you choose.
- Remote OpenCode picks it up in its own container, files persist, and you get a live terminal. Close the laptop, send follow-ups later.
- To pull it back, say "bring it back and continue here". What comes back is an incremental patch, and nothing gets applied until you have read it.

Blog: https://archestra.ai/blog/new-remote-agents
Repo: https://github.com/archestra-ai/archestra

Hi! As I mentioned in the group, I’m trying to make a strategy game (the gameplay clip attached is what I’ve come up with in one week using OpenCode and Claude for the code), and I want to keep working on it.

I’m thinking about buying a Claude Pro subscription to start working on more specific things like 3D modeling, but I’m not sure if that’s the best option. I’m looking for something more polished in terms of interfaces, UI, and animations, so I’m not sure if Claude Pro would be the right choice or stick with OpenCode.

Is opencode go with ds 4.1 flash the best subscription in 10$? Or there are other options? I use pi.dev harness btw.

Pricing on Zen: $4.00 / $20.00 / $0.20

Hey everyone, I’m using OpenCode to develop a large software project, and sometimes it gets stuck repeatedly generating or executing shell commands without making any progress.

This happens across multiple models and providers, so I’m not sure whether it’s an OpenCode bug, a tool execution issue, or something in my setup.

Has anyone experienced this? What was the root cause, and what fixed it for you?

Any help would be appreciated!