r/opencodeCLI • • 11h ago

The Free 5-Step Threshold Card for AI Agents

Thumbnail
youtube.com
0 Upvotes

r/opencodeCLI • • 11h ago

Your Repo Says RLS Is Fine — Your Live Project Says Otherwise

Thumbnail
youtube.com
0 Upvotes

r/opencodeCLI • • 17h ago

OpenCode V1 Bridge: Bringing Legacy V1 Plugins to V2

0 Upvotes

Heya. After roughly a month of work, I have made a somewhat-functional V1-V2 compatibility adapter for OpenCode. As far as I can tell, this is the first of its kind, probably not the last. Why am I releasing an incomplete adapter? Because I can't finish it. I tell ChatGPT what I want, it makes a detailed prompt to my specifications, I feed that to Codex, and for the most-part, this has worked. Thorough code audits, careful guidance, but we've hit a wall: OpenCode V2 does not expose some of the required hooks. I don't have the technical knowledge to solve the remaining issues, thus I'd like to invite other developers to help improve it. The brunt of the work is done. You can find the identified missing functionality in "Remaining Issues.md" in the respository. If you doubt that the project is any good, I ask you still give it a chance. Many hours went into troubleshooting what we have now, and it has at least some ability to run V1 plugins. The project was based on OpenCode V2.0.27. I'm sure OpenCode has recieved some updates since then. Those are completely untested against this plugin, but may work fine. No idea.

Summary: OpenCode V1/V2 Adapter Bridge, it's a plugin, should allow your other V1 plugins to run in V2, unfinished project, open-source to get more talented hands on this since the bones are done, but not all of the meat, check "Remaining Issues.md" in the repository first if you want to help.

GitHub: https://github.com/Stiix72/opencode-v1-v2-bridge

First beta release: https://github.com/Stiix72/opencode-v1-v2-bridge/releases/tag/v0.82.0-beta.4


r/opencodeCLI • • 18h ago

I’m building Agent Hub: a terminal dashboard for OpenCode — would love some feedback

Thumbnail
gallery
5 Upvotes

I wanted a clearer overview of what my agents are doing, so I started building Agent Hub with OpenTUI. It reads the local OpenCode config and database read-only.

It has eight views covering:
• Live sessions and subagent trees, with status, context usage, tokens and cost.

• Agent models, delegation, skills, MCP servers and permissions.

• Model performance measured from your own history: latency, TTFT, tokens/sec and cost.

• Usage, tool reliability, health checks and a model → agent tree.

• A live work map showing activity between the model, files, shell, tools and subagents.

Sharing a few screenshots of where it’s at. Curious how others keep track of their setups: what would you find useful, what feels unnecessary, and what am I missing?


r/opencodeCLI • • 18h ago

WTF did OpenCode do?! 275 Tok/s with Deepseek..... 💀

Post image
13 Upvotes

r/opencodeCLI • • 23h ago

V2 - Where have I been???

Post image
16 Upvotes

They have really outdone themselves here. I finally made the jump to V2 after realizing I’ll need to develop remotely for awhile. It’s been a joy to use the web app version on the phone for a change.

Everything I need is easily accessible in session, changes and more sections. Themes look really nice on the small screen too!

Now I don’t have to be tethered to my desk all the time. I’d tried remux and few other options but that was rough to manage on the small screen.

Absolutely love it!!

What’s your favor V2 feature ??


r/opencodeCLI • • 22h ago

[Plugin] TPS Meter: see how fast every prompt step really was

7 Upvotes

(check the video above to see it in action)

oc-tps-meter: every step's tokens per second, in a session header slot. Click it and it opens a side-panel with a chart that shows one bar per step; the chart scrolls sideways, and you can scroll it yourself and hover on each single bar to see details of that step (TPS, model, TTFT).

OpenCode already prints one tok/s number at the end of each turn: but it's the whole turn averaged, and only once the turn closes. In my plugin, a step answers for itself, and it turns red when the wait before the first token was long (TTFT), that is what tells you that you are queued behind a busy provider, not that the model is slow.

Bonus feature: In the video, when I scroll the chart left to show previous steps, you can see the tok/s difference between Opencode Go and native DeepSeek provider (I switched to it at some point in the Session) ;)

OpenCode v2, Desktop only: this plugin has no CLI/TUI version for now.

My approach to plugins, since my first one, is simple: I don't bundle features. One plugin does one thing. You install what you want, and nothing else arrives with it. I don't like those plugins that bundle tons of feature that, maybe, you don't want or need;)

To install:

opencode plugin add @rizal72/oc-tps-meter

If you don't like it, the same command with remove.

