Run OpenClaw with a Local LLM on macOS – Guide for 16–24GB RAM

A new guide walks through setting up OpenClaw with a local LLM on macOS, specifically targeting machines with 16–24GB RAM. The author tested a quantized version of Qwen 3.5 configured for OpenClaw, and includes a test skill to confirm everything is working.
Setup Overview
- Model: Qwen 3.5 (quantized) – chosen to fit within 16–24GB RAM while providing decent reasoning capability.
- Platform: macOS (tested on Mac Mini with 16–24GB).
- Key step: Configure OpenClaw to use the local model endpoint (typically via Ollama or llama.cpp). The guide provides specific config file edits.
Test Skill
To validate the setup, the author created a test skill that calls the local model and returns a known response. If the skill executes correctly, your local LLM is fully integrated with OpenClaw.
Why Local LLM?
Running an LLM locally avoids API costs and latency, keeps code and prompts on-device, and works offline. For OpenClaw users with Apple Silicon Macs, quantized models like Qwen 3.5 are a practical compromise between accuracy and memory.
Next Steps
If the test skill fails, check your model server (Ollama) is running and the OpenClaw config points to the correct URL (http://localhost:11434 for Ollama). Adjust context window size if needed to fit memory.
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw Failure Patterns: 42 Real Incidents in 28 Days
A developer running OpenClaw daily documented 42 specific failures across eight categories, including AI hallucinations, authentication breakdowns, and automation that costs more time than it saves. The source provides concrete examples like Google OAuth 7-day token expiration and Opus 4.6 adding unwanted metadata to files.

OpenClaw Ollama Cloud: Three-Layer Fix for Missing Models and Doctor Delete Bug
A clean install of OpenClaw with Ollama Cloud models failed: only kimi-k2.5 worked, configs disappeared. Root cause: providers list missing, name field required, and 'openclaw doctor --fix' deletes your provider block.

Fix for 'VM Service Not Running' error in Cowork on Windows 11
A Reddit user shares a PowerShell command fix for the 'VM Service Not Running' error in Cowork when Hyper-V is installed but the hypervisor isn't launching at boot. The solution involves checking hypervisorlaunchtype and setting it to auto.

GitHub Repo Owners: Use Git's --author Flag to Block AI Bot Spam
Archestra fought AI comment/PR spam by exploiting GitHub's 'prior contributors' setting and Git's --author flag to whitelist real humans via a captcha-based onboarding flow.