Not that agreement proves anything but I am glad to know I was not the only one. Him, Boris, Theo (t3.gg or something) -- I look at their archetype and wonder if that is what you need for success and if indeed that is what you need, then perhaps I do not want success at all.
Highly recommend "The Nerd Reich" [0].
what would success bring you?
if what you want is success at all costs however, this is where you have to start
You have people who have high visibility on social media without playing games or constantly exaggerating their accomplishments or work.
But you're right that people who do play these games and adopt your so called archetype end up with this much visibility.
I think the reality is as simple as grandiose claims or presentation or just being clickbait personified works to gain an audience. It's also why these people have a bigger ratio of fans to people who can't stand them.
The much rarer people who reach a large audience while remaining genuine tend to be much more universally liked. The ratio is better for sure at least.
> doesn't mean you aren't the Chief executive. Thr not a ceo thing is kind of a twitter meme
Jay V (@jayair) seems to be explicitly publicly listed as the CEO. Is that enough to make someone else who says they aren’t the CEO, not the CEO? Or what would realistically convince you that Jay is the CEO?
Yes. I was shocked to suddenly discover everything was "auto permit all"
Then i discovered that all my pinned sessions were lost
Then you read on X that they vibing some sort of UI library or whatever the flavour of the week is
It a shame because they getting nice deals on tokens. You can churn billions of tokens per month
Just grow up already...
I mainly read Hacker News. So not surprised I've missed it.
But, I'm curious because I love to study good marketing.
These are gone, not because the generic "enshittification", but because with the new-wave of software, there is no need to "model user behavior" or guide "user metal model" any more: user tells exactly what software they want, based on what their mental model is. There is no need for such craftsman software any more.
Every single one I looked into looks like low quality vibecoded typescript.
> If you want to wrap it in a jsonrpc api for mcp, this is like 4 hrs or a work for an llm, point them at a pkg thats uses CDP like go-rod.
As someone who has vibe-coded my own such wrapper, I think that here is a lot of value in having a common interface for an agent to interact with CDP beyond just slinging together ad-hoc scripts until something works. CDP exposes a lot of features, but exposing them to an agent in a sane, consistent way takes a good bit of work.
> If you want to wrap it in a jsonrpc api for mcp, this is like 4 hrs or a work for an llm, point them at a pkg thats uses CDP like go-rod.
As someone who has vibe-coded my own such wrapper, I think that there is a lot of value in having a common interface for an agent to interact with CDP beyond just slinging together ad-hoc scripts until something works. CDP exposes a lot of features, but exposing them to an agent in a sane, consistent way takes a good bit of work.
It's also taken me a good bit longer than 4 hours by now. The features really add up over time.
Granted, Ive neen building browser automation tools on top of cdp for many years now.
SST was a tool ahead of its time when it launched (I used it). It’s on version 3 and is now open source and community maintained. I’ve found it useful.
The OpenCode agent is very cool and they even host some of their own models via a subscription. I found it useful too.
I haven’t used this new one yet.
Have you built anything useful, or are you just a critic?
Yes I put in 12 hrs a day, and usually running overnight as well in maybe half a dozen containers. I have billions of tokens going through Opencode a day as my main harness, for atleast a year.
I cannot accept their security model in V2 nor am I willing accept the nightmare and dangerous process of an upgrade. Where they basically tell the user, it ships with no permission model your plugins wont work, and we're making arbitrary changes all the time because we dont like how something is spelt/is plural that break your config. Typical vibe coded changes being made that come for no rhyme or reason but they push them and let the user deal with the headache. V2 is literaly slop because they got obsessed with full on vibe coding.
Instead of having a version bump to V2 that cared about backwards compatibility they said screw the user, we have llms now just tell it to upgrade your config and ask it to make no mistakes, we provided a skill, good luck (oh, and by the way we no longer ship an easy way to confine the agent into a directory, thats on you good luck.. Ask the llm who now has access to your entire computer, make no mistakes).
This wouldnt be that big of a deal if I didnt have half a dozen different sets of configs with granular permissions, each with their own plugins for different clients Im working for. Its probably a multi day task to upgrade for any power user which shouldn't be the case for any piece of software's version bump. If Im going to take the time to upgrade it would be to a different harness all together.
Oh and by the way, when you turn off acess to the internet to a container and use a local model, session titles suddenly stop working.. Turn it back on and they start working even with no Opencode acct authenticated, because they're summarizing your conversations without your consent to derive session titles.... So who knows what they're swallowing up of your data idk, I should put it behind an burp and see.
They have 2k issues on github but are shipping native UI frameworks nobody is going to use, for twitter likes.
They got a bunch of their users keys stolen and never took responsibility but rather blamed it on "distillers" instead of their own internal policies that lead to it. You can thank Dax for how every AI company scapegoats all their failures to distillers now whenever they fumble your credentials.
"If AI is so great at coding, and you're so good at using AI, why can't you make the changes you want in the v1 codebase gradually? Why can't you use AI to solve (not just mass close, actually FIX) the thousands of open issues you have on your GitHub?"
I think this is making me realize that I don't want to keep using OpenCode after using it as my daily driver for over a year (thousands of sessions).
And before anyone says "use Pi, it's great", I tried it and while it is fine, I think I fundamentally don't want to use a node-based tool ever again. Don't know why, they just always feel "slick" in all the least useful, most flashy ways. Anyone have any recommendations for the "sublime text 3"/nvim of stable and reliable harnesses?
I really don't get it, since Pi has always been "vim of harness space" for me...
These are not (nostly) written in JS/TS, so I think these are not node based.
https://github.com/openai/codex
https://github.com/nousresearch/hermes-agent
https://github.com/charmbracelet/crush
https://github.com/aaif-goose/goose https://aaif.io/projects
https://github.com/Aider-AI/aider kinda the original one
As for how reliable these are, you'd have to try them and see for your own usage. I am sure there are more. Lighter ones, maybe less famous, but I have tried these and I am back to using Claude Code most of the time :D. Though I am trying to get familiar with Goose. However given a choice between OpenCode and others, I won't even bother with OpenCode – it's really that bad. Though I've their Go plan and that has been very userful for me (super vfm).
I also don't get the point of Pi. Pi either has to become Claude/Codex for most coding tasks and then what's the point it, otherwise a tiny harness (or script) replaces it, so I've also stopped using Pi.
Do you have an example of tiny harness?
I use Pi, without any plugins and it is enough for me, I don't need more. The only issue is that I don't like JS/TS (its place is in the web, not in terminal) and I would prefer something written in a compiled language (C or Rust preferably) or at least Java/Python.
Oh, and I would need integration with Github Copilot and Claude APIs (api pricing) so I could use what I get at work.
Comment below mentions hax, it looks promising.
[1]: https://maki.sh/
It runs on all 3 platforms on a machine of your choice, from your browser. It has a tiling window manager and it is a frontier coding harness. It is not written in node.
DreamCoder's built to be stable and run day in and day out. It's not perfect, because harnesses are exceptionally complex, but it works really well.
It is a _very_ different paradigm to what you have used in Pi/OpenCode TUI.
What exactly does that mean, these days? Which harnesses are not frontier, and what does it do much better (on the code generation front) than others?
That's not so easy to achieve as you might think. Like all good software you can get 80% of the way to something quite quickly; it's the remaining 20% that takes a long time.
As for code generation, I'm not sure what you mean precisely?
You can use any model you like with dreamcoder. The harness steers the models well, and they'll turn out the same quality code as the other frontier harnesses.
I use several: Qwen 3.8 27B for local, which is a cracked little model; a Codex sub (Astra, Sol); and the free monthly credits I get with my claude sub for UI/visual stuff.
Browsers are everywhere, and you can point your phone at it. It also means the backend's a REST API, which has its own advantages.
This is from September 2025: https://github.com/anomalyco/opencode/issues/2632
Issue comment: "In my opinion very strange that Opencode allows any actions by default."
Comments from OpenCode devs:
"This was done very intentionally by the team they felt like this was a better UX and better default when they made the decision"
"most people initially think they want permissions and then actually prefer not having them so that's why our defaults work this way"
"I use it everyday in real projects at work, so do my coworkers, none of us use permissions"
ok, last i used it, which was within the last 12 months, it was v3. i was wrong.
> is not maintained
they're running off investor money (maybe profitable now, i don't know), do you expect them to spend their runway to maintain a project that clearly isn't going to work as a business model?
they spent years, day and night (i'm sure) working as hard as possible to build the SST tool, which by the way, could be used for free. (they even built seed.run - a way to deploy your SST projects)
how many years of their work are we entitled to? i am going to keep defending these guys against critics. it is so easy to be a critic and so hard to build something from nothing.
vulnerabilities in SST have been reported to them. in April they announced [0] their intent to maintain and support SST. take a look at the commit activity graph [1]. I'm not saying that they are beholden to provide support for years for free. I'm saying that they are currently paid to support SST and are not providing it, and that for those who aren't paying they owe an acknowledgement.
[0] https://x.com/vimtor/status/2039039247286501688 [1] https://github.com/anomalyco/sst/graphs/commit-activity
I'd go nuts if I had to use opencode at work; I use it for my you projects at home, it's okay for those. (Desktop, for both, I guess I should specify.)
Why are you doing oppo resesrch on me lol, I do not have any sort of product in the AI space lol.
I follow him on X, and I never got that impression. He has always come across as a skeptic IMO. Often wondering what others know that he doesn't due to practices that he hasn't found useful. I think yesterday he posted something suggesting that he doesn't follow usage patterns posted by others because the models have advanced to the point where any perceived improvements are by model rather than these patterns. I generally agree with this, and try not to get attached to any way of working with these things.
As for the usage of OpenCode, I have kept it to a minimum. V1 memory usage got a bit wild. Not sure if V2 has greatly improved. I have signed up for their Go plan a few times for times when I get tight on my other subs.
I wanted to use htmx in some project for fun. But Dax is really off putting .
It is outlined in "htmx lore" at https://htmx.org/essays/lore/#htmx-ceo
opencode team is great and dax doesn't even follow me
isn't that what this is?
>If you want to wrap it in a jsonrpc api for mcp, this is like 4 hrs or a work for an llm
isn't vibecoding a throwaway integration like this what you're criticizing opencode for here? why would i waste my tokens on that when opencode will give it to me already built?
Please elaborate. What is the problem if I only use OpenCode v2 (without extensions like Browse).
I think you're looking at it wrong. I run opencode itself inside bwrap (atop other layers) so anything it runs it's already sandboxed.
So I figured it’d make sense to lock down code execution within each Location (the internal name for worktree-like things) and rely on the permission system to ask me when the LLM wants to do stuff outside the Location through other channels than the shell tool.
Locking down the shell tool correctly only took a moment, but I really wasn’t prepared for the whack-a-mole exercise of stamping out all the other ways an LLM can execute arbitrary code without confirmation through other opencode features. And I don’t trust the next update not to introduce new ones.
Is that about agent permissions/access? I actually prefer the approach where they ship an unlocked product and it’s on you to decide how to configure and deploy it. Claude Code and Codex ship complex, but partial sandboxes that could surprise a lot of users in what they allow.
The agent is the drunk version of you. You may not be there for the drive but you'll be there for the DUI.
Security should be enforced outside the harness with a sandbox.
You're just being stubborn, the best UX is through the harness. Most users dont even know how to configure a sandbox properly and dont even use one.
Ive known quite a few naive people that have gotten their home directories wiped and really gotten burned. Many users of these products dont even know how to use a terminal and these harness companies are marketing to the average joe.
This separation doesn't mean it must result in bad UX. It just needs somebody to make a nice UI/TUI to configure the sandbox and when running that it does its setup and open whatever command you want.
The problem with the harness doing sandboxing is that from my experience the simply break all the time leading to users ignoring properly configuring it and using abominations like codex' `Approve for me` where IT ASKS A SEPARATE AI and not the user.
Hundreds of thousands of people are using them naively, if they shipped with common sense strictish permissions instead of none at all, like what opencode opted to do it would be safer for everyone. Its much easier for a normal non programmer to configure a simple config file than it is for them to learn how to properly setup a container/vm, they will just not do the latter 9/10.
Honestly, a harness should always install heavily gaurded, remember when Grok code/build was instantly indexing your home directory and sending it back to HQ on the first request it made..
That being said I still believe this should be separated and composable at an application level and power users should be able to switch out the sandbox. This way you don't have to trust the harness since it doesn't know anything about the sandbox and can't modify it etc.
This is their problem. But running and screaming "ai deleted my database" is all on them, not on LLM.
I have even been running my IDE in server/client mode with the server inside the container too (because of malicious extensions).
I agree in principle, but in practice most sandboxing technology (like bwrap) is too static for this use case: You grant access once during startup and can't extend/revoke without a restart. That's inconvenient when you realize halfway through your session that you need additional permissions, and it's insufficient for permissions that are only briefly needed (for the duration of one tool call).
A harness that controls the sandbox (e.g. for each individual tool invocation) can manage this much more effectively.
Put your agent in a restricted but fixed environment, and let it do its task. Anything else is mostly theatre and token burn.
I find auto review mode mandatory and refuse to consider any harness that doesn’t support it.
Opencode doesn’t support it. And there are no good plugins to do it either, the most popular had only six stars last I checked.
https://embracethered.com/blog/posts/2026/breaking-claude-co...
Also the harness should definately just have a solid permission structure for the average user that 1000% is not using a sandbox, most people I know naively do not and think these things are perfectly safe.
I have my agent request permissions for things like a Cloudflare API key (or I guide it or just come up with the request myself). These go in a simple queue, with justifications.
I review them and then have another agent with far more permissions create the tokens, with expiry and so on, and then hand the API tokens back.
The original agent doesn’t even run as my main user; it sits on a computer in a restricted account (easy to do with either macOS or Linux, or even Windows these days).
It has taken some rather long prompts to get it to self-report on itself when it tries to workaround.
Getting an agent to talk firefox/chrome's debug websocket takes 15 minutes.
The thing that takes time is figuring out how you want to design/structure the input/output mechanism.
I will make it easy for you and wont ask for all 36. List at least 20 projects they have released in past 3 months
rune, browse, nightmail, opencode-console-cli, deadbolt, strobe, bank, grim, isocast, textjs, clip, bellhop, flicks, hokum, justice, phonecall, opencode-plugin-lane, blackout, jobmail, fiend, haunt
15 have had substantive commits in the last 30 days.
The 3 months before that, there were 8 repos created and out of those, 3 have had substantive commits in the last 30 days.
I had to scrape the bottom of the barrel and some are internal, but they are certainly more prolific than you'd expect (Nothing against Anomaly, I just follow them on twitter and see anouncements for new stuff regularly enough to think that it was possible)
A jsonRPC wrapper isnt exactly the critical part here. Also not advocating for that, just use cdp lol. There are also well maintained wrappers of cdp that existed long before Ai/AnomalSlop that are maintained by incredible devs, like the one I mentioned go-rod maintained by yasmood.. Whos actually an expert on browsers/cdp unlike anaomoly who has zero background on it. .
Adding a jsonRPC wrapper to existing and maintained solutions for tool annotations isnt exactly that big of a deal... And you can then choose your security model rather than allow dax to choose for you, who doesnt give a fk about security.
I have a wrapper script to fire up opencode which enforces this config:
"default_model": $model,
"small_model": $model,
"telemetry": "disabled",
"updates": {
"disable": true,
"notify": false,
"auto": false
},
"permission": {
"*": "ask",
"websearch": "deny",
"webfetch": "deny",
"external_directory": "ask",
"bash": "ask",
"edit": "ask"
},
"web_search": false
.. and I have to regularly audit to ensure its up to date ..What are some specific examples of this?
In particular it's absolutely imperative that credentials of any kind should never enter the sandbox and never be accessible by the agent. If they are, consider the credentials compromised
I find it contradictory that you criticize OpenCode's projects as vibe coded while advocating for using LLM to vibe code the MCP connection.
Is the issue that their vibe coded projects are not as good as my vibe coded project?
Their CEO spends all day on twitter talking about how much better he is than everyone. And how nobody can use agents like he can. Its quite obnoxious
Also just use CDP, way too many browser solutions for agents when chrome ships with the ability to crontrol the browser at a low level.
If you want to wrap it in a jsonrpc api for mcp, this is like 4 hrs or a work for an llm, point them at a pkg thats uses CDP like go-rod.