Show HN: Vessel Browser – An open-source browser built for AI agents, not humans
I've used agents extensively in my workflows for the better part of the last year - the biggest pain point was always the browser. Every tool out there assumes a human operator with automation bolted on. I wanted to flip that - make the agent the primary driver and give the human a supervisory role.
Enter: Vessel Browser - an Electron-based browser with 40+ MCP-native tools, persistent sessions that survive restarts, semantic page context (agents get structured meaning, not raw HTML), and a supervisor sidepanel where you can watch and control exactly what the agent is doing.
It works as an MCP server with any compatible harness, or use the built-in assistant with integrated chat and BYOK to 8+ providers including custom OAI compatible endpoints.
Install with: npm i @quanta-intellect/vessel-browser
Curious about the MCP tool schema design: with 40+ tools, are you using a flat tool registry or do you have any grouping/namespacing? I've run into issues where agents get confused when they have too many tools with similar-sounding names and start hallucinating tool calls that don't exist.
The way that I manage that in Vessel is contextual surfacing. This way, the model doesn't necessarily have 40+ tools to choose from at any given time, but rather is focused toward a subset of tools that are applicable given the current page context.
Speed and efficiency are my number 1 priority with this browser so this framework may change/shift as time goes on, but this is an approach that I'm particularly interested in exploring.
I've been packaging reusable MCP tool schema definitions (the JSON spec layer, not implementations) as a way to give agents a consistent vocabulary across different harnesses. The hallucination problem you're solving at the surfacing layer is related but distinct from the schema consistency problem — both matter for reliable tool use in production.
Your schema work sounds pretty interesting - any links? I'd be curious to check it out!
One thing I've been thinking about is whether we even need a separate browser process. On macOS, Safari's AppleScript bridge lets you run JS in any tab without launching anything new. Your existing browser with all its sessions is already there.
The trade-off is obvious though: a purpose-built browser like Vessel can add agent-specific features (structured DOM output, action recording) that you'd never get from a general-purpose browser's scripting API.
How are you handling authenticated sessions? That's been the biggest pain point I've seen with headless/separate browser approaches — users have to re-login or copy cookies.