Skip to content

Features

Inline diffs in the thread

Helicon renders each edit as a diff inline in the thread, at the exact turn that produced it, instead of printing a patch into scrollback. A file viewer sits beside the conversation, so any path Muse Code mentions opens with syntax highlighting without leaving the app.

Last updated · Markdown version

Why inline matters

A patch printed into a terminal is correct and nearly unusable. Ten minutes later it is above the fold of a scroll buffer with no anchor to the sentence that caused it. Putting the diff where the edit happened means the reason and the result are one screen apart.

What you get

  • Added and removed lines coloured with the same tokens the rest of the app uses, in light and dark.
  • The file path, so you know what moved without guessing.
  • A viewer beside the thread that opens any path the agent mentions, with syntax highlighting.
  • Markdown preview and editing, plus image, video and PDF preview, for repositories that are not only source.

Reviewing a long run

For a thread that ran while you were away, scroll the conversation and the diffs are already in place. Nothing needs to be replayed, because the event log is the record and Helicon renders it directly.

Frequently asked questions

Can I edit files in Helicon?

Markdown can be previewed and edited in the viewer. For source code, Helicon is read oriented and expects you to keep your own editor.

Do diffs survive a resume?

Yes. They are part of the thread history, so reopening the session shows them exactly where they were.

Does it show shell commands too?

Yes. Tool calls and their output are rendered in the thread alongside the diffs.

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.