Short version: probably no OpenClaw config change.
MLX is an LM Studio runtime/engine thing. To benefit from it you need to be on Apple Silicon and load an MLX-format / MLX-backed Qwen 3.6 model in LM Studio. If you’re still running a GGUF/llama.cpp build of Qwen, that release note won’t magically switch it to MLX — you’d need to download/select the MLX variant and run that in LM Studio.
For OpenClaw, as long as LM Studio still exposes the same OpenAI-compatible endpoint and model id, nothing changes. If the MLX model has a different id/name in LM Studio, update the configured model string to match whatever LM Studio shows.
Tiny caveat: local models can still be a bit flaky for tool calling, so if OpenClaw starts ignoring tools or producing weird tool JSON after switching runtimes, that’s the first thing I’d suspect — not the endpoint config. Models docs here: https://docs.openclaw.ai/concepts/models