Moonfold. Download

DocsGet started

Running Moonfold in the background

On Linux and macOS, Moonfold can run as a service for your user so you do not need to keep a terminal open.

Manage the service

Install the moonfold CLI first (Install Moonfold), then run these commands on the machine that will host Moonfold:

Task Command
Install and start moonfold service install
Inspect status and log location moonfold service status
Move to a newer release moonfold update
Restart moonfold service restart
Stop and remove from startup moonfold service uninstall

Uninstalling the service leaves your projects, threads, and settings intact. Running moonfold service install again repairs a service that moonfold service status reports as broken.

moonfold update downloads the newest release on your channel and switches moonfold and the service to it. Restarting interrupts running agent turns, terminals, and remote clients, so it asks first; answer no and the service keeps running the old version until you run moonfold service restart. Pass --yes from a script. A server you started by hand is left running; stop and start it again to pick up the new version. Wait for any remote update already in progress before updating; to match a remote client's version, follow Updating Moonfold.

Pass an exact version (moonfold update 0.0.42) to pin one, --channel nightly to switch trains, or --allow-downgrade to move backwards. preview is a maintainers' test train: its builds can be broken and are never offered as updates, so the installer and moonfold update ask for confirmation before installing one.

moonfold uninstall removes the background service, the moonfold launcher, and the downloaded versions after showing you the list and asking once. Your projects, threads, and settings under ~/.moonfold/userdata are kept. Pass --yes from a script.

Platform support

Linux needs systemd user services. Setup enables lingering so Moonfold starts at boot and keeps running after logout. If this needs administrator permission, setup prints a recovery command before changing the service.

macOS starts the service when you log in and stops it when you log out. Keep the Mac logged in and awake for unattended remote access. Installing over SSH while nobody is logged in at the Mac's screen can fail at the final start step; the service is still installed and will start at the next login.

Windows background services are not supported.

Moonfold Connect can offer service installation during setup, but the two are managed separately. Signing out of Moonfold Connect does not stop or uninstall the service.

Troubleshooting

Start with moonfold service status on the host. It prints the log path and, on Linux, checks whether the installed service is running, enabled, and allowed to survive logout.

If it stops when your SSH session closes, check for linger-disabled. An administrator can enable lingering with:

sudo loginctl enable-linger "$(id -un)"

Over SSH, allow sudo to prompt:

ssh -t your-server 'sudo loginctl enable-linger "$(id -un)"'

Then retry service setup as your normal user. Run only the loginctl command with sudo; running Moonfold as root creates a separate installation and Connect identity. Without administrator access, run moonfold serve in a terminal and keep that session open.

Status problem Next step
linger-unavailable Run loginctl show-user "$(id -un)" --property=Linger and check that systemd-logind is available.
user-manager-unavailable Run systemctl --user status in a login session for the service user; check your distribution's systemd user-session support.
service-disabled or service-stopped Read the log and systemctl --user status moonfold.service, then use the repair command printed by Moonfold.
restart-pending A newer version is installed but the service still runs the previous one. Run moonfold service restart.

On macOS, check System Settings → General → Login Items if the service no longer starts at login. If agent work cannot access Desktop, Documents, or Downloads, it may need Full Disk Access for the moonfold executable listed in ProgramArguments in ~/Library/LaunchAgents/dev.moonfold.app.service.plist.

For failures after signing in to Moonfold Connect, see connection troubleshooting.

Edit this page on GitHub