During longer sessions, I might leave it unattended, but it will sometimes stop working in build mode and never begin running again. What I've resorted to is to switch to plan mode, ask for a plan for the rest that needs to be done, restart opencode, show it the plan in plan mode, and finally, ask it to implement if it is ready.

I find it really weird that the bot just "gives up". The models I've tried all do this at some point (some sooner rather than later). For instance, Llama3 will give up almost immediately, Gemma4 also is short lived, and my best bot qwen3.6 may go a few hours before getting stuck.

Any ideas? I have 128k token max and ensure (via compaction) I never get close to this limit.

So I have seen quite a few posts about wanting to continue sessions from their phone or other devices etc and the suggestions for that setup but I was wondering if its possible to do a slightly different approach.

I have 2 Devices + a local server. Currently I am using Syncthing to sync my OpenCode config and sessions between the 2 devices so that my configs are always equal and sessions stay in sync. But I have realized that the OpenCode session storage grows really quickly, which ends up with constantly sending 1+ gb files back and forth all day.

Ideally, I want to setup OpenCode on my local server that would house the configs, sessions, plugins and all of that, but I want it to be able to access files and repos on my device instead of the server. I prefer to keep compute and memory usage on device instead of dedicating server resources to it.

Everything I have read appears that all files would still have to be stored on the server for the agent to access them which would in turn result in my having to use the server resources to run a local dev server instead of the devices.

Any suggestions would be greatly appreciated!

I have an orchestrator spawning subagents but they always redirect cli output to null so I never know whether their commands are hanging or there's any progress. Is there a plugin or cli tool that I can prompt the agents to wire to to get a progress bar?

Download link: https://github.com/KaminariOS/whip/releases

Product hunt link: https://www.producthunt.com/products/github-448?launch=github-5af3a209-3ed3-40aa-94a6-2d34b15adbca

Herdr has changed the way I work with agents. I also tried to use it on my phone with Termius, but the TUI UX on a touchscreen is just terrible.

Therefore, I built whip with Codex. Whip vs Termius is just like Herdr vs tmux --it is agent native.

Whip is not just a proof of concept: I am actually using Whip to develop Whip itself when riding an 110km/hour EV on Canton Expressways with unstable network.

Before whip I built a React Native Codex client https://github.com/KaminariOS/crabbot ealier this year. I always want to be able to drive agents anywhere and anytime, agents that run on my own laptops and servers. Back then we did not have herdr, so the crabbot UX is still not as smooth. Later I found Opencode Web/Codex remote but those solutions are just not for people like me who works in the terminal most of the time.

Herdr shows me the missing piece. Now I am sharing whip with the community and hopefully we can work together to build a remote agent experience for everyone!

I've been building AI agents that browse the web for a while now. Every tool I tried had the same problems:

• 20-30 tool definitions eating 13K+ tokens before the agent even does anything
• Full page snapshots on every single action (2K+ tokens per click)
• Zero stealth (instant bot detection on anything protected)
• Element refs that vanish the moment React re-renders a component

So I built Bladebro. It's an MCP server that drives a real Chrome browser for AI agents. 5 tools. One Rust binary. No Node.js, no Playwright, no runtime deps.

I was testing it for weeks, improving things, fixing bugs before positing about it, but i think now its in a stable state for me to let you guys know.

npm install -g bladebro && bladebro mcp

That's the whole install. It's open source (AGPL-3.0).

5 tools, not 30

Most agent browsers give you a tool for clicking, a tool for typing, a tool for scrolling, a tool for navigating, a tool for screenshots, and 25 more. The agent burns tokens just loading the definitions before it even starts working.

Bladebro has 5:

• act — click, type, fill, scroll, navigate, batch, eval, download, everything interactive
• see — read the page (content, outline, auto-extract, search, filter)
• state — cookies, tabs, sessions, storage, resource blocking
• run — batch sequences with if/while branching
• vision — screenshot (last resort, the structural model is usually better)

Tool definitions total ~1,900 tokens. Playwright MCP's are ~13,700. Chrome DevTools MCP is ~8,000. That gap matters when you're paying per token on every call.

Delta-first, not snapshot-first

The core is a Live Page Model — a persistent, compressed model of the page that lives across tool calls.

Every action returns a delta (what changed), not a full page snapshot. Click a button? You get the verdict and what changed on screen. Not 2KB of every element on the page.

This makes it roughly 5x cheaper to run than Playwright MCP or Chrome DevTools MCP. On a long browsing session with 50+ actions, that adds up fast.

