Skip to content

Use cases

Muse Code for macOS power users

If you run Muse Code across several repositories on a Mac, the constraint is not the agent, it is keeping track of it. Helicon gives every thread a home: projects grouped by directory, sessions with full history and resume, inline diffs, an approval queue and cost at API rates, in a universal DMG.

Last updated · Markdown version

The pattern this fixes

Four terminal tabs, three of them idle, one waiting on an approval you have not noticed, and no way to reopen the thread from Tuesday that had the reasoning you now need. That is the normal state of running an agent seriously, and it is an interface problem rather than a model problem.

What changes

  • Threads are listed under their project and resume with full history.
  • Blocked threads are marked, so the approval queue is visible at a glance.
  • Diffs are inline, at the turn that produced them.
  • The usage page shows what each thread would have cost at published rates.
  • The command palette reaches any project or session without the mouse.

Practical notes

  • One universal DMG covers Apple Silicon and Intel.
  • First launch needs right click then Open, because the builds are not Apple notarized yet.
  • The theme follows the system, in both light and dark.
  • Auto update keeps the app current.

Frequently asked questions

Is there an Apple Silicon build?

One universal DMG covers Apple Silicon and Intel.

Why the Gatekeeper warning?

The builds are updater signed but not Apple notarized yet. Right click and Open the first time.

Does it replace my editor?

No. It has a file viewer for reading what the agent touched. Writing code stays where you like it.

Same Muse Code. Same subscription. Better interface. 

Free and MIT licensed. Signed Windows installer, universal macOS DMG, and a web build against a daemon you run.