Opencode vibe codes and releases like 3 projects a week at this points. Cool, just know its throwaway software to them. They seem really reckless when it comes to security. Opencode V2 basically threw security out the window. Theyve completely lost the plot as an org.
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 control 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.
show comments
jeremyjacob
The functionality seems to overlap with the Playwright MCP server [0]. I've been using this instead of the built in browsers in Claude Code and Codex since it lets you grant access to pages and sessions that are already open. Of course one should be weary of the lethal trifecta when using these tools and use separate profiles for them.
> Your real browser:
Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera and Chromium.
Firefox not?
show comments
skeledrew
I found agent browsing to be an issue when I started using them months ago. Built a Firefox extension back then that uses the browser instance that I use, the way I use it, so there's really no difference to a site.
_pdp_
Cool.. but I think it is just simply better to give your AI agents their own browsers for your own sanity.
At least they don't even pretend that it's sandboxed or approval gated.
To anyone trying this, good luck and keep a fire extinguisher handy.
vibebingo
Oh this is a problem? I just ask my agent to do stuff with a browser and it figures it out.
orsenthil
OpenCode comes with the cost too. The cost of the hosted version is on par with cloud hosted proprietary models. And we cannot simply run the LLMs on every laptop. Given this, how do we us the browse efficiently?
show comments
esafak
It's all right when it works, but it has a habit of disconnecting; you have to rerun 'browse pair'. This MCP should hopefully become unnecessary once OpenCode's integrated browser tool gains persistent sessions. https://github.com/anomalyco/opencode/pull/63002
latchkey
codex's extension connection will often randomly fail on me and i (and ai) can't figure out how to get it working again.
i've switched to using omp's extension and that seems to work better.
Opencode vibe codes and releases like 3 projects a week at this points. Cool, just know its throwaway software to them. They seem really reckless when it comes to security. Opencode V2 basically threw security out the window. Theyve completely lost the plot as an org.
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 control 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.
The functionality seems to overlap with the Playwright MCP server [0]. I've been using this instead of the built in browsers in Claude Code and Codex since it lets you grant access to pages and sessions that are already open. Of course one should be weary of the lethal trifecta when using these tools and use separate profiles for them.
[0] https://playwright.dev/docs/getting-started-mcp
> Your real browser: Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera and Chromium.
Firefox not?
I found agent browsing to be an issue when I started using them months ago. Built a Firefox extension back then that uses the browser instance that I use, the way I use it, so there's really no difference to a site.
Cool.. but I think it is just simply better to give your AI agents their own browsers for your own sanity.
why not https://github.com/ChromeDevTools/chrome-devtools-mcp
At least they don't even pretend that it's sandboxed or approval gated.
To anyone trying this, good luck and keep a fire extinguisher handy.
Oh this is a problem? I just ask my agent to do stuff with a browser and it figures it out.
OpenCode comes with the cost too. The cost of the hosted version is on par with cloud hosted proprietary models. And we cannot simply run the LLMs on every laptop. Given this, how do we us the browse efficiently?
It's all right when it works, but it has a habit of disconnecting; you have to rerun 'browse pair'. This MCP should hopefully become unnecessary once OpenCode's integrated browser tool gains persistent sessions. https://github.com/anomalyco/opencode/pull/63002
codex's extension connection will often randomly fail on me and i (and ai) can't figure out how to get it working again.
i've switched to using omp's extension and that seems to work better.
https://github.com/can1357/oh-my-pi/blob/main/packages/brows...