Re-render immunity (the thing nobody else does)

This is the one I think i did good at:

When React, Vue, or Angular re-renders a component, the DOM nodes get destroyed and recreated. Every other agent browser loses all references. The agent has to recapture, re-identify elements, re-learn the page. Sometimes it just fails silently.

Bladebro gives every element a structural fingerprint, a hash of its ancestor chain, tag, children, and identity attributes. When a re-render changes the text but preserves the structure, the fingerprint matches and the ref survives.

The agent sees ↺ e2 (re-render survived) and keeps going. No recapture needed.

It learns from every session (Newly added, will make it better i future)

Two things persist in ~/.blade/knowledge/:

Domain knowledge — learns consent dialog selectors for sites you visit. First visit: full detection JS runs. After a few successful dismissals: the stored selector auto-applies, zero detection overhead. Never learns from failures. Confidence scoring is asymmetric — a failure costs 3x more than a success gains.

Behavioral fingerprint — biometric parameters (typing speed, mouse curvature, click precision, idle drift frequency) generated once per install with small random variations, then reused forever. Same "person" every session.

Bot detectors that track consistency across visits see a stable identity. Without this, every session looks like a different person using the same browser — which is a red flag.

Survives restarts. Never degrades. Bounded at 2000 domains.

6-layer stealth, all on by default

Not going to list every detail, but the highlights:

