1. Generate a connect command
Open the Execution page in Wemux, create a new executor, and generate a connect command.
Open /execution -> New Executor -> Generate Connect CommandWorker Install
Install a Wemux worker, connect it fast, and finish the first task loop.
This is the shortest onboarding path we want beta users to complete: install a worker, pair it, and prove the first task can come back with real execution output.
Fast path
If this path is slow or confusing, onboarding breaks. The goal is not a long manual. The goal is to get one machine online fast.
2. Run it on the target machine
Choose Local or Docker, then run the generated command on the target machine. For Local, pick macOS/Linux or Windows first. Local install registers a service with auto-restart and auto-update; Docker uses the container restart policy.
# macOS / Linux
curl -fsSL http://127.0.0.1:8989/install | bash -s -- --pairing-code '<PAIRING_CODE>'
# Windows PowerShell
powershell -NoProfile -ExecutionPolicy Bypass -Command "& ([scriptblock]::Create((irm 'http://127.0.0.1:8989/install.ps1'))) -PairingCode '<PAIRING_CODE>'"
# Docker option
curl -fsSL http://127.0.0.1:8989/install/docker | bash -s -- --pairing-code '<PAIRING_CODE>'3. Check the service later
After the service is installed, it restarts automatically on reboot, crash, and worker updates.
$HOME/.wemux-worker/bin/wemux service status
$HOME/.wemux-worker/bin/wemux service logs --follow4. Optional manual fallback
If you prefer the manual path after installing, you can open the local Worker Console and paste only the pairing code there.
$HOME/.wemux-worker/bin/wemux worker open
http://127.0.0.1:481005. Complete the first task
Create one real task, keep execution mode enabled, and route it to the newly paired worker. Confirm that a branch, logs, and reviewable output come back.
Create task -> choose executor -> wait for branch/log/resultCommands
These are the exact commands a beta user is most likely to need during install and pairing.
macOS / Linux install
Installs the worker on macOS or Linux, pairs it, registers a user-level service, and enables service-backed auto-update.
curl -fsSL http://127.0.0.1:8989/install | bash -s -- --pairing-code '<PAIRING_CODE>'Windows install (limited support)
Installs the worker on Windows, pairs it, registers a scheduled background service, and enables service-backed auto-update. ⚠️ The current version has limited compatibility with native Windows — we recommend using WSL (Windows Subsystem for Linux) or choosing the macOS / Linux target instead.
powershell -NoProfile -ExecutionPolicy Bypass -Command "& ([scriptblock]::Create((irm 'http://127.0.0.1:8989/install.ps1'))) -PairingCode '<PAIRING_CODE>'"Docker connect command
Runs the worker inside node:22-bookworm-slim, persists install state in a Docker volume, and lets idle workers self-update through the container restart policy.
curl -fsSL http://127.0.0.1:8989/install/docker | bash -s -- --pairing-code '<PAIRING_CODE>'Installed binary
Installed worker binary path used for service management and manual diagnostics.
$HOME/.wemux-worker/bin/wemuxManual console path
Manual fallback after installation when you want to open the local console or run the daemon in foreground.
$HOME/.wemux-worker/bin/wemux worker open
$HOME/.wemux-worker/bin/wemux worker daemonSuccess checklist
If any item below is false, the onboarding is not complete yet.
- A connect command is generated in /execution.
- The command runs successfully on the target machine.
- Later restarts can reuse the same connect command because old pairing codes are ignored after the first successful pairing.
- The paired machine shows online or paired in the executor list.
- The first task returns logs, branch output, and a review path.
Related pages
These links connect install intent back to product framing and beta conversion.