Skip to content
Download
v0.23.1Read the release notes

A desktop app for Meta's coding agent, Muse Code.

Every session, diff and approval in one window, on the Muse Code plan you already pay for.

Free and open source. Native on Windows (no WSL), macOS and Linux, plus VS Code.

Read Alexandr Wang’s post on X
Alexandr Wang@alexandr_wang · Chief AI Officer, Meta

harjot here built a pretty sick unofficial muse code app for windows!

7:50 PM · Sep 17, 2026 · 37.7K Views

422332448
Read Cosmo Du’s post on X
Cosmo Du@Answeror · Muse Code, Meta

really impressive desktop app by @harjjotsinghh built on github.com/meta-models/mu…

11:02 AM · Sep 17, 2026 · 3,086 Views

53335
Read Michael Douglas’s post on X
Michael Douglas@mjdouglas · Muse Code, Meta

Super impressive community-made desktop app for Muse Code. Well done, Harjot!

7:12 AM · Sep 17, 2026 · 2,435 Views

2201

0:00 / 0:00

MIT licensedFree, no paid tier
No second billRuns on your Muse Code plan
Your own loginCredentials stay in muse
Local stateSQLite on your machine

Tested with Muse Code 1.4.14 on Windows, macOS and Linux, 29 October 2026. Every build's changes are in the release notes.

Replay of a real run, sped up

Watch Muse Code fix a real bug

I recorded these runs on a public sample repo. Pick a task, step through each tool call, approve the edit and watch the diff land. Nothing runs on your machine.

Pick a taskRecorded run

Pick a task above. Each one replays a real Muse Code run inside the Helicon window, one step at a time.

Everything a session needs, in one window

Projects, threads, diffs, approvals and cost live side by side, so you stop hunting through terminal tabs.

Inline diffs

Every edit lands in the thread as a diff, right where it happened. No scrollback digging.

How inline diffs work
src/daemon/host.ts+6-3Edited
@@ -10,11 +10,14 @@ openWorkspace

Approvals stay approvals

Every approval is surfaced the moment it arrives. None are batched or bypassed.

How approvals work

Muse Code wants to run a shell command

Nothing runs until you decide.

$ npm test -- routes/projects

Try it: this card works.

Cost, in the open

What each thread would cost at API rates, so you see what your plan is doing.

How the cost view works

Cost at API rates, 30 days

$5.29

$5.51 saved by cache

muse-spark-1.3
$4.55
muse-spark-1.3 contributor
$0.74

Sample figures

Keyboard first

Command palette, slash commands and a model picker. Reach any thread by keyboard.

How the command palette works
Search threads, projects and actions⌘K
  • New thread⌘⇧O
  • Toggle sidebar⌘B
  • Refresh threads from Muse Code
  • Use light theme
/plan/review/compact!git status

Press ⌘K inside any live demo to open it.

One UI, two shells

The same React interface ships as a Tauri desktop app and as a web app pointed at a remote daemon.

How the remote daemon works

Same daemon, same threads, either way

Helicon
Desktop appTauri, with auto-update on Windows, macOS and Linux
your-server:4186
Web appAny browser, pointed at a remote daemon

Try the app right here

This is the real Helicon interface running on sample data in your browser. Pick a screen, then click around: open threads, approve a command, or send a message.

A thread waiting on your approval. Allow the test run and watch the turn finish, or send a message of your own.

ThreadLive demo

No terminal scraping

A local daemon spawns one muse serve host per workspace and speaks the Muse Code Session Protocol through Meta's official MIT @muse-code/sdk.

Auth is your own muse login. Helicon never stores credentials, and all state is local SQLite.

  • Auth from muse login
  • Local SQLite
  • Windows: native Muse Code, or WSL2 with path translation
  1. Helicon UITauri desktop app or web app
  2. Local daemonSQLite state, one host per workspace
  3. muse serveMuse Code Session Protocol via @muse-code/sdk
Events stream both ways, so approvals and diffs arrive as they happen.

