Helicon vs a VS Code extension for Muse Code

At a glance

What each one is

Several community extensions bring the muse CLI into VS Code. They give you a chat panel inside the editor, which means the agent's output is a click away from the file tree you already have open, and applying an edit lands in the editor's own diff view. For a single repository and a single task that is hard to beat.

Helicon takes the other position. It is a standalone app whose primary object is the session, not the file. The sidebar lists every project on the machine, each with its threads, and the thing you resume is a conversation rather than a folder. That difference matters most when you are running work in four repos and want one place to see which ones are waiting on you.

Where they actually differ

One workspace versus every workspace

An editor extension is scoped to the window it lives in. Helicon indexes projects across your machine, including isolated git worktrees, and shows them in one sidebar with their sessions underneath.

The editor keeps working

Helicon does not care which editor you use. Neovim, Zed, JetBrains, Xcode or VS Code: the thread lives in its own window and the file viewer beside it opens whatever path the agent mentions.

Cost is surfaced

Helicon shows what threads would have cost at published API rates, by day, model and thread. This is a meter reading on your existing subscription, not a bill, and it is not something editor panels usually show.

Approvals are a queue, not a toast

Approval requests are listed and stay listed until you act. onRequest, promptUnmatched and denyUnmatched are mapped one to one and never bypassed.

Windows is a first class target

Helicon ships a signed Windows installer with auto update, runs Muse Code natively on Windows, and falls back to Muse Code inside WSL2 with path translation both ways when native is not installed.

Choose a VS Code Muse extension if

• Your work is one repo at a time and the file tree is the thing you care about.
• You want edits to land in the editor's own diff and staging flow.
• You already live in VS Code and do not want another window.

Choose Helicon if

• You want a session home that outlives any single editor window.
• You triage several threads across repos and worktrees.
• You want cost, approvals and full history in one surface.
• You are on Windows and want an installer, not setup.

Can you use both?

They compose cleanly. Keep the extension for inline work in the repo you are editing, and open Helicon when you want to see everything at once or resume something from last week. Both talk to the same muse CLI and the same subscription, so there is no second bill and no second login.