Best Local LLM for OpenClaw: What Actually Runs an Agent in 2026

Ranked local model picks for OpenClaw by RAM tier, the Ollama URL gotcha that breaks tool calling, and the hardware reality most listicles skip.

Published on

Best Local LLM for OpenClaw: What Actually Runs an Agent in 2026
Do not index
The best local LLM for OpenClaw in 2026 is Qwen3.6-27B if you have 24 to 32 GB of RAM, GPT-OSS-20B if you have 16 GB, GLM-4.5-Air at 48 to 64 GB, and GPT-OSS-120B at 96 GB or more. Those picks come from what OpenClaw actually stresses: tool calling, long context, and multi-turn agent loops, not chatbot benchmarks. We run Agent37, a hosting service for OpenClaw, so we watch roughly a thousand live instances run agents every day. Here is what works locally, what breaks, and what to do when your hardware says no.

What OpenClaw demands from a model

OpenClaw is not a chatbot. Every message you send it kicks off an agent loop: a big system prompt, tool schemas, tool calls, tool results, and often ten or more round trips before you get a reply. That workload filters out most of the local model catalog fast.
Three requirements decide everything:
  • Native tool calling. OpenClaw's onboarding only auto-offers an installed Ollama model after confirming it supports tools. Models that emit tool calls as plain text are useless here.
  • Real context. The onboarding gate also requires at least a 16K context window, and Ollama's own OpenClaw integration guide recommends 64K or more. OpenClaw warns you when free context drops below 20 percent and hard-blocks below 10 percent, so a small window means constant stalls.
  • Multi-turn discipline. The OpenClaw docs say it plainly: "Some local models handle simple prompts but struggle with the full agent tool surface." A model that nails one tool call but drifts by round eight will lose constraints mid-task.
So ignore generic leaderboard rankings. What matters is tool-call reliability across long loops, and that is what the picks below are ranked on.

The best local LLM for OpenClaw by RAM tier

Match the model to the machine you actually own. Every model here has native tool support, an open license, and a real presence in the mid-2026 local-agent community.
Your hardware
First pick
Also strong
Why
16 GB RAM or GPU
GPT-OSS-20B
Qwen3.5-9B (sub-16 GB)
14 GB footprint, built for agent loops
24-32 GB
Qwen3.6-27B
GLM-4.7-Flash, Qwen3.6-35B-A3B, Devstral Small 2
The mid-2026 default for local agents
48-64 GB
GLM-4.5-Air (3-bit)
Llama 3.3 70B
Bigger-brain reliability on a 64 GB Mac
96 GB+
GPT-OSS-120B
Qwen3.5-122B-A10B
Strongest local agent brain below datacenter class
192 GB+
DeepSeek V4 Flash
The prosumer ceiling; most people use its API instead
16 GB: GPT-OSS-20B. OpenAI's open-weight model is the consensus starter for this tier. It is a 21B mixture-of-experts model with about 3.6B active parameters, ships at a 14 GB native MXFP4 footprint, and OpenAI states it runs on 16 GB machines. It was built around an agentic format with native function calling, and it appears in the OpenClaw docs' own Ollama examples as gpt-oss:20b. Apache 2.0 license. If even that does not fit, Qwen3.5-9B is the best sub-16 GB tool caller, at roughly 6 GB quantized.
24 to 32 GB: Qwen3.6-27B. This is the sweet spot tier. Qwen3.6-27B was released in April 2026 with explicit agentic training, including reasoning preserved across tool rounds, which is exactly the OpenClaw workload. It pulls at about 17 GB quantized, carries a 256K context window, and is Apache 2.0. Three alternates worth knowing: GLM-4.7-Flash (30B MoE with about 3B active parameters, MIT licensed, and Zhipu reports a 79.5 on tau2-Bench for interactive tool use), Qwen3.6-35B-A3B (same family, sparser and faster, which matters when your agent answers WhatsApp messages), and Devstral Small 2 (Mistral's 24B coding-agent specialist, 68 percent on SWE-bench Verified by Mistral's own count; pick it if your agent mostly runs shell and file tools). If your agent needs to see images, Gemma 4 brings native function calling and full multimodality, and the Qwen3.6 models take image input too; pick Gemma 4 when you want the Google stack.
48 to 64 GB: GLM-4.5-Air. The 64 GB Mac community's favorite agent model, and still current: the GLM-4.6-Air successor Zhipu promised never shipped, and the only Air-sized release since is the vision-focused GLM-4.6V. It is a 106B MoE with about 12B active parameters, MIT licensed, and the community runs 3-bit quants of it on 64 GB unified memory. You get noticeably better multi-turn reliability than any 27B to 35B model. Llama 3.3 70B also fits this tier at Q4 and remains a fine conversationalist, but it predates the 2025-2026 agentic training wave, so expect more drift in long tool loops.
96 GB and up: GPT-OSS-120B. OpenAI's larger open-weight model wants an 80 GB GPU or a 96 GB+ Mac; its 65 GB weights do not leave room on a 64 GB machine once the OS and context take their share. In exchange you get the strongest broadly validated local agent brain short of datacenter hardware. Qwen3.5-122B-A10B is the fast alternative in this tier, with only about 10B active parameters. At 192 GB and beyond, DeepSeek V4 Flash (284B MoE, MIT license) even has a dedicated ds4 backend in OpenClaw for macOS Metal, but at that point you have bought a small server, and most people consume this model through its API.

