Skip to main content
FluffBuzz supports both native Windows and WSL2. WSL2 is the more stable path and recommended for the full experience — the CLI, Gateway, and tooling run inside Linux with full compatibility. Native Windows works for core CLI and Gateway use, with some caveats noted below. Native Windows companion apps are planned.

​
Native Windows status

Native Windows CLI flows are improving, but WSL2 is still the recommended path. What works well on native Windows today:
  • website installer via install.ps1
  • local CLI use such as fluffbuzz --version, fluffbuzz doctor, and fluffbuzz plugins list --json
  • embedded local-agent/provider smoke such as:
Current caveats:
  • fluffbuzz onboard --non-interactive still expects a reachable local gateway unless you pass --skip-health
  • fluffbuzz onboard --non-interactive --install-daemon and fluffbuzz gateway install try Windows Scheduled Tasks first
  • if Scheduled Task creation is denied, FluffBuzz falls back to a per-user Startup-folder login item and starts the gateway immediately
  • if schtasks itself wedges or stops responding, FluffBuzz now aborts that path quickly and falls back instead of hanging forever
  • Scheduled Tasks are still preferred when available because they provide better supervisor status
If you want the native CLI only, without gateway service install, use one of these:
If you do want managed startup on native Windows:
If Scheduled Task creation is blocked, the fallback service mode still auto-starts after login through the current user’s Startup folder.

​
Gateway

​
Gateway service install (CLI)

Inside WSL2:
Or:
Or:
Select Gateway service when prompted. Repair/migrate:

​
Gateway auto-start before Windows login

For headless setups, ensure the full boot chain runs even when no one logs into Windows.

​
1) Keep user services running without login

Inside WSL:

​
2) Install the FluffBuzz gateway user service

Inside WSL:

​
3) Start WSL automatically at Windows boot

In PowerShell as Administrator:
Replace Ubuntu with your distro name from:

​
Verify startup chain

After a reboot (before Windows sign-in), check from WSL:

​
Advanced: expose WSL services over LAN (portproxy)

WSL has its own virtual network. If another machine needs to reach a service running inside WSL (SSH, a local TTS server, or the Gateway), you must forward a Windows port to the current WSL IP. The WSL IP changes after restarts, so you may need to refresh the forwarding rule. Example (PowerShell as Administrator):
Allow the port through Windows Firewall (one-time):
Refresh the portproxy after WSL restarts:
Notes:
  • SSH from another machine targets the Windows host IP (example: ssh user@windows-host -p 2222).
  • Remote nodes must point at a reachable Gateway URL (not 127.0.0.1); use fluffbuzz status --all to confirm.
  • Use listenaddress=0.0.0.0 for LAN access; 127.0.0.1 keeps it local only.
  • If you want this automatic, register a Scheduled Task to run the refresh step at login.

​
Step-by-step WSL2 install

​
1) Install WSL2 + Ubuntu

Open PowerShell (Admin):
Reboot if Windows asks.

​
2) Enable systemd (required for gateway install)

In your WSL terminal:
Then from PowerShell:
Re-open Ubuntu, then verify:

​
3) Install FluffBuzz (inside WSL)

For a normal first-time setup inside WSL, follow the Linux Getting Started flow:
If you are developing from source instead of doing first-time onboarding, use the source dev loop from Setup:
Full guide: Getting Started

​
Windows companion app

We do not have a Windows companion app yet. Contributions are welcome if you want contributions to make it happen.