GoKawiilUnless you’ve been living under a rock, OpenClaw has dominated headlines, both good and bad , for much of early 2026. Developed by Peter Steinberger, the tool is an engine that spins up an AI agent that can autonomously act on your behalf, going so far as having the ability to run files, browse the web, and much more. Using a system named “Skills,” you can even teach your AI assistant to perform new tasks, with more integrations popping up daily. But how useful is it for the average person? I took it upon myself to answer that question by using the relatively humble Beelink SER10 MAX mini PC, which comes pre-installed with OpenClaw, to find out.
To kick things off, when setting up your OpenClaw installation, there’s a fairly large decision one has to make: Do you want to rely on Cloud resources and more powerful AI models, or run something locally? Beelink’s SER10 MAX ships with Qwen-3.5 9B, which is a relatively older and more outdated AI model. Since I want to keep things fairly simple, I opted for the local AI route first. To run larger models, you’ll need a lot of memory, so I first tweaked the humble Mini PC’s video memory up to 48GB, which should allow us to keep a larger, more complex model in memory. It also leaves us 16GB of system memory to play around with, which should be more than enough to run the terminal and ensure that everything else works as intended.
Selecting the ideal local AI model
Having 48GB of available video memory should allow us to run a fairly powerful AI model on the system. However, the downside of running a larger model is that token speeds are likely to be slightly lower than expected. However, for running the super-smart AI that does things for us locally, we want as much intelligence as we can get. For this exercise, I chose Google Gemma 4 31B (UD-Q8_K_XL), a near-lossless quantization, somewhat ambitiously, as I will learn shortly.
Latest Videos From Tom's Hardware Watch full video here:
After downloading the model and running it in llama.cpp, we managed to attain 2.34 tok/s. On average, everyday queries took 116 tokens to generate, at 2.34 tok/s. That’s still too slow for fast everyday use. So, I took a deep breath and conceded that the humble Ryzen AI 9 HX 470 didn’t have fast enough memory or memory bandwidth to run such a large model at acceptable token speeds. Even if I had dropped the quantization to 4-bit, we’re still looking at the theoretical maximum of around 5 tok/s for that model in particular. If you had a faster machine with rapid RAM speeds, such as a Strix Halo system like the Framework Desktop , it might be more workable, but for a lower-end piece of silicon with relatively humble DDR5-5600 speeds, you’ll just have to accept a slightly more neutered model.
So, I eventually conceded that the smaller Gemma 12B (Q4_K_M) was a much more sensible choice for a device of this caliber. After loading things up into llama.cpp, we managed to get a much more sensible 10.64 tok/s on a general knowledge query: “What is Tom’s Hardware?” Now that I have a little piece of talking electrified sand on my desk, it’s time to configure OpenClaw.
Hatching HammerClaw
(Image credit: OpenClaw)
The device I am using, the Beelink SER10 MAX, comes with OpenClaw pre-installed. The only real dependency it has is llama.cpp, which we configured earlier while testing which AI model to use. Since the llama.cpp port is open, OpenClaw leverages that to talk to the AI model, with all of its additional fanciness included. The OpenClaw installer is fairly straightforward in getting things up and running, including setting up a Telegram channel to communicate with our AI model remotely and configuring a gateway, so we can configure things without relying on Ubuntu’s terminal commands.
... continue reading