Models to skip

  • Phi-4. No native tool support, which alone disqualifies it. Its 16K context window is also the bare minimum OpenClaw's onboarding gate accepts, a quarter of what Ollama recommends.
  • Llama 4 Scout and Maverick. Awkward sizes, a lukewarm agentic reputation since launch, and a dead product line. Neither cracks Ollama's most-pulled models in July 2026.
  • DeepSeek R1 distills. Reasoning-only. No reliable native tool calling, which disqualifies them for agent work.
  • Anything under 9B for the full loop. Small models can answer a question; they cannot survive ten tool rounds with a big system prompt.
  • Models that do not exist. SEO content about local models is now heavily polluted with invented names. As of July 2026 there are no Llama 5 weights on Hugging Face, and Meta's frontier releases have gone closed. If a guide recommends "Llama 5" for OpenClaw, close the tab.

Wiring it up, and the one gotcha that breaks tool calling

Most self-hosters serve models with Ollama, so that config comes first; the OpenClaw docs' own pick for the strongest local stack is LM Studio, covered just after.
If you run Ollama, use its native URL. The OpenClaw docs are blunt about this: do not point OpenClaw at Ollama's OpenAI-compatible /v1 endpoint, because it breaks tool calling and models can emit raw tool-call JSON as plain text. Set OLLAMA_API_KEY to any placeholder string; it just switches OpenClaw's model discovery on (ollama-local works for local hosts). Pull your model and OpenClaw finds it automatically, using the model's exact tag from the Ollama library:
{
  agents: {
    defaults: {
      model: {
        primary: "ollama/gpt-oss:20b",
        fallbacks: ["anthropic/claude-opus-4-6"],
      },
    },
  },
}
On LM Studio: the docs currently call LM Studio running a large model the best local stack. Load a full-size Qwen, DeepSeek, or Llama build, enable the local server, and use the Responses API so reasoning stays separate from the text your agent sends to WhatsApp. Whichever backend you choose, keep a hosted fallback in the config like the snippet above, because when a local model chokes mid-loop, a fallback saves the task instead of losing the conversation. For the full setup, including custom OpenAI-compatible endpoints and where API keys live, follow our guide to configure an LLM provider in OpenClaw.

The hardware reality

Here is the part most "best local LLM" listicles skip. The OpenClaw docs put the comfortable hardware floor for a full agent loop at two or more maxed-out Mac Studios or an equivalent GPU rig in the tens of thousands of dollars. A single 24 GB GPU handles lighter prompts at higher latency. That is the project's own assessment, and it matches what we see from agents running on small open-weight models all day: the tiers above genuinely work, but "works" means a personal agent that is helpful and occasionally slow, not a frontier assistant.
Know the failure modes before you commit:
  • Long-horizon drift. Local models lose schema discipline and forget constraints as tool rounds pile up, exactly where hosted frontier models stay coherent.
  • Paper context vs real context. A 256K window on the label degrades well before 256K in practice, and quantization makes it worse.
  • Quantization has a security cost. The docs warn that small or heavily quantized checkpoints truncate context, and local models skip provider-side safety filters, which widens the prompt-injection blast radius. Run the largest variant you can host, and read the OpenClaw security guide before you give a small model exec access.
  • Concurrency. One consumer box serving several chatty agents queues badly.
The pattern the community converged on in 2026 is hybrid routing: the local model handles routine turns and tool dispatch, and a hosted model takes planning and hard steps through the fallback chain. That is also our advice. Local-first is a great setup. Pure local-only works too; you just eat the hard-step failures yourself instead of handing them to a fallback.

No 24 GB GPU? Your options

The models above are free, and OpenClaw is free. What you are really budgeting for is compute plus uptime, because a personal agent only earns its keep when it is reachable at 2 pm and at 2 am.
  • Hardware you already own. A 16 GB or 24 GB machine running GPT-OSS-20B or Qwen3.6-27B is a real local agent for zero new dollars. The catch: when the laptop sleeps, your agent sleeps.
  • Hosted open-weight models. The OpenClaw docs themselves call hosted open-weight variants on OpenRouter the middle ground: you keep model choice and data-routing control, and you skip the hardware bill. Local-only remains the strongest privacy path.
  • Hosted OpenClaw with bundled open-weight models. On Agent37, a Basic instance is $3.99 a month with bring-your-own-key, so you can point it at OpenRouter or any provider on this page. The Plus tier at $9.99 a month bundles GPT-OSS-20B, GPT-OSS-120B, and DeepSeek V4 Flash, three of the exact models ranked above, hosted, with usage capped per rolling 5-hour window plus a weekly cap. One honest caveat: an Agent37 container is a small always-on Linux box that runs OpenClaw itself; it does not have the RAM to run a 27B model inside the container. The bundled models run on our infrastructure, not in your instance.
If the whole point of local is that prompts never leave your house, buy the RAM and run Qwen3.6-27B on your own metal. If the point is an always-on agent with open-weight brains and no hardware project, deploy OpenClaw on Agent37 in one click: always-on, from $3.99 a month.

Keep reading