Who is this for?

This is an advanced topic for developers who want to extend OpenClaw into a customizable local-first assistant with persistent memory, document RAG, explicit browser search, deterministic routing, and proactive scheduling.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Explain the local and external data boundaries of an OpenClaw-based runtime.
  • Deploy and validate the reference runtime with local vLLM inference on NVIDIA DGX Spark.
  • Verify persistent memory, document RAG, explicit browser search, deterministic routing, and proactive scheduling with Telegram and Qdrant.
  • Optionally move the same application workflows to a CPU-only Armv9 system through an OpenAI-compatible llama.cpp endpoint.

Prerequisites

Before starting, you'll need the following prerequisites:

  • An NVIDIA DGX Spark system with NVIDIA drivers, Docker and NVIDIA Container Toolkit
  • Administrative access on DGX Spark
  • Access to Telegram through a mobile, desktop, or web client
  • Familiarity with Linux, Docker Compose, and command-line tools
  • (Optional) A Radxa Orion O6 or comparable CPU-only Armv9 system running Debian 12, Docker, and at least 30 GB of memory

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll extend OpenClaw into a local-first assistant that runs across Arm platforms with local inference and explicit external-data boundaries. First, you’ll prepare a DGX Spark with Docker, Ollama, Qdrant, and vLLM. Then, you’ll validate memory and document RAG, browser search, weather, routing, and scheduled notifications. You can optionally move the same workflows to a CPU-only Armv9 system with an OpenAI-compatible llama.cpp endpoint.