FSB v0.9.95 Full Self Browsing
AI-powered browser automation through natural language. Tell it what to do, and watch it browse for you.
Pure structural intelligence. Zero vision. Zero guessing.
Benchmark · What's New · Quick Start · MCP Server · Architecture · Providers · Development
Benchmark
Average success rates on Online-Mind2Web, with FSB included.
| # | Agent | Average success rate |
|---|
| 01 | Hark | 97.7% |
| 02 | Navigator (n1.5) | 97.3% |
| 03 | ACT-2 | 92.7% |
| 04 | FSB | 92.3% |
| 05 | Navigator (n1-preview) | 78.7% |
| 06 | Google Computer Use | 69.0% |
| 07 | Operator | 61.3% |
| 08 | ACT-1 (Aug 2025) | 57.3% |
| 09 | Claude Computer Use | 56.3% |
| 10 | ACT-1 (Jul 2025) | 45.7% |
FSB: AI-reviewed result (277/300).
Overview
FSB (Full Self Browsing) is an open source Chrome extension for AI powered browser automation. Describe a task in plain English; FSB reads the live DOM, builds a plan, executes browser actions, verifies results, and reports progress through the popup, side panel, or MCP.
FSB v0.9.95 is functional and production ready for supervised automation. Browser automation can still behave unpredictably on complex or sensitive sites, so monitor actions and test on non critical pages first.
Why DOM First
Project Mariner, Claude Computer Use, and OpenAI Operator rely heavily on visual page understanding. FSB uses page structure directly.
| Metric | Vision based agents | FSB |
|---|
| Page understanding | Screenshots | DOM, selectors, ARIA, forms |
| Hidden elements | Often invisible | Available in structure |
| Typical per step latency | 1 to 3 seconds | 50 to 200 ms |
| Token/cost profile | Image heavy | Text/structure heavy |
Quick Start TL;DR
FSB shines when your AI client drives it directly. Install the MCP server for your client of choice — one command, no manual config edits, and no FSB API key needed (your MCP client's model handles the reasoning):
| Client | One-command install |
|---|
| Claude Code | npx -y fsb-mcp-server@latest install --claude-code |
| Claude Desktop | npx -y fsb-mcp-server@latest install --claude-desktop |
| Cursor | npx -y fsb-mcp-server@latest install --cursor |
| VS Code | npx -y fsb-mcp-server@latest install --vscode |
| Antigravity | npx -y fsb-mcp-server@latest install --antigravity |
| Codex | npx -y fsb-mcp-server@latest install --codex |
| Cline | npx -y fsb-mcp-server@latest install --cline |
| All at once | npx -y fsb-mcp-server@latest install --all |
Preview before writing: append --dry-run. Sanity check with npx -y fsb-mcp-server@latest doctor. Restart the client so the new MCP server appears.
Then install the browser side (the MCP bridge talks to the extension):
- Get FSB from the Chrome Web Store.
- From your MCP client, try:
Search for cats on Google or Read this page and summarize it.
Want to run FSB standalone from the extension popup/side panel? Open settings, paste an API key (xAI, Gemini, OpenAI, Anthropic, OpenRouter, LM Studio, or custom), and start there — no MCP needed.
On OpenClaw? Install FSB directly from ClawHub. That is the fastest onboarding route. If you need the manual fallback, the FSB skill in skills/fsb/ still prints the canonical OpenClaw stdio config block and runs the doctor flow. The bare --openclaw install flag stays manual because OpenClaw's MCP config schema is unstable across builds.
On Hermes? Use the same skill at skills/fsb/. Run node skills/fsb/scripts/print-hermes-yaml.mjs to print the canonical ~/.hermes/config.yaml mcp_servers.fsb block, or run node skills/fsb/scripts/install-host.mjs to detect a local Hermes config and gate the install on consent.
On Grok Bot? The marketplace wrapper lives in plugins/grok-bot/, with a pinned npm MCP server and one FSB skill. It uses Chrome on Bot's own computer; see its setup and privacy disclosures. Marketplace listing is pending publisher review.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
