Features
Approvals you can actually see
Helicon surfaces every approval request Muse Code raises, as it arrives, and never batches or bypasses one. The three protocol modes, onRequest, promptUnmatched and denyUnmatched, are mapped one to one, so the app behaves exactly as the CLI would. Allow all exists but sits behind a deliberate opt in.
Last updated · Markdown version
Why this is a design decision, not a feature
An agent with shell and file system access is only as safe as the moment you get to say no. A wrapper that auto approves to keep a demo smooth has quietly removed that moment. Helicon treats the approval as the most important event in the protocol.
The three modes, unchanged
| Mode | What Muse Code does | What Helicon does |
|---|---|---|
| onRequest | Asks before the tool call runs | Shows the request and waits for you |
| promptUnmatched | Asks when the call is outside the allow list | Same, with the reason shown |
| denyUnmatched | Refuses anything outside the allow list | Shows the refusal in the thread |
In practice
- A waiting thread is marked in the sidebar so you can tell at a glance which one needs you.
- The request shows the command or edit, not a summary of it.
- Decisions stay in the thread history, so you can see later what was allowed.
- Allow all is a dangerous opt in, labelled as such, and off by default.
Frequently asked questions
Can Helicon approve things on my behalf?
Only if you turn on allow all, which is an explicit opt in presented as dangerous. By default every approval waits for you.
Do I lose approvals if I close the window?
No. The request belongs to the session, so reopening the thread shows it still waiting.
Does Helicon change what Muse Code considers safe?
No. The allow list and the modes are Muse Code's. Helicon renders them and sends your answer back.
Keep reading
- Background workSend a running tool call to the background, stop one, or stop them all. Cancel a workflow run, or skip and retry its agents, without abandoning the thread.
- Inline diffsEvery file the agent edits lands as a diff at the point in the conversation where it happened, with the touched file open in a viewer beside the thread.
- The muse terminalHow a Muse Code GUI differs from the muse CLI terminal interface: session history, inline diffs, approvals and cost, side by side with what the TUI already does well.
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.