English

简体中文

English

简体中文

Appearance

​

Preface ​

  • Use the Network Disk 🚀 to download our provided .img image file from the System Images/ directory.

  • The Ubuntu24 image used in this document is: TaishanPi-3M-RK3576_Ubuntu24-GNOME_AP6256.img

🦞 OpenClaw installation demo version is: v2026.3.28 (f9b1079)

Flash Image to Development Board ​

Refer to Finished Image Flashing to flash the downloaded image file to the development board.

Run Installation Script ​

OpenClaw official provides an installation script method to install OpenClaw:

Note:

  1. This step requires the development board to have internet access.
  2. It is recommended to use SSH to connect to the development board's terminal to execute the installation command, to avoid serial port data interfering with the interaction during installation.

If the domestic network environment cannot access the official Node.js source, you can first run the following command to install Node.js and npm:

bash
NODE_VERSION=24.14.1
curl -#fL https://npmmirror.com/mirrors/node/v${NODE_VERSION}/node-v${NODE_VERSION}-linux-arm64.tar.xz \
  -o /tmp/node.tar.xz && \
  sudo tar -xJ -C /usr/local --strip-components=1 -f /tmp/node.tar.xz
Result [Click to expand]
bash
lckfb@localhost:~$ NODE_VERSION=24.14.1
curl -#fL https://npmmirror.com/mirrors/node/v${NODE_VERSION}/node-v${NODE_VERSION}-linux-arm64.tar.xz \
  -o /tmp/node.tar.xz && \
  sudo tar -xJ -C /usr/local --strip-components=1 -f /tmp/node.tar.xz
################################### 100.0%
################################### 100.0%
lckfb@localhost:~$ node -v
v24.14.1
lckfb@localhost:~$ npm -v
11.11.0

Execute OpenClaw installation script:

Here we use npm config set registry to specify the use of a domestic npm mirror source to install OpenClaw to speed up the installation process.

bash
npm config set registry https://registry.npmmirror.com/ && \
  curl -fsSL https://openclaw.ai/install.sh | bash
Result [Click to expand]
bash
lckfb@localhost:~$ npm config set registry https://registry.npmmirror.com/ && \
  curl -fsSL https://openclaw.ai/install.sh | bash

  🦞 OpenClaw Installer
  I'll do the boring stuff while you dramatically stare at the logs like it's cinema.

✓ Detected: linux

Install plan
OS: linux
Install method: npm
Requested version: latest

[1/3] Preparing environment
✓ Node.js v24.14.1 found
· Active Node.js: v24.14.1 (/usr/local/bin/node)
· Active npm: 11.11.0 (/usr/local/bin/npm)

[2/3] Installing OpenClaw
✓ Git already installed
· Installing OpenClaw v2026.3.28

✓ OpenClaw npm package installed
✓ OpenClaw installed

[3/3] Finalizing setup

! PATH missing npm global bin dir: /home/lckfb/.npm-global/bin
  This can make openclaw show as "command not found" in new terminals.
  Fix (zsh: ~/.zshrc, bash: ~/.bashrc):
    export PATH="/home/lckfb/.npm-global/bin:$PATH"

🦞 OpenClaw installed successfully (OpenClaw 2026.3.28 (f9b1079))!
Finally unpacked. Now point me at your problems.

After installation is complete, you will enter the onboarding interface:

Basic Configuration ​

In the onboarding interface, we need to perform some basic configuration to make OpenClaw usable. Other settings can be changed later.

Operation Instructions

On the guide page, navigation is mainly done using the Up/Down/Left/Right arrow keys on the keyboard, Space to select, Enter to confirm selection.

Accept Risk ​

Select Yes and press Enter to confirm.

bash
◆  I understand this is personal-by-default and shared/multi-user use requires lock-down. Continue?
│  ● Yes / ○ No
└

Select Quick Start ​

Select QuickStart and press Enter to confirm.

bash
◆  Onboarding mode
│  ● QuickStart (Configure details later via openclaw configure.)
│  ○ Manual
└

Select Model ​

Here we can skip the model configuration directly. We will configure it later via the OpenClaw Model API Configuration document. So select Skip for now and press Enter to confirm.

bash

◆  Model/auth provider
.....
│  ● Skip for now
└

Select all providers for model supplier:

bash
◆  Filter models by provider
│  ● All providers
.....
└

