Firecrawl Without Docker and a Smarter VibeFuse Installer

VibeFuse 0.1.12 adds Firecrawl cloud API fallback without Docker and an installer that replaces stale builds instead of reporting already present.

Two friction points blocked real installs: Firecrawl assumed Docker, and the installer sometimes left people on stale builds. VibeFuse 0.1.12 fixes both.

Firecrawl cloud fallback

Not every Windows box runs Docker Desktop. Paste a Firecrawl API key (fc-…) in Settings → Tools and Connect switches the MCP plus built-in search/scrape/map tools to api.firecrawl.dev. Local Docker on port 3002 still wins when it is healthy. That dual path is what makes MCP tools demos honest on a fresh laptop.

Installer version check

The installer compares installed VibeFuse.exe against the latest release and re-downloads when stale — instead of reporting “already present.” Combined with the small installer size, that is the one-click trust loop: download, replace, launch the build you meant to test.

Download VibeFuse free or use Settings → About → Update when a newer build is available.

Product hub: AI desktop workspace · Related: /mcp-tools · Download VibeFuse free

Update FAQ

Do I need Docker for Firecrawl in VibeFuse?

No. Paste a Firecrawl API key (fc-…) in Settings → Tools to use api.firecrawl.dev. Local Docker on port 3002 still works when available.

What did the installer fix?

It compares the installed VibeFuse.exe version to the latest release and re-downloads when stale instead of saying the app is already present.

Which version introduced this?

VibeFuse 0.1.12.

Where do I download the installer?

From /downloads/VibeFuse/ — use VibeFuseInstaller.exe for the one-click path.