OpenCode Browse
- ID
- 47399
- Status
- summarized
- Published
- 17 Nov 2026, 5:20 AM
- Fetched
- 17 Nov 2026, 11:40 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://opencode.ai/product/browse
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 17 Nov 2026, 11:41 PM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
OpenCode (from Anomaly) launched Browse, an MCP server plus Chromium extension that lets coding agents drive your real browser — your tabs, logins and extensions — rather than a fresh headless session. Agent tabs open in background collapsed groups, and control hands back to you for login, 2FA or payment, resuming when you click Continue. It works with any MCP client (OpenCode, Claude Code, Cursor, Codex, Zed), supports Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera and Chromium, and installs via curl, pwsh, npm or bun; it also does screenshots, tab recordings and network capture, with an allowed-sites list to pin an agent to named domains. The HN thread drew 311 points and 195 comments.
Why it matters
The concrete shift is that agent automation no longer needs stored credentials or scripted logins — the agent inherits every session you're already signed into. That flips the risk model: instead of scoping a headless browser to one origin, you must configure the allowed-sites list per task and route 2FA and payment steps through the handoff, because the agent's blast radius is now your authenticated web identity, not a sandbox. If you already run Claude Code, Cursor or Codex, this is installable today without switching clients.
Discussion angle
Cookie inheritance vs. sandboxing: ask the room whether they'd let an agent share their live browser profile at all, and if so, what the allowed-sites list and handoff rules should look like before it touches anything with a saved card or an admin session.