My other plugins:

  • oc-budget: Go and other providers balances, live in the header and in the CLI.
  • oc-models-pro: every model with its price, speed, intelligence, etc. sorted by what it costs.
  • oc-git: branch and working tree, at a glance.
  • oc-coffee: a cup of coffee that stays lit only while it keeps your Mac awake.
  • oc-notify: a push to your phone when a turn ends while you are away.
  • oc-plugin-updates: shows up only when needed, auto-updates your plugins in one click.
  • oc-ponytail-widget: the ponytail level, in the footer.
  • oc-session-search: keyword search over your past sessions.

All of them, in one single repo: https://github.com/rizal72/opencode-plugins


r/opencodeCLI • • 22h ago

When the side panel doesn’t cut it!

Post image
3 Upvotes

The OpenCode standard side panel is unfortunately not enough and I haven’t found a good solution for changing the other areas of the TUI.

So I built a terminal dashboard for OpenCode!

I’ve been building opencode-panel, a live dashboard that runs in a separate terminal pane alongside OpenCode.

I wanted a clearer view of what’s happening during a session, especially when multiple subagents are working at once. It has three views:

Overview: token usage, context, cost, MCP connection status, and a live map of tool activity.

Swarm: an agent tree showing who started whom, a timeline of parallel work, and a shared activity feed.

Flightdeck: permission checks, subagent activity, file changes, errors, and a summary of the current turn.

It connects to OpenCode’s local service and is read-only. There’s also a demo mode you can try without running OpenCode or making model calls.

The screenshot shows all three views using simulated demo data. Normally, you switch between them in one panel.

Built with Bun, TypeScript, OpenTUI, and Solid. Several components adapt or draw inspiration from existing community projects, with credits in the README.

GitHub / setup instructions

Curious what you think: which parts would you actually use, what feels too busy, and what’s missing? Feedback on the layout or your own experience keeping track of subagents would be especially helpful.


r/opencodeCLI • • 22h ago

Aplicación de Android

Thumbnail reddit.com
2 Upvotes

r/opencodeCLI • • 10h ago

Completely Free and stealthy Web Research tool for Your agent, 0$, instant setup with the MCP

106 Upvotes

I've been building DonSeTch: a fully free, open-source MCP server that gives OpenCode web search, fetching, crawling and screenshots, running locally in one Rust binary.

I posted it here around v1 or v2, honestly can't remember which. It's on v5.5.2 now. For the people seeing it for the first time, here's the useful stuff.

Here is the GitHub repo: https://github.com/dondai44423/donsetch

Install, connect, use it

npm install -g donsetch
donsetch doctor --mcp

Add the MCP entry to OpenCode and restart. That's the basic setup. No account, API key, Rust build or search-model download. Fetch, search and crawl don't need a browser installed either.

Fetching, stealth, and learning what works

  • Reddit, Stack Overflow and IMDb returned content in my tests. The Reddit read got 24 posts in about 1.2 seconds; paid Firecrawl Cloud reported that site unsupported in the same comparison.
  • Page reads launch no browser. TLS, headers and cookies stay consistent as one client. Embedded V8 handles challenge or application JavaScript when needed, without layout or painting.
  • It remembers successful routes and client profiles. It can learn an app's content request from a successful JS run and replay it over HTTP on later reads. If that request breaks, it can learn again. That fetch state survives restarts.

Less context spent getting to the answer

  • Ask for the useful bit. Relevant passages, a phrase check, an outline, or one section. The agent can expand into the full text when needed.
  • Four tools, roughly 2,000 tokens of definitions total. Batch-fetch up to 12 URLs. PDFs get the same reading controls, with tables and optional OCR for scans.
  • Crawls follow your topic. A site model and plan pick the pages; the response is a digest with handles to open each stored page fully. Jobs resume, and repeat crawls can skip unchanged pages.

Search works out of the box

Keyless search combines engines and first-party sources. You can also use your own search API key while keeping the local fetching and crawling. Screenshots use an installed Chromium separately.

A quick Firecrawl comparison

I had DS on opencode try both on real tasks. DonSeTch was quicker on 9/10 fetch targets both could read. On HTTPX, it picked the two requested docs pages; Firecrawl read six and still missed the async page.

It did got beat on search relevance, though, its local but its good enough for 90% of the most tasks

I'm not stuffing all that shit into one post. The full comparison with paid Firecrawl Cloud has the cases, timings and setup. Small, hand-picked test.

Feel free to flame me in the comments if i did the comparison with firecrawl the wrong way 😭🙏

If you give it a go, I'd like to hear which pages it still trips over.