Skip to content

Guides

Driving Helicon from the keyboard

Open the command palette to jump to any project, session or action. Slash commands work in the composer the way they do in the CLI, and the model and reasoning effort picker changes the next turn without restarting the thread. No part of Helicon requires a pointing device.

Last updated · Markdown version

The palette is the main road

If you know the name of a project or a session, the palette is faster than the sidebar. It also holds the actions, so new thread, stop, background, settings, theme and usage are all one search away.

In the composer

  • Slash commands, matching what the CLI accepts.
  • Goal controls, so you can set or change the standing objective without leaving the input.
  • The model and reasoning effort picker, applied to the next turn.

Why this exists

The reasonable objection to any GUI over a CLI is that it will be slower. It is only slower if it forces the mouse. Everything here was built so the keyboard path is the fast one.

Frequently asked questions

Can I remap shortcuts?

The palette covers every action by name, which is the intended fast path. Settings holds the app level preferences.

Do slash commands behave like the CLI?

The composer accepts them, and the goal controls also exist as panel buttons when you prefer clicking.

Can I switch model mid thread?

Yes, with the picker. It applies from the next turn.

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.