---
title: "Fix: macOS blocks Helicon on first launch"
url: https://helicon.sh/guides/macos-first-launch
description: "The macOS builds are updater signed but not Apple notarized yet, so Gatekeeper warns once. Right click the app and choose Open, and later launches are normal."
updated: 2026-09-19
site: Helicon
---

# Opening Helicon the first time on macOS

The macOS DMG is updater signed but not Apple notarized yet, so Gatekeeper warns on first launch. Right click the app in Applications and choose Open, then confirm in the dialog. macOS remembers the decision and every later launch is normal. Notarization is a known gap, not a policy.

## What the warning means

Gatekeeper distinguishes between signed and notarized. The Helicon DMG is signed for the updater but has not gone through Apple notarization, so macOS shows the unverified developer dialog the first time. It is not a statement about the binary being unsafe, and the source for it is public.

## The fix

1. Open Applications in Finder.
2. Right click Helicon and choose Open.
3. Confirm in the dialog that appears.
4. Launch normally from then on.

> If you prefer to verify first, the repository is public and the releases are built from it.

## Open Helicon for the first time on macOS

1. **Open Applications** Find Helicon in Finder.
2. **Right click and choose Open** This is the path Gatekeeper accepts for an unnotarized app.
3. **Confirm** The dialog now has an Open button.
4. **Launch normally** macOS remembers, so later launches do not warn.

## Frequently asked questions

### Will the builds be notarized?

Notarization is a known gap rather than a decision. Until then the right click and Open path works.

### Is the app signed at all?

Yes, it is updater signed, which is what makes auto update work. Apple notarization is the separate step.

### Does this affect auto update?

No. Updates arrive through the app's own updater.

## Related

- [macOS](https://helicon.sh/install/macos): One universal DMG for Apple Silicon and Intel, with auto update. Install the muse CLI, sign in, drag Helicon to Applications, and open it the first time with right click.
- [macOS power users](https://helicon.sh/use-cases/macos-power-users): Several repositories, several threads, and a history that outlives the terminal. A universal DMG, a session sidebar, inline diffs and a cost view.
- [Muse Code on Windows without WSL](https://helicon.sh/guides/muse-code-windows-without-wsl): Muse Code runs natively on Windows. Here is how to check which route you are on, run it with Windows paths and PowerShell, and keep WSL2 as a fallback.
- [Resume a session](https://helicon.sh/guides/resume-a-muse-session): Find and reopen any past Muse Code thread, including ones started in the terminal TUI, with its full history, diffs and approval record intact.
- [Remote daemon](https://helicon.sh/guides/remote-daemon-setup): Put the Helicon daemon and the muse CLI on the machine that holds your code, then open the same UI in a browser from anywhere you trust the network.
- [See what a thread cost](https://helicon.sh/guides/see-muse-code-cost): Open the usage page to see what every thread would have cost at published per token rates, by day, by model and by thread, plus your plan meter.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt