Skip to content

Use cases

For people who do not want a GUI

The objection to a GUI over a CLI is that it will be slower and will take something away. Helicon is keyboard first with a command palette, requires no migration because it reads the same sessions the CLI writes, and adds only the things a terminal structurally cannot do: persistent history, cross project triage, and cost.

Last updated · Markdown version

What you are not giving up

  • The CLI keeps working, unchanged, alongside the app.
  • Sessions you start in the terminal appear in the app and resume there.
  • No configuration is migrated, rewritten or taken over.
  • Every action is reachable from the command palette without a mouse.

What a terminal structurally cannot do

CapabilityWhy the terminal cannot
Persistent session listScrollback is not an index
Cross project triageTabs do not know about each other
Approval queueA prompt only helps if you are looking at it
Cost per threadThe shell never sees the usage events
Structured subagent viewSeven writers, one stream

The honest recommendation

Keep the terminal for quick single repository work. Open the app when the number of threads exceeds what you can hold in your head, or when you need to find something from last week. If that never happens to you, you do not need this.

Frequently asked questions

Can I use it without a mouse?

Yes. The command palette reaches every project, session and action.

Will it change my CLI setup?

No. It drives your existing install with your own login and settings.

What if I try it and prefer the terminal?

Uninstall the app. Your sessions and configuration are untouched, because it only ever read them.

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.