Windows (WSL2)
Fased on Windows is recommended via WSL2 (Ubuntu recommended). The CLI + Gateway run inside Linux, which keeps the runtime consistent and makes tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native Windows runtime support is not the public default yet because daemon/process management, shell assumptions, and path handling differ. WSL2 gives you the full Linux experience — one command to install:wsl --install.
Native Windows companion apps are planned.
Install (WSL2)
- Getting Started (use inside WSL)
- Install & updates
- Official WSL2 guide (Microsoft): https://learn.microsoft.com/windows/wsl/install
Gateway
Gateway service install (CLI)
Inside WSL2: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), expose it deliberately through Windows port forwarding. The WSL IP changes after restarts, so you may need to refresh the forwarding rule. Example (PowerShell as Administrator):- 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); usefased status --allto confirm. - Use
listenaddress=0.0.0.0only for intended LAN access;127.0.0.1keeps it local only. If the Gateway is reachable from other devices, require token/password auth. - 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):2) Enable systemd (required for gateway install)
In your WSL terminal:3) Install Fased (inside WSL)
Use the same repo-backed install flow you would use on Linux:./install.sh runs onboarding by default. Use ./install.sh --no-onboard only
when you want to install the CLI/runtime first and run
fased onboard --install-daemon later.
Full guide: Getting Started