---
title: "How to run Muse Code on a remote machine with a web UI"
url: https://helicon.sh/guides/remote-daemon-setup
description: "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."
updated: 2026-09-19
site: Helicon
---

# Drive Muse Code on a remote machine

Run the Helicon daemon and the muse CLI on the machine that holds your code, then open the web build in a browser and point it at that daemon. You get the same sidebar, diffs, approvals and cost view as the desktop app, with the agent running next to the repository instead of on your laptop.

## When this is the right shape

- The repository is large and the machine that holds it is not your laptop.
- Builds and test suites want more CPU than a laptop has.
- Code must not leave a particular machine.
- You want long runs to continue while the laptop sleeps.

## What you need on the remote machine

- Node 22 or newer, because you are running the daemon from source rather than using the bundled runtime.
- The muse CLI, signed in with its own `muse login` on that machine.
- A way to reach it: your own tunnel, VPN or reverse proxy.

## Security posture

The daemon can start processes and edit files, because that is what a coding agent does. Treat it as you would any service with shell access: do not expose it to the open internet, put it behind a tunnel or a VPN, and keep the approval modes strict rather than turning on allow all.

> There is no hosted Helicon. Nothing about your code, prompts, threads or files passes through us.

## Set up Helicon against a remote daemon

1. **Install the muse CLI on the remote machine** Sign in there with its own login.
   ```sh
   muse login
   ```
2. **Run the daemon there** Node 22 or newer is required when running from source.
   ```sh
   npm install && npm run dev
   ```
3. **Reach it privately** Use your own tunnel, VPN or reverse proxy rather than exposing the port.
4. **Open the web UI** Point the browser build at the daemon and add the projects on that machine.

## Frequently asked questions

### Is there a hosted version?

No. The daemon is yours, on a machine you control.

### Does the web UI have fewer features?

No. It is the same React UI as the desktop app. The difference is which machine the daemon runs on.

### Can several people use one daemon?

Multi user deployment is out of scope today. Helicon targets an individual developer's own machines.

## Related

- [Remote daemon and web UI](https://helicon.sh/features/remote-daemon): The same Helicon UI ships as a web app pointed at a daemon on another machine, so a laptop can supervise Muse Code running on a workstation or a server.
- [Linux](https://helicon.sh/install/linux): An x86_64 AppImage that runs on most distributions and updates itself. Make it executable, run it, and point it at a muse CLI that is signed in.
- [Remote development](https://helicon.sh/use-cases/remote-development): Run the daemon and the muse CLI on the machine that holds the repository, then supervise from a browser on a laptop. Same UI, same sidebar, same approvals.

---

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