Built from the ground-up for agents, Vessel Browser is an open source AI browser for Linux/Mac/Windows that provides a durable state, MCP control, and BYOK with full autonomous browsing. Use with Hermes Agent, OpenClaw, or connect to your favorite API provider.
# Add to your Claude Code skills
git clone https://github.com/unmodeled-tyler/vessel-browserGuides for using ai agents skills like vessel-browser.
vessel-browser is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by unmodeled-tyler. Built from the ground-up for agents, Vessel Browser is an open source AI browser for Linux/Mac/Windows that provides a durable state, MCP control, and BYOK with full autonomous browsing. Use with Hermes Agent, OpenClaw, or connect to your favorite API provider. It has 101 GitHub stars.
vessel-browser's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/unmodeled-tyler/vessel-browser" and add it to your Claude Code skills directory (see the Installation section above).
vessel-browser is primarily written in TypeScript. It is open-source under unmodeled-tyler on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh vessel-browser against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.

Open source chromium-based browser for persistent web agents. Linux is the most mature install target today, and macOS release packaging is available from source.
Vessel gives external agent harnesses a real browser with durable state, MCP control, and a human-visible supervisory UI. It is built for long-running workflows where the agent drives and the human audits, intervenes, and redirects when needed.
Vessel is in active development and currently makes no security assurances. Use and deploy it with care.
https://github.com/user-attachments/assets/0a72b48a-873a-4eb0-b8f2-23e34d8472c4
Want the full agent toolkit from day one? Start a 7-Day Free Trial of Vessel Premium — $5.99/mo.
Linux AppImage from GitHub Releases:
Vessel-<version>-x64.AppImagechmod +x Vessel-*.AppImage./Vessel-*.AppImageCtrl+,) and confirm the MCP endpoint shown therenpm install -g @quanta-intellect/vessel-browser
vessel-browser
Or run it directly without installing:
npx @quanta-intellect/vessel-browser
curl -fsSL https://raw.githubusercontent.com/unmodeled-tyler/vessel-browser/main/scripts/install.sh | bash
Vessel development uses Node.js 22. If you use fnm, run fnm use from the repo root to pick up .node-version.
fnm use
npm install
npm run dev
If you want extra local AI tracing in development, create an optional src/main/telemetry/trace-logger.local.cjs file. Vessel will load it only in local dev builds, and packaged production builds ignore it.
Most browser automation stacks are either headless, stateless, or designed around a human as the primary operator. Vessel is built around the opposite model: the browser is the agent's operating surface, and the human stays in the loop through a visible interface with clear supervisory controls.
Vessel is built for persistent web agents that need a real browser, durable state, and a human-visible interface. The agent is the primary operator. The human follows along in the live browser UI, audits what the agent is doing, and steers when needed.
Today, Vessel provides the browser shell, page visibility, and supervisory surfaces needed to support that model. The long-term goal is not "a browser with AI features," but a browser runtime for autonomous agents with a clear supervisory experience for humans.
Ctrl+L) — a secondary operator surface for harness-driven workflows and future runtime commandsCtrl+Shift+L) — live supervision across eight tabs: Supervisor, Bookmarks, Checkpoints, Chat, Skills, History, Changes, and ResearchF12) — inspect console output, network requests, and MCP/agent activity in a resizable panel at the bottom of the window; export logs by category and date range as JSONCtrl+N; print the active page with Ctrl+P or save it directly as PDF with Ctrl+Shift+Pundo_last_action toolintent (what the page is for), expectedContent (what to expect on the page), keyFields (important form fields), agentHints (arbitrary directives), and a stored pageSchema; humans can create and edit this metadata directly in the Bookmarks tab, and all fields are searchablepageType (article, product, form, search, checkout, login, dashboard), primaryEntity (structured fields for products and articles), formFields (with names, types, labels, selectors), and actionButtons (with inferred intents: submit, addToCart, login, etc.); schema is attached to every content extraction resultflow_start; progress is tracked step-by-step with flow_advance and visible in the sidebar throughout executionChanged badge in the address bar when the title, headings, or main content differ on a later visit; expand it to see a compact summary of what changed since the last snapshot