Vessel is an open-source browser runtime built for persistent autonomous web agents. The AI operates. You supervise.
$ npm i @quanta-intellect/vessel-browser
One prompt. Five books added to cart on Powell’s. The agent navigates, browses, selects, and completes the entire workflow autonomously while you watch.
Traditional browsers assume a human at the helm. Vessel inverts that model — the agent is the primary operator, and every surface is designed for programmatic control with human oversight.
Not a human browser with agent bolted on. Every interaction surface — tools, state, context — is built for autonomous operation.
Core ArchitectureFull Model Context Protocol integration with 40+ tools. Navigate, interact, extract, and manage state through structured protocol calls.
ProtocolNamed sessions preserve cookies, localStorage, and browsing state. Checkpoints capture snapshots for recovery after restarts.
State ManagementSupervisor sidebar shows exactly what the agent is doing. Live approval controls, pause/resume, and configurable approval policies.
OversightStructured content extraction with visibility info, disabled state, current values, and select options. Not just DOM — meaning.
IntelligenceBuilt-in developer tools with console, network, and MCP activity logs. Command bar for harness-driven workflows. Reader mode for clean extraction.
Developer ExperienceVessel sits between your agent harness and the web, providing structured control with human oversight at every step.
Run Vessel as an MCP server through your agent harness, or use the built-in chat assistant with your own API keys. Eight providers supported out of the box — plus any OpenAI-compatible endpoint.
External agent harness controls the browser via Model Context Protocol
Built-in sidebar assistant reads the page, uses browser tools, multi-turn history
Inspired by the McDonald brothers' kitchen that made average workers extraordinary — Vessel encodes web browsing workflow so agents don't have to think about which tool to use.
On a login form, the agent only sees login-relevant tools
Elements annotated with workflow context and step progress
Workflow state maintained across page navigations
Login, search, checkout — common patterns as single actions
Tools revealed by layer — core, navigation, intelligence, diagnostic
Three ways to install. Pick whichever fits your workflow.
npm update -g to stay current.