@llyfn/claude-in-firefox
v0.4.0
Published
Drive Firefox from Claude Code and other MCP clients
Readme
Claude Code Bridge for Firefox
Let Claude Code drive your everyday Firefox: open tabs, click, type, read pages, fill forms, take screenshots, and read console and network logs.
It works in your real profile, with your logins. Read Safety before you use it on sites that matter.
Quick start
You need Firefox 140 or newer and Node 20 or newer, on macOS, Linux or Windows. On Linux, the Snap and Flatpak builds of Firefox are not supported. Zen works too; see Zen.
- Add-on. Install Claude Code Bridge for Firefox from addons.mozilla.org.
- Bridge. Run:
This registers the bridge with Firefox and adds anpx @llyfn/claude-in-firefox installfirefoxMCP server to Claude Code. Add--no-claudeto skip the Claude Code step. Run it from your home folder, not inside a project: npx puts that project'snode_modules/.binfirst on PATH, where a package could stand in fornode. - Use it. Start a new Claude Code session and ask it to use Firefox.
How it works
Claude Code ──▶ claude-firefox mcp ──socket or pipe──▶ native host ──native messaging──▶ add-on- Each Claude Code session gets its own Firefox window, opened behind yours. It can only touch tabs in that window, plus popups opened from them. Zen works differently; see Zen.
- The window title, and the tab group when tab groups are on, name the session, for example
Claude · d42a, and addworkingwhile Claude is acting orstoppedafter you press Stop. - A violet glow and a cursor show which tab Claude is working in.
- On Windows the two halves of the bridge talk over a named pipe. Before using the pipe, the MCP server checks that the process at the other end holds a key that only your user account can read.
Tools
| Tool | What it does |
|---|---|
| tabs_context, tabs_create, tabs_close | List, open and close the session's tabs |
| navigate | Load a URL, or go back or forward, waiting up to 15 s for the page to load |
| computer | Click, type, press keys, scroll, hover, drag, take screenshots, zoom, wait |
| read_page, find | Accessibility-tree outline with ref_N ids, and keyword search over it |
| form_input, file_upload | Set form fields by ref, and attach local files to file inputs |
| get_page_text | Readable text of the page's main content |
| read_console_messages, read_network_requests | Console output and HTTP requests since the page's origin loaded |
| resize_window | Resize the session window |
| browser_batch | Run several of these tools in one call |
Safety
- It acts as you. Claude uses your logged-in sessions. The add-on blocks no sites and asks no per-site permission; Claude Code's own permission settings are the only gate.
- Prompt injection is a real risk. A page can contain text written to steer Claude. Be careful on sensitive sites, especially if you run Claude Code without permission prompts.
- Stop button. Pages in a session window show a "Claude is using this window · Stop" bar. Stop blocks the session's browser calls until you press Resume and tells Claude to ask you how to continue. A call already running returns at once, though what it started in the page can still finish. Only a real click works; Claude's synthetic input can't press it.
- Some pages can't show the bar:
about:pages (including a new window's blank tab), other add-ons' pages, PDFs and restricted sites. On those, press Stop in another tab of the window, or interrupt Claude Code. - Closing the window doesn't stop Claude, and it clears a Stop: Claude can open a new window with
tabs_context.
- Some pages can't show the bar:
- Dialogs are answered automatically in session tabs, and Claude sees each answer:
alert()is dismissed,confirm()gets OK,prompt()gets its default text, and "Leave page?" prompts are skipped. While a session is stopped, dialogs appear normally. - What's redacted. Password, one-time-code and payment-card fields show as hidden in
read_pageandform_input. Nothing else is redacted: screenshots and console and network logs can show sensitive data. - Where data goes. What Claude reads from session tabs goes through the bridge to Claude Code, which sends it to Claude as part of your conversation. The add-on itself makes no network requests. It keeps the console and network logs of every tab in memory, but Claude can read them only from tabs in its window, including a tab you move into it.
- Domain guard. Input stops if the tab moves to another domain in the middle of an action.
- Firefox's own limits still apply. No add-on can touch
about:pages, other add-ons' pages, or the domains in theextensions.webextensions.restrictedDomainspref, such as addons.mozilla.org. To allow those domains, clear that pref and setprivacy.resistFingerprinting.block_mozAddonManagertotrueinabout:config. The installer never changes Firefox prefs.
Limitations
- Synthetic input. Firefox gives add-ons no OS-level input, so clicks and keys are simulated inside the page (
isTrusted: false). Because of that:- CSS
:hoverdoesn't apply. - Native
<select>menus and file pickers can't be used; useform_inputandfile_uploadinstead. - Clipboard paste doesn't work.
- Some pages ignore simulated events.
- CSS
- One Firefox profile at a time can run the add-on.
- Reload open tabs after you disable, reload or update the add-on. Otherwise console capture and dialog handling can break in tabs that were already open.
- Very early dialogs. A dialog raised by a page's first scripts can show normally and stall the call until it times out.
- Focus. Opening a session window brings Firefox to the front if another app is active.
- Windows is tested in CI with Firefox Developer Edition only.
Zen
Zen copies every tab into every window, so a session window would hold all of your tabs. In Zen, each session instead gets one tab in a "Claude · …" tab group at the end of your current window.
- Claude can only touch tabs in its group, plus popups opened from them. Tabs it opens from its pages join the group. A tab you drag into the group becomes Claude's.
- Claude works in the background and never switches your tab. Its pages run as background tabs, which some sites treat differently from the tab you're looking at.
- When the session ends, its tabs are ungrouped and stay open.
- Zen needs tab groups. If they are off,
tabs_contextsays so.
Update and uninstall
- Update: run
npx @llyfn/claude-in-firefox@latest install. Firefox updates the add-on from addons.mozilla.org on its own. - Uninstall: run
npx @llyfn/claude-in-firefox uninstall, then remove the add-on inabout:addons. This removes the Claude Code entry, the Firefox registration and the bridge's files.--no-claudekeeps the Claude Code entry.
With --no-claude, or when claude isn't on your PATH, the installer prints the claude mcp add command for you to run. If a firefox entry already exists, remove it first with claude mcp remove --scope user firefox.
Other MCP clients
The installer also prints a JSON block like this. Add it to your client's MCP configuration; for Claude Desktop, that is claude_desktop_config.json.
{ "mcpServers": { "firefox": { "command": "<path to node>", "args": ["<app directory>/node_modules/@llyfn/claude-in-firefox/host/src/cli.js", "mcp"] } } }Each client process is its own session, with its own window.
Troubleshooting
- "Firefox extension not connected". Check that Firefox is running, the add-on is installed, and you ran the install command. If you reinstalled after an uninstall, restart Firefox. Native host errors appear in the Browser Console (⌘⇧J on macOS, Ctrl+Shift+J elsewhere), prefixed
claude-firefox native host:. - On Windows, "could not prove that it holds the key in pipe-key". Restart Firefox: the bridge may still be running from before your last install. If that doesn't help, run the install command again, which recreates
pipe-nameandpipe-keyin the app directory if they are missing or damaged. If the error persists, another program may be using the bridge's pipe name. - It stopped working after a Node upgrade. The installer remembers the first
nodeon your PATH. Run the install command again. - "Cannot access this page". Firefox reserves that page for itself (see Safety).
- Clicks land in the wrong place. Take a new screenshot first. Coordinates always refer to the tab's latest screenshot.
The bridge lives in an app directory: ~/Library/Application Support/claude-in-firefox on macOS, ~/.local/share/claude-in-firefox on Linux, and %LOCALAPPDATA%\claude-in-firefox on Windows.
Development
Development needs Node 22.22 or newer.
npm install
npm test # unit tests
npm run lint # web-ext lint
npm run install-host -- --no-claude # install this clone like a release
npm run e2e # drive a real Firefox Developer Edition
npm run build # package the add-on into web-ext-artifacts/- e2e needs Firefox Developer Edition and a prior
npm run install-host -- --no-claude. On Linux, setFIREFOX_BINto its path. Don't run e2e while another Firefox has the add-on installed, because only one native host can run at a time. - Unsigned builds need Developer Edition or Nightly with
xpinstall.signatures.requiredset tofalse. Install the.zipfromweb-ext-artifacts/throughabout:addons→ gear menu → Install Add-on From File…. - After you change anything under
host/src, runnpm run install-hostagain. - Design notes are in
docs/superpowers/specs/.
.github/workflows/release.yml submits the add-on to addons.mozilla.org as a listed add-on, publishes @llyfn/claude-in-firefox to npm, and creates a GitHub release.
Every release also sends the listing in amo-metadata.json, so edit the listing there; changes made on addons.mozilla.org are overwritten. Screenshots and the icon are set in the Developer Hub.
One-time setup: store three secrets in the repository's release environment, for example with gh secret set NPM_TOKEN --env release:
AMO_JWT_ISSUERandAMO_JWT_SECRET, the API credentials from https://addons.mozilla.org/developers/addon/api/key/;NPM_TOKEN, an npm granular access token with read and write access to@llyfn/claude-in-firefoxand "Bypass two-factor authentication" ticked. Write tokens expire within 90 days, so check it before each release.
Only v* tags on main can use that environment, and each run waits for a maintainer's approval.
For each release:
- Bump
versionin bothextension/manifest.jsonandpackage.json. addons.mozilla.org won't sign a version twice. - Commit, then push a matching tag, for example
git tag v0.3.0 && git push origin v0.3.0. - Approve the run in the Actions tab. The workflow then checks that the versions match the tag, runs the tests and lint, checks the npm token, submits the add-on, publishes to npm with provenance, and creates the release.
The npm package is live as soon as the run ends, but a new add-on version, and on the first release the listing page itself, reaches users only after Mozilla reviews it. Firefox then updates the add-on on its own, while the bridge changes only when users run the installer again. So each add-on version has to work with older bridges, and each bridge with the add-on version before it.
