Use cases
Muse Code for Windows developers
Windows has historically been the worst platform for terminal coding agents: WSL2 plumbing, mixed path formats and binaries you build yourself. Helicon ships a Windows installer with auto update, runs Muse Code natively with PowerShell for shell commands, and falls back to Muse Code inside WSL2 with two way path translation.
Last updated · Markdown version
What normally goes wrong
- The agent reports /home/you/project and nothing on the Windows side can open it.
- Half your tooling is in the distribution and half is on the host.
- Updating means finding the release page again.
What Helicon does about each
| Problem | What the app does |
|---|---|
| Mixed paths | Translates both ways on the WSL2 route, uses Windows paths natively |
| Shell mismatch | PowerShell for shell commands on the native route |
| Manual updates | Auto update built into the app |
| Which route am I on | Detection prefers native and tells you what it chose |
A setup that works
- Install Muse Code natively on Windows if you can. PowerShell should answer
muse --version. - Run
muse loginin that shell. Helicon stores no credentials. - Install Helicon with the installer. It is not code-signed yet, so click More info, then Run anyway if SmartScreen warns.
- Add the Windows paths you actually work in.
- Keep WSL2 only if your project or toolchain genuinely lives there.
Frequently asked questions
Do I need WSL2?
No. Muse Code runs natively on Windows and Helicon drives it directly. WSL2 remains supported for setups that need it.
Is the installer signed?
Not code signed yet, so SmartScreen may show 'Windows protected your PC': click More info, then Run anyway. Auto update is built in, and updates are signature checked by the app.
Does it work on Windows on ARM?
The published installer is x64. ARM users can run from source with Node 22 or newer.
Keep reading
- WindowsA Windows installer for a Muse Code desktop app, with auto update. Runs Muse Code natively on Windows, or inside WSL2 with path translation both ways.
- WSL2If your muse CLI lives in WSL2 Ubuntu, Helicon routes to it from the Windows desktop app and translates paths both ways, so the agent and the UI agree on where files are.
- Muse Code on Windows without WSLMuse Code runs natively on Windows. Here is how to check which route you are on, run it with Windows paths and PowerShell, and keep WSL2 as a fallback.
- macOS power usersSeveral repositories, several threads, and a history that outlives the terminal. A DMG for each Mac chip, a session sidebar, inline diffs and a cost view.
- Running agents in parallelIsolated worktrees, one sidebar, and clear marks for which thread is running, finished, or blocked on you. Plus the cost of all that parallelism, per thread.
- Remote developmentRun the daemon and the muse CLI on the machine that holds the repository, then supervise from a browser on a laptop. Same UI, same sidebar, same approvals.
Same Muse Code. Same subscription. Better interface.
Free and MIT licensed. Windows installer, Apple Silicon, Intel and universal macOS DMGs, and a web build against a daemon you run.