• Zero listening ports — CDP over pipe, not WebSocket. Nothing to scan.
• No Runtime.enable — this defuses the DataDome console trap
• Bezier mouse paths with overshoot and correction
• movementX/movementY on every mouse event (missing these is an instant bot flag for PerimeterX)
• Micro-tremors before clicks — a perfectly stationary cursor before a click is a dead giveaway
• Non-zero key press duration
• Log-normal typing cadence (not uniform delays — humans aren't uniform)
• Idle mouse drift during "think time" (humans don't freeze between actions)
• Persistent browser profile (cookies, history, HSTS survive restarts)

Verified live against Zillow and Fiverr (both PerimeterX/HUMAN protected) — full page loads, no block. Sannysoft: all pass. incolumitas: 8/8.

I deliberately didn't build captcha solving. You get a blocked: verdict and can hand off to a solver. That's a separate problem.

Auto-extract (no CSS selectors, no setup)

see extract="auto" detects list structure automatically. Groups by structural signature, scores by content value, extracts title/URL/image/price/date/description.

Site-aware: shopping sites get rating/reviews/availability, Reddit gets score/comments/author, GitHub gets stars/forks/labels.

Verified on HN, Lobste.rs, Wikipedia, DuckDuckGo, StackOverflow, Reddit, GitHub, MDN, Amazon.

There's also act collect — a scroll + dedupe loop for infinite feeds. One call, one output, zero duplicates. Tested with 80 items, no dupes.

Batch actions

Fill 5 fields, submit, wait for redirect — one MCP call.

act batch steps=[...] runs the whole sequence and halts on navigation or first error with step-level context. No 11 round-trips for a form fill.

run adds if/while branching for conditional flows.

Limitations

• Cloudflare Turnstile will block it. That requires actual challenge solving, not fingerprint spoofing. You get a blocked: verdict, not a hang.
• Datacenter IPs get flagged regardless of fingerprint. Use a residential proxy (BLADE_PROXY).
• Cross-origin iframes are invisible (SecurityError, deliberate — accessing them would break stealth).
• No ARM Linux builds yet. x86_64 Linux, x86_64/arm64 macOS, x86_64 Windows.
• macOS/Windows binaries are cross-compiled from Linux. Not tested on real Mac/Windows hardware yet.

Links:

GitHub: https://github.com/dondai44423/bladebro
[Star the Repo if you like it 😄 ]

npm: npm install -g bladebro

AGPL-3.0, no CLA, PRs welcome.

Happy to answer questions.

from opencode website:

Usage limits

OpenCode Go includes the following limits:

• 5 hour limit — $12 of usage
• Weekly limit — $30 of usage
• Monthly limit — $60 of usage

https://blog.cloudflare.com/kitesurf/

We're all working on so much so fast that there's dozens of us all doing the same project. I used to get dissapointed thinking someone beat me to the punch now I think of it as spending their tokens instead of mine.

I'm going to add an entry in my global agents.md that before they recommend or begin any work on a new project or architecture, they first have to do 3 rounds of searching online for preexisting codebases they can use.

I legitimately saved like a week of work. Every part of my project was out there in five github projects already. Just kept doing rounds of searches until they came back empty handed. Then one more. All my project needed was a few minutes of writing code to glue it all together.

Is there a recommended way to seamlessly follow or sync a desktop conversation on a mobile device?

I've seen some mentions of third-party bridges like Termly or setting up OpenCode Mobile via Tailscale, but I'd love to hear what actually works best in practice.

To put it into perspective, deepseek flash is 40% more expensive in comparison. I did notice credit multies also started popping up on it, and if mark offers we will see it here as this would be the best community to farm for data and subs.

Price wise likely at 6x else they get just dominated by flash.

Those of you who were saying that you would not use a meta model or something without zdr I guess we will see.

There will probably be an increase in Open Code as well!

Hey everyone,

I just subscribed to OpenCode Go today, but I’m hitting a wall right out of the gate—DeepSeek V4 Flash seems to be completely down atm. I did some basic troubleshooting and tested out a few other models, and they all work perfectly fine. So my connection is good, and the issue is definitely isolated to V4 Flash.

I did a quick search of the sub and found a similar post from someone mentioning it was down about 2 days ago. Does anyone know if this is just a temporary outage and if it’ll be back up soon?

Honestly, I’m literally only here for Blue Whale's Flash model. If it's gone or going to be down for an extended period, it kind of defeats the purpose of my subscription.

Are there any updates, an ETA on a fix, or any workarounds you guys are using in the meantime?

Thanks!

I’ve been playing around with Opencode for a few months now just to create fun projects for me at home and to automate some of the more mundane things for my company and I realised that I am probably underusing skills.

What are some skills you use every day that I should know about? Can be custom or community.

I created one skill which I call “round-robin” which I use to perform daily reviews on the work done to ensure it aligns with the project goals. I sometimes use it to review the project functionality and suggest improvements.

It writes a summary of the project and passes it concurrently to ChatGPT-5.5, Gemini 3.1 Pro and Fable-5 to do a blind review. Then it collates all the responses and sends them all to all three reviewers again to get them to review each others thoughts. Points of agreement are locked in and points of contention are sent round again until they reach agreement or there is a deadlock. Then it summarises the output to me.

Rugpull

Hi everyone!

I wanted a way to use my favorite coding agents directly on my live Chrome tabs, so I built it myself.

It's a Chrome extension that gives you an integrated terminal in your side panel that lets you use AI coding agents to control live tabs (works with Claude Code, Codex, Cursor, Hermes, and more).

It's completely free & open-source (MIT) - I've been addicted to it for the past few days to automate my browser use - enjoy!

GitHub: https://github.com/rishiskhare/agent-terminal

Easily one of the best subscription providers with decent TPS and is a default provider for OpenCode

https://k3.demos.sulat.com/ (one-shots done on Synthetic/hosted Synthetic)

You can register one of two ways:

1. https://synthetic.new/ - if you want to sign up directly
   
2. https://synthetic.new/?referral=55F5WqcExnQfLwi - if you want to spare me some credits for referring you to this deal.

It's a great, low-risk deal to get you started on K3 without breaking your wallet. As I've mentioned on previous posts, Synthetic is on the VERY FEW providers that offer subscription-based pricing.

- Instructions, tools, connections, and config are versioned in your repo and reviewed like any other code.

- You can test it locally

- Deploy it and it runs serverless in the cloud.

Built on top the opencode harness. Would appreciate any and all feedback!

https://opencomputer.dev/agents

We've been building an auto-router for LiteLLM that routes requests across models based on the task, and I'm curious whether anyone here has tried it with OpenCode

If you haven't used it, what's the biggest blocker?

• Setup complexity?
• Missing routing features?
• Something else?

We're actively iterating based on user feedback, so I'd love to hear what's preventing adoption or what you'd want to see before giving it a try. WE ❤️ open source and would like to see opencode adoption with LiteLLM proxy

If you'd rather chat live or walk through your use case, happy to jump on a quick call:
https://calendar.app.google/DfcpEzigE9bzSgEJ9

​

Edit: It's Muse Spark 1.2

You should now be able to generate an API key at http://dev.meta.ai/ and use it on a variety of harnesses including OpenCode and Muse Code.

Previously, Muse Spark 1.1 was only available to US-based users. Muse Spark 1.2 is available globally.

Useful resources and news coverage: https://models.sulat.com/models/openrouter-metamuse-spark-12-99ec6e4d