Where Helicon fits

Helicon is one of several ways to run Muse Code. It is not the only GUI, and it is not official.

Runs on Windows

Helicon
Installer, native or WSL2
Editor extension
Via your editor's WSL setup
Switch harness
Varies

Billing

Helicon
Your Muse Code subscription
Editor extension
Your Muse Code subscription
Switch harness
Usually its own API billing

Lives where

Helicon
Standalone app or web
Editor extension
Inside the editor
Switch harness
Its own harness

Several repos at once

Helicon
Sidebar, grouped by directory
Editor extension
One window per project
Switch harness
Varies

Approvals

Helicon
Surfaced, never bypassed
Editor extension
Editor-dependent
Switch harness
Harness-dependent

Install in a few minutes

Pick your platform. You need the muse CLI signed in first; Helicon uses that login.

Windows

Installer with auto-update. Muse Code runs natively on Windows; WSL2 still works, with path translation both ways.

  1. Install Muse Code for Windows in PowerShell.

    irm https://dev.meta.ai/install.ps1 | iex

  2. Sign in once.

    muse login

  3. Run Helicon_0.23.1_x64-setup.exe from the latest release.

The installer is not code signed yet, so SmartScreen may warn: click More info, then Run anyway. Already running Muse inside WSL2? Helicon uses that when native Muse is not installed. Set HELICON_MUSE_RUNTIME=wsl to keep WSL when both are.

Download for Windows

Before you install

Billing, credentials, Windows, and whether any of this is official. Straight answers.

Ask on GitHub

Comparing options? Every Muse Code GUI, compared.

No. Helicon is an unofficial community project, MIT licensed. It is not made, sponsored or endorsed by Meta. It is a client for the Muse Code CLI, and has nothing to do with the Muse assistant app for Mac. "Muse" and "Muse Code" are trademarks of Meta, used here only to say what Helicon works with.

No. Helicon uses your existing Muse Code subscription through the muse CLI. There is no second bill.

With the muse CLI, from your own muse login. Helicon never stores or handles them.

Yes. Sessions started in the terminal TUI show up in the sidebar with full history, and you can resume them.

The macOS builds are not Apple-notarized yet. On macOS 15 or later, open Helicon once, click Done, then go to System Settings > Privacy & Security and click Open Anyway. On macOS 14 or earlier, right-click the app and choose Open. Or run xattr -dr com.apple.quarantine /Applications/Helicon.app in Terminal.

Yes. The same UI ships as a web app that can point at a daemon running elsewhere.

Muse Code runs natively on Windows now, and Helicon runs it directly: your own Windows paths, PowerShell for shell commands, no WSL. Muse Code inside WSL2 still works, and Helicon uses it when native Muse Code is not installed.

What each thread would have cost at Meta's published per-token rates. It is not a bill, just the meter reading, so you can see what your subscription did.

Yes. Command palette, slash commands, and a model and reasoning-effort picker cover everything, with full keyboard operation throughout.

Muse Code, the coding agent Helicon drives, needs a Meta credential: a browser sign-in or a Model API key. Billing is one of its 4 subscription plans, or pay per token with the API key. Helicon itself is free and adds no cost of its own.

Just the muse CLI, logged in with your own muse login. The desktop app ships its own Node.js. Running from source or hosting the web app needs Node 22+ yourself.

Only to check for updates. The desktop app asks helicon.sh whether a newer version exists, and that request tells us an install is alive: the platform, the version, and a weekly hash of the IP it came from. Nothing about your code, prompts, threads or files ever leaves your machine, and there is no account.

Yes. MIT licensed, no paid tier, source on GitHub. It uses your existing Muse Code subscription, so there is no second bill.

No. Helicon is a free, open-source desktop app for Meta's Muse Code coding agent. Helicon Focus is unrelated photo focus-stacking software from Helicon Soft.

Bring your threads out of the terminal.

Free, MIT licensed, and running on the Muse Code subscription you already have.

Download for WindowsView source100stars on GitHub