Mac mini 2020–2024 — OpenClaw Performance Projection
The question isn't whether OpenClaw runs — it's whether it runs well enough for what your colleague actually wants to do with it.
All Mac mini generations + M1 Max reference
| Chip | Memory bandwidth | Released |
|---|---|---|
| M1 | 68.25 GB/s | 2020 |
| M2 | 100 GB/s | 2023 |
| M2 Pro | 200 GB/s | 2023 |
| M4 | 120 GB/s | 2024 |
| M4 Pro | 273 GB/s | 2024 |
| M1 Max (reference) | 400 GB/s | Prior report — not a Mac mini |
M1 Max shown as reference from prior report (not a Mac mini). Token generation scales linearly with bandwidth for memory-bound models.
The prior report found qwen3:32B timed out on bank sessions because it generated only 10–13 tok/s on an M1 Max. That problem disappears with smaller models. A 7B model generates 18–52 tok/s depending on the chip — fast enough that a 10-step browser task completes in 3–5 minutes on every Mac mini here, well inside a 10–15 minute bank session timeout. The constraint shifts from speed to capability: can the model you can fit in your RAM actually navigate complex authenticated flows reliably?
Local Ollama mode · best-fit model per RAM tier
| Config | Bandwidth | Best local model | Tok/s | 10-step time | Cloud | 7B | 14B | Browser auto |
|---|---|---|---|---|---|---|---|---|
| M1 · 68.25 GB/s · Nov 2020 | ||||||||
| M1 / 8 GB | 68 GB/s | 7B Q4 | 18 | 4.3 min | ● | ● marginal | ● won't fit | ● |
| M1 / 16 GB | 68 GB/s | 14B Q4 | 10 | 5.8 min | ● | ● | ● tight | ● |
| M2 · 100 GB/s · Jan 2023 | ||||||||
| M2 / 8 GB | 100 GB/s | 7B Q4 | 25 | 3.8 min | ● | ● marginal | ● won't fit | ● |
| M2 / 16 GB | 100 GB/s | 14B Q4 | 14 | 4.9 min | ● | ● | ● tight | ● |
| M2 Pro · 200 GB/s · Jan 2023 | ||||||||
| M2 Pro / 16 GB | 200 GB/s | 14B Q4 | 22 | 4.0 min | ● | ● | ● tight, fast | ● |
| M2 Pro / 32 GB | 200 GB/s | 14B Q4 | 22 | 4.0 min | ● | ● | ● | ● |
| M4 · 120 GB/s · Nov 2024 | ||||||||
| M4 / 16 GB | 120 GB/s | 14B Q4 | 16 | 4.6 min | ● | ● | ● tight | ● |
| M4 / 24 GB | 120 GB/s | 14B Q4 | 18 | 4.4 min | ● | ● | ● | ● |
| M4 Pro · 273 GB/s · Nov 2024 | ||||||||
| M4 Pro / 24 GB | 273 GB/s | 14B Q4 | 30 | 3.6 min | ● | ● | ● | ● |
| M4 Pro / 48 GB | 273 GB/s | 32B Q4 | 8 | 6.8 min | ● | ● | ● | ● |
Legend: green ● = good · amber ● = marginal/tight · red ● = won't fit / not viable
For your colleague's specific question — setup time is not the risk. OpenClaw installs in minutes on macOS; Ollama pulls a model in one command. The risk is discovering mid-task that their Mac mini doesn't have enough RAM to run a model capable of what they're trying to automate.
Start with cloud API mode. It's zero setup overhead and lets your colleague learn OpenClaw's behavior before betting on a local model. Once they know what they need it to do, they'll know whether a 7B model is sufficient or whether they need 16 GB+ to run a 14B.
The one configuration to avoid for serious local use: 8 GB on any chip. macOS itself consumes 2–3 GB, leaving under 6 GB for a model — enough for a 7B but not for the quality level needed to navigate an authenticated multi-step bank session reliably.