1. Architecture 1 2 3 4 5 6 7 ┌──────────────────────┐ A2A/JSON-RPC ┌───────────────

1. Introduction to OpenViking 1.1 Use Cases Problem How OpenViking Handles It Fragmented context Unified management with a filesystem paradigm: memory, resources, and skills all map to a viking:// virtual directory, so context is managed the way files are High token consumption L0/L1/L2 tiering: the L0 summary (~100 tokens) is

1. Start the Container Set the image 1 export IMAGE=ghcr.io/openclaw/openclaw:2026.3.2 Generate a random token 1 openssl rand -hex 32 Set the gateway token 1 export OPENCLAW_GATEWAY_TOKEN=xxx This token is used for authentication on both the remote web UI and the local TUI. Set directory permissions 1 2 mkdir -p openclaw-home

1. What Skills Are 1 2 3 openclaw skills list Skills (7/51 ready) OpenClaw ships with a number of built-in skills, which you can view with openclaw skills list. The concrete implementations of these Skills can be found at https://github.com/openclaw/openclaw/tree/main/skills. A Skills file mainly describes the Skill’s metadata, when it

1. Preparing the Node Environment Install nvm 1 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash Set the nvm environment variables You need to edit Bash’s config file and add the following: 1 2 3 export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" Install Node 1 nvm install 22 default 2.