Skip to content

Guides

Review what the agent changed

Scroll the thread. Each edit is rendered as a diff at the turn that produced it, tool calls show the command and its output, and approvals show what you allowed and when. Click any path the agent mentions and it opens in the file viewer beside the conversation.

Last updated · Markdown version

A review is three questions

  1. What did it change? The inline diffs, in the order they happened.
  2. What did it run? The tool calls, with the command and the output, not a summary.
  3. What did I allow? The approval record, still in the thread.

Reading a long unattended run

Nothing needs replaying. The thread is the event log rendered, so a run that finished overnight reads exactly like one you watched. Start at the first approval, because that is usually where the run either went well or went sideways.

Cross checking against git

Helicon does not commit for you. The diffs in the thread are what the agent did, and your working tree is the ground truth. For parallel work, isolated git worktrees appear as their own projects, so one agent's changes never mix with another's.

Frequently asked questions

Does Helicon commit changes?

No. It shows what changed. Committing stays yours.

Can I see the exact command that ran?

Yes. Tool calls are rendered with the command and its output rather than a description.

Where do I see what I approved?

Approval decisions stay in the thread history at the point they were made.

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.