Setup & Hardening
Install OpenClaw on your machine and secure it properly.
Choose the right setup path first
This page is not just a list of installers. It helps you avoid the wrong path before you lose time.
- •Choose Linux VPS if you want the cheapest always-on setup.
- •Choose native Mac install if you want the fastest first run.
- •Choose Docker if isolation matters more than convenience.
- •Choose WSL2 on Windows, do not try to force a native install.
macOS Installation (M1/M2/M4 Chips)
OpenClaw runs natively on macOS and is optimized for Apple Silicon. The installer will automatically set up Node.js 22+ via Homebrew if needed.
Prerequisites
- macOS 12 or later
- Node.js 22+ (auto-installed if missing)
- Homebrew (recommended for dependencies)
One-Line Install
Run this in Terminal:
curl -fsSL https://molt.bot/install.sh | bash
exec bashThe exec bash restarts your shell to load the new configuration.
Post-Installation Setup
Run the onboarding wizard to configure your gateway, workspace, and channels:
moltbot onboardThe Gateway installs as a launchd service and survives reboots automatically.
Optional: Install via NPM
If you prefer NPM (requires Node.js 22+ already installed):
npm install -g moltbot@latestMac Mini Tip: For always-on operation, a Mac Mini makes an excellent dedicated OpenClaw server. It can run 24/7 with low power consumption.
Fixing the macOS App Crash
If the OpenClaw app disappears or shows "Abort trap 6" when clicking "Allow" on a privacy prompt:
- Use CLI mode instead: Run openclaw gateway start in Terminal
- Reset TCC Cache (if the above doesn't work):
# Quit Moltbot completely # Open Terminal and run: tccutil reset All com.moltbot.gateway # Then re-launch Moltbot - Check Console.app for crash logs if the issue persists.
5-minute preflight check
- Confirm you picked one path: Mac, VPS, Docker, or WSL2, not a hybrid.
- Run onboarding right after install, do not stop at the CLI install.
- Bind to localhost first, then add a reverse proxy if remote access is needed.
- Connect one primary channel first, then expand to more integrations.
Most common setup mistakes
- •Exposing port 8080 directly to the internet without auth or a reverse proxy.
- •Skipping WSL2 on Windows and expecting native install to work.
- •Finishing install but never running onboarding for gateway and channels.
- •Choosing Docker for “simplicity” while ignoring volumes and localhost binding.
OC NEWS