Guides
Turn on YOLO mode (muse --yolo) in Helicon
YOLO mode is Helicon's switch for the muse --yolo posture. Nothing asks for approval in any thread, and new threads run without sandbox confinement. Turn it on in the Permissions menu or in Settings. Turning it off restores the approval modes you had before.
Last updated · Markdown version
What YOLO mode changes
YOLO mode sets the posture of muse --yolo. Nothing asks for approval in any thread. New threads run without sandbox confinement. Workspaces are trusted.
Approvals turn off for every open thread at once. The sandbox change applies to new threads only. Threads that are already open keep the sandbox posture they started with.
Flipping the switch restarts the running Muse hosts, which interrupts their turns.
Turn it on
- Open the Permissions menu in the composer and switch on YOLO mode. You can also open Settings, go to the YOLO mode section and flip its toggle.
- Read the dialog titled Turn on YOLO mode? and choose Turn on YOLO.
The four approval modes
When YOLO mode is off, the Permissions menu picks one of four approval modes. The table gives each menu label, its value name, and what it does.
| Menu label | Value name | What it does |
|---|---|---|
| Ask first | onRequest | Muse asks before anything that needs approval. |
| Ask for unlisted | promptUnmatched | Commands your rules allow just run; anything else asks. |
| Deny unlisted | denyUnmatched | Commands your rules allow just run; anything else is refused. |
| Full access | allowAll | Every tool runs without asking. Only for sandboxes. |
When YOLO fits
YOLO mode suits a disposable environment, such as a container or VM you can delete. The full access dialog gives the same advice: use it only in a disposable environment.
When it does not fit
- Your main checkout, or any folder with work you have not committed.
- A repo where you can push to a shared remote or deploy, since a bad command can run git push or a release script without asking.
- A machine that can reach production credentials, SSH keys or other secrets.
- Any thread you will not watch, since no approval prompt will stop a bad command.
Turn it off
Switch YOLO mode off in the Permissions menu or in Settings. Helicon restores the approval modes you had before.
Turn on YOLO mode in Helicon
Open the Permissions menu. In the composer, open the Permissions menu.
Confirm. Read the dialog titled Turn on YOLO mode? and choose Turn on YOLO.
Turn it off when done. Switch YOLO mode off to restore your previous approval modes.
Frequently asked questions
Is YOLO mode the same as muse --yolo?
It sets the same posture. The Settings text says it works like muse --yolo, and hosts start with --disable-sandbox and --trust-workspace.
Does YOLO mode turn itself off?
No. It stays on until you switch it off, and the confirmation says so.
Do open threads change right away?
Approvals turn off for every open thread at once. The sandbox change applies only to new threads.
Keep reading
- Review what the agent didRead a finished Muse Code run: inline diffs where each edit landed, tool calls with output, the approval record, and touched files beside the thread.
- Parallel agents in worktreesUse isolated git worktrees so parallel agents never collide, then watch all of them from one sidebar that shows which threads are running and which are blocked.
- Resume a sessionFind and reopen any past Muse Code thread, including ones started in the terminal TUI, with its full history, diffs and approval record intact.
Same Muse Code. Same subscription. Better interface.
Free and MIT licensed. Windows installer, universal macOS DMG, and a web build against a daemon you run.