Skip to content

Features

Subagents and workflow runs

Muse Code can fan work out to parallel subagents and run multi step workflows. In a terminal that is interleaved text. Helicon renders it as structure, so you can see which agents are running, cancel a workflow run, and skip or retry individual agents without restarting the thread.

Last updated · Markdown version

The terminal problem

Seven agents writing to one stream is not a log, it is noise. The information is all there and none of it is legible. A replayable event log deserves a renderer.

What Helicon does with it

  • Shows each subagent separately rather than interleaved.
  • Cancels a workflow run without killing the whole thread.
  • Skips an agent, or retries one that failed.
  • Sends a running tool call to the background, stops one, or stops them all.

Why it stays honest

Helicon renders the protocol events Muse Code emits. It does not summarise them into something tidier, because the point of watching an agent is seeing what it really did.

Frequently asked questions

Can I stop one subagent without stopping the thread?

Yes. Individual agents in a workflow run can be skipped or retried, and a workflow run can be cancelled on its own.

Do subagents cost extra?

They use your Muse Code subscription like any other turn. Helicon shows what the thread would have cost at published rates so the fan out is visible.

Can I start a workflow from Helicon?

Workflow support tracks what the protocol exposes. Where Muse Code surfaces a run, Helicon renders and controls 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.