Windows (WSL)
While SlopCode can run directly on Windows, we recommend using Windows Subsystem for Linux (WSL) for the best experience. WSL provides a Linux environment that works seamlessly with SlopCode’s features.
Setup
-
Install WSL
If you haven’t already, install WSL using the official Microsoft guide.
-
Install SlopCode in WSL
Once WSL is set up, open your WSL terminal and install SlopCode using one of the installation methods.
Terminal window curl -fsSL https://slopcode.dev/install | bash -
Use SlopCode from WSL
Navigate to your project directory (access Windows files via
/mnt/c/,/mnt/d/, etc.) and run SlopCode.Terminal window cd /mnt/c/Users/YourName/projectslopcode
Desktop App + WSL Server
If you prefer using the SlopCode Desktop app but want to run the server in WSL:
-
Start the server in WSL with
--hostname 0.0.0.0to allow external connections:Terminal window slopcode serve --hostname 0.0.0.0 --port 4096 -
Connect the Desktop app to
http://localhost:4096
SLOPCODE_SERVER_PASSWORD=your-password slopcode serve --hostname 0.0.0.0Web Client + WSL
For the best web experience on Windows:
-
Run
slopcode webin the WSL terminal rather than PowerShell:Terminal window slopcode web --hostname 0.0.0.0 -
Access from your Windows browser at
http://localhost:<port>(SlopCode prints the URL)
Running slopcode web from WSL ensures proper file system access and terminal integration while still being accessible from your Windows browser.
Accessing Windows Files
WSL can access all your Windows files through the /mnt/ directory:
C:drive →/mnt/c/D:drive →/mnt/d/- And so on…
Example:
cd /mnt/c/Users/YourName/Documents/projectslopcodeTips
- Keep SlopCode running in WSL for projects stored on Windows drives - file access is seamless
- Use VS Code’s WSL extension alongside SlopCode for an integrated development workflow
- Your SlopCode config and sessions are stored within the WSL environment at
~/.local/share/slopcode/