Support

Clone the repository from GitHub, open Chrome and go to chrome://extensions, enable Developer Mode, click "Load unpacked" and select the FSB folder. The extension icon will appear in your toolbar.

We recommend xAI Grok 4.1 Fast for the best balance of speed and accuracy. It has a 2M token context window and costs $0.20/$0.50 per million tokens. For a free hosted option, try Gemini 2.0 Flash (experimental). For maximum quality, use Claude Opus 4.1 or Grok 4.1. If you want broad model access, use OpenRouter. If you want a privacy-friendly local setup with no API key, use LM Studio.

FSB itself is free. With hosted providers, you only pay for AI API usage. A typical automation task uses a few thousand tokens, costing fractions of a cent with budget models. Gemini 2.0 Flash is completely free (experimental). If you use LM Studio, there is no per-token API billing from FSB because requests stay on your local machine, though you still need the local hardware to run the model. The dashboard tracks hosted usage in real time.

FSB supports Chrome 88+ and all Chromium-based browsers including Microsoft Edge, Brave, Opera, and Vivaldi. Firefox support is planned for a future release.

Yes. API keys are encrypted using AES-GCM before being stored in Chrome's local storage. They are only decrypted in-memory when making API calls. Keys are never logged, exported, or transmitted to any server other than your chosen AI provider.

FSB has built-in stuck detection and recovery. If it detects it is repeating actions or not making progress, it will try alternative strategies. If all recovery attempts fail, it stops gracefully and reports what happened in the chat. You can always stop automation manually at any time.

FSB includes action validation and safety checks. It only performs actions on the current tab and only when explicitly instructed. All code is open source and auditable. That said, use caution with tasks involving sensitive accounts or financial transactions -- always review what FSB is doing.

Open an issue on the GitHub Issues page. Include the website URL, your task description, and any error messages from the FSB chat or browser console. Session logs from the Debug tab in Options can also help.

Sync (Beta) is the FSB extension tab that pairs the extension with the dashboard at full-selfbrowsing.com. Once paired, the dashboard shows live connection state, session counters, cost and token usage, and the active controlled tab. Background scheduling has been retired in v0.9.45rc1 -- use OpenClaw or Claude Routines for recurring autonomy, and FSB for precise browser execution.

MCP (Model Context Protocol) lets you control FSB from AI coding tools like Claude Code, Codex, Cursor, or OpenClaw. Install the fsb-mcp-server npm package, add it to your MCP client configuration, and you can automate browsers directly from your IDE. FSB exposes 50+ browser actions as MCP tools.

Connect FSB as an MCP server, then let the coding agent open the local app, click through real flows, observe DOM state, capture console or task errors, and report failures back into the coding session. This closes the manual loop between code generation, browser testing, logging, and fixing.

Yes. The Remote Dashboard at full-selfbrowsing.com lets you pair with your FSB extension via QR code, then send tasks, view a live DOM preview of the browser, and monitor current execution state from any device with a web browser.

FSB has a local memory system with three layers: semantic memory (site navigation patterns), episodic memory (past action sequences), and procedural memory (successful workflows). This data stays on your device and helps FSB navigate familiar sites faster and avoid repeating mistakes. Memory auto-consolidates after enough sessions.

Install the server with npm install -g fsb-mcp-server, then add it to your MCP client config (Claude Code, Codex, Cursor, Windsurf, etc.). In the FSB extension, open Options and enable the MCP bridge -- it will listen for connections on a local WebSocket. Once connected, your AI coding assistant can call any of FSB's browser tools directly from your editor.

FSB exposes two modes through MCP. Manual mode gives you 50+ granular tools -- navigate, click, type, scroll, read page content, take screenshots, fill spreadsheets, and more. Autopilot mode lets you describe a task in natural language and FSB's AI handles the step-by-step execution. This is especially useful when coding agents need to test an app in-browser and bring observations back to the editor.

The extension itself runs locally. If you use a hosted provider, AI-powered automation needs internet access to reach that provider's API. If you use LM Studio with its local server running and a model loaded, AI-powered automation can run locally on your machine. MCP manual tools (click, type, navigate) also work without external AI calls, and recorded workflow replays can run fully offline since they skip AI calls entirely.