--- name: openclaw-local-mac-mini description: Set up OpenClaw locally and run it reliably on a Mac mini for private, always-on local agent workflows. license: MIT metadata: author: devops-skills version: "1.0" --- # OpenClaw Local + Mac mini Setup Use this skill when you want to run [OpenClaw](https://github.com/openclaw/openclaw) on a developer laptop or promote it to a stable Mac mini host. ## Local Setup (any modern dev machine) 1. Clone and enter repository. 2. Follow upstream prerequisites from OpenClaw README (runtime, package manager, model/provider requirements). 3. Create a local environment file from the example and configure keys/endpoints. 4. Install dependencies and run the development command. 5. Validate startup by loading the local UI/API health endpoint. ```bash git clone https://github.com/openclaw/openclaw.git cd openclaw # Follow upstream bootstrap steps in repo docs # cp .env.example .env # # ``` ## Mac mini Production-ish Setup ### Host baseline - Keep macOS updated and enable automatic security updates. - Use wired Ethernet and a UPS for stability. - Enable FileVault and lock down local admin access. - Configure Tailscale or WireGuard for secure remote admin. ### Service operation - Run OpenClaw in a dedicated user account. - Store secrets in macOS Keychain or a managed secret store (avoid plain-text files in shared folders). - Use `tmux` for manual operation or `launchd` for auto-start on reboot. - Keep logs rotated and monitor disk usage. ### launchd pattern (example) Create `/Library/LaunchDaemons/com.openclaw.service.plist` to run startup command from the OpenClaw directory, then: ```bash sudo launchctl load -w /Library/LaunchDaemons/com.openclaw.service.plist sudo launchctl list | rg openclaw ``` ## Validation Checklist - App starts after reboot without manual intervention. - Health check succeeds from local network. - Secrets are not committed and not world-readable. - Access to admin interfaces is restricted to trusted users/devices. ## Troubleshooting Quick Hits - Slow responses: verify model backend availability and local RAM/CPU pressure. - Boot failures: inspect launchd logs and working directory paths. - Auth errors: re-check provider keys, scopes, and endpoint URLs. - Random crashes: pin dependency versions and restart with clean environment. ## Related Skills - [ollama-stack](../ollama-stack/) - Local model serving patterns - [mac-mini-llm-lab](../mac-mini-llm-lab/) - Mac mini reliability and security baseline - [startup-it-troubleshooting](../../it/startup-it-troubleshooting/) - Small-team operational triage