For the default model, we can just keep it as is. We will modify it in the detailed configuration later:

bash

◆  Default model
│  ● Keep current (default: anthropic/claude-opus-4-6)
......
└

Channel Configuration ​

In OpenClaw, a channel (Channel) is the bridge connecting users with the AI assistant. Configuring channels allows users to interact with OpenClaw through familiar communication platforms (sending messages).

Here we can skip the configuration directly. We will configure it later via the OpenClaw Feishu Channel Configuration document. So select Skip for now and press Enter to confirm.

bash
◆  Select channel (QuickStart)
......
│  ● Skip for now (You can add channels later via `openclaw channels add`)
└

Configure Search Provider ​

Let's skip this for now and select Skip for now. Later we can add it via command.

bash
◆  Search provider
│  ○ Brave Search
│  ○ DuckDuckGo Search (experimental)
│  ○ Exa Search
│  ○ Firecrawl Search
│  ○ Gemini (Google Search)
│  ○ Grok (xAI)
│  ○ Kimi (Moonshot)
│  ○ Perplexity Search
│  ○ Tavily Search
│  ● Skip for now (Configure later with openclaw configure --section web)
└

Configure Skills ​

Select No to skip configuration. Later, through conversation, we can let OpenClaw configure its own Skills. We don't need to do it ourselves:

bash
◆  Configure skills now? (recommended)
│  ○ Yes / ● No
└

Hook Configuration ​

Select all configurations using Space, then press Enter to confirm:

bash

◆  Enable hooks?
│  ◻ Skip for now
│  ◼ 🚀 boot-md (Run BOOT.md on gateway startup)
│  ◼ 📎 bootstrap-extra-files (Inject additional workspace bootstrap files via glob/path patterns)
│  ◼ 📝 command-logger (Log all command events to a centralized audit file)
│  ◼ 💾 session-memory (Save session context to memory when /new or /reset command is issued)
└

Hatch Configuration ​

We select Do this later to skip this configuration. Let's not open the chat box with the bot for now and talk about it later.

  • Hatch in TUI (recommended): Chat directly in the terminal
  • Open the Web UI: Open the browser web version
  • Do this later: Exit for now and talk about it later
bash
◆  How do you want to hatch your bot?
│  ○ Hatch in TUI (recommended)
│  ○ Open the Web UI
│  ● Do this later
└

Complete Installation ​

Follow-up Configuration ​

After completing the installation, we need to run source ~/.bashrc for the first time to load environment variables, so that we can use the openclaw command:

bash
source ~/.bashrc

Access UI Interface ​

To access the OpenClaw UI interface, we need to set configuration parameters to allow access within the LAN:

You can use openclaw help to view the usage instructions for the openclaw command.

bash
# 1. Set network access mode to LAN
openclaw config set gateway.bind lan

# 2. Set HTTP access downgrade to true, allow insecure HTTP access (if this parameter is not set, HTTP access is prohibited by default)
openclaw config set gateway.controlUi.allowInsecureAuth true
openclaw config set gateway.controlUi.dangerouslyDisableDeviceAuth true
openclaw config set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback true

# 3. Restart OpenClaw gateway to apply the configuration
openclaw gateway restart

Use the following command to view the Dashboard URL for accessing OpenClaw via LAN:

This command will automatically open the default browser on the board to access the OpenClaw UI interface. So after seeing the related address, we can use Ctrl + C to terminate this command.

bash
openclaw dashboard --no-open

The access address is generally http://<Development Board IP Address>:18789/#token=<token>. Enter this address in the browser to access the OpenClaw UI interface:

  • Use the ifconfig command to view <Development Board IP Address>. Replace the original 127.0.0.1 with it to access within the LAN.

  • <token> is an access token used to verify user access permissions, ensuring that only authorized users can access the OpenClaw UI interface. Every time OpenClaw is installed or reset, this token changes. So you need to use the latest token to access the UI interface. The access address we obtained using the openclaw dashboard command contains the latest token. You can directly use this address to access the UI interface.

bash
# Before replacement:
http://127.0.0.1:18789/#token=65e93827a9dc220819dca1324ef14fe4616ba3e94aa68d7c

# After replacement:
http://192.168.137.60:18789/#token=65e93827a9dc220819dca1324ef14fe4616ba3e94aa68d7c

Last updated: