Guides

These are task guides for running Muse Code through a graphical client: Windows without WSL, resuming past sessions, remote daemon setup, parallel agents in git worktrees, reading what an agent changed, and the two failures people hit most, a missing muse CLI and the macOS first launch warning.

Last updated 29 October 2026

Each guide is one task, with the steps and the failure modes.

• 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.
• Resume a sessionFind and reopen any past Muse Code thread, including ones started in the terminal TUI, with its full history, diffs and approval record intact.
• Remote daemonPut the Helicon daemon and the muse CLI on the machine that holds your code, then open the same UI in a browser from anywhere you trust the network.
• Muse Code over SSHPoint Helicon at a folder on a remote machine and Muse Code runs there over ssh, while you keep threads, approvals and diffs in a desktop app on your laptop.
• Muse Code in VS CodeRun Muse Code in a VS Code side panel with Helicon: threads as tabs, approvals you can read, and the files each thread changed. Uses your own muse login.
• Muse Code in CursorCursor, Windsurf and Antigravity install Helicon from Open VSX: a Muse Code side panel with threads as tabs, readable approvals and the files each thread changed.
• See what a thread costOpen the usage page to see what every thread would have cost at published per token rates, by day, by model and by thread, plus your plan meter.
• Review what the agent didRead a finished Muse Code run: inline diffs where each edit landed, tool calls with output, the approval record, and touched files beside the thread.
• Parallel agents in worktreesUse isolated git worktrees so parallel agents never collide, then watch all of them from one sidebar that shows which threads are running and which are blocked.
• Keyboard controlThe command palette, slash commands in the composer, and the model and reasoning effort picker. Everything in Helicon is reachable without a mouse.
• Fix: muse CLI not foundHelicon needs a working, logged in muse CLI. Here is how to check which install it is looking at on Windows, macOS, Linux and WSL2, and how to fix each case.
• Muse Code loginSign in to the muse CLI once, confirm the login from Helicon, fix the common login failures, and see how Helicon uses that login.
• YOLO modeHelicon's YOLO switch runs muse --yolo: no approvals, no sandbox for new threads. Read the four approval modes and when YOLO fits.
• Fix: macOS first launchThe macOS builds are not notarized yet, so Gatekeeper blocks the first launch. On macOS 15+, click Open Anyway in System Settings > Privacy & Security.
• Move from the terminalYou do not have to choose. Sessions started in the terminal show up in Helicon, resume there, and the CLI keeps working exactly as before.
• Muse Code approval promptsHelicon marks Muse Code threads that wait on an approval and shows the real command before it runs. Here is why I built it that way.
• Attach screenshots to Muse CodePaste, drop or pick up to 10 files per Muse Code prompt in Helicon. Images go straight to the model; other files land in your project for the agent to read.
• Muse Code pricingMuse Code pricing as Meta lists it: four monthly plans from $5 to $200, per-token Model API rates and no free tier. Helicon, the desktop client, adds no cost.
• Muse Code reviewA plain Muse Code review covering plans and prices, usage limits, platforms, when the plain terminal wins, and what the Helicon desktop app adds on top.