durar-ai 2026.4.4

package/docs/install/node.md

@@ -0,0 +1,144 @@
+---
+title: "Node.js"
+summary: "Install and configure Node.js for Durar — version requirements, install options, and PATH troubleshooting"
+read_when:
+  - "You need to install Node.js before installing Durar"
+  - "You installed Durar but `Durar` is command not found"
+  - "npm install -g fails with permissions or PATH issues"
+---
+
+# Node.js
+
+Durar requires **Node 22.14 or newer**. **Node 24 is the default and recommended runtime** for installs, CI, and release workflows. Node 22 remains supported via the active LTS line. The [installer script](/install#alternative-install-methods) will detect and install Node automatically — this page is for when you want to set up Node yourself and make sure everything is wired up correctly (versions, PATH, global installs).
+
+## Check your version
+
+```bash
+node -v
+```
+
+If this prints `v24.x.x` or higher, you're on the recommended default. If it prints `v22.14.x` or higher, you're on the supported Node 22 LTS path, but we still recommend upgrading to Node 24 when convenient. If Node isn't installed or the version is too old, pick an install method below.
+
+## Install Node
+
+<Tabs>
+  <Tab title="macOS">
+    **Homebrew** (recommended):
+
+    ```bash
+    brew install node
+    ```
+
+    Or download the macOS installer from [nodejs.org](https://nodejs.org/).
+
+  </Tab>
+  <Tab title="Linux">
+    **Ubuntu / Debian:**
+
+    ```bash
+    curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
+    sudo apt-get install -y nodejs
+    ```
+
+    **Fedora / RHEL:**
+
+    ```bash
+    sudo dnf install nodejs
+    ```
+
+    Or use a version manager (see below).
+
+  </Tab>
+  <Tab title="Windows">
+    **winget** (recommended):
+
+    ```powershell
+    winget install OpenJS.NodeJS.LTS
+    ```
+
+    **Chocolatey:**
+
+    ```powershell
+    choco install nodejs-lts
+    ```
+
+    Or download the Windows installer from [nodejs.org](https://nodejs.org/).
+
+  </Tab>
+</Tabs>
+
+<Accordion title="Using a version manager (nvm, fnm, mise, asdf)">
+  Version managers let you switch between Node versions easily. Popular options:
+
+- [**fnm**](https://github.com/Schniz/fnm) — fast, cross-platform
+- [**nvm**](https://github.com/nvm-sh/nvm) — widely used on macOS/Linux
+- [**mise**](https://mise.jdx.dev/) — polyglot (Node, Python, Ruby, etc.)
+
+Example with fnm:
+
+```bash
+fnm install 24
+fnm use 24
+```
+
+  <Warning>
+  Make sure your version manager is initialized in your shell startup file (`~/.zshrc` or `~/.bashrc`). If it isn't, `Durar` may not be found in new terminal sessions because the PATH won't include Node's bin directory.
+  </Warning>
+</Accordion>
+
+## Troubleshooting
+
+### `Durar: command not found`
+
+This almost always means npm's global bin directory isn't on your PATH.
+
+<Steps>
+  <Step title="Find your global npm prefix">
+    ```bash
+    npm prefix -g
+    ```
+  </Step>
+  <Step title="Check if it's on your PATH">
+    ```bash
+    echo "$PATH"
+    ```
+
+    Look for `<npm-prefix>/bin` (macOS/Linux) or `<npm-prefix>` (Windows) in the output.
+
+  </Step>
+  <Step title="Add it to your shell startup file">
+    <Tabs>
+      <Tab title="macOS / Linux">
+        Add to `~/.zshrc` or `~/.bashrc`:
+
+        ```bash
+        export PATH="$(npm prefix -g)/bin:$PATH"
+        ```
+
+        Then open a new terminal (or run `rehash` in zsh / `hash -r` in bash).
+      </Tab>
+      <Tab title="Windows">
+        Add the output of `npm prefix -g` to your system PATH via Settings → System → Environment Variables.
+      </Tab>
+    </Tabs>
+
+  </Step>
+</Steps>
+
+### Permission errors on `npm install -g` (Linux)
+
+If you see `EACCES` errors, switch npm's global prefix to a user-writable directory:
+
+```bash
+mkdir -p "$HOME/.npm-global"
+npm config set prefix "$HOME/.npm-global"
+export PATH="$HOME/.npm-global/bin:$PATH"
+```
+
+Add the `export PATH=...` line to your `~/.bashrc` or `~/.zshrc` to make it permanent.
+
+## Related
+
+- [Install Overview](/install) — all installation methods
+- [Updating](/install/updating) — keeping Durar up to date
+- [Getting Started](/start/getting-started) — first steps after install

package/docs/install/northflank.mdx

@@ -0,0 +1,42 @@
+---
+summary: "Deploy OpenClaw on Northflank with one-click template"
+read_when:
+  - Deploying OpenClaw to Northflank
+  - You want a one-click cloud deploy with browser-based Control UI
+title: "Northflank"
+---
+
+Deploy OpenClaw on Northflank with a one-click template and access it through the web Control UI.
+This is the easiest "no terminal on the server" path: Northflank runs the Gateway for you.
+
+## How to get started
+
+1. Click [Deploy OpenClaw](https://northflank.com/stacks/deploy-openclaw) to open the template.
+2. Create an [account on Northflank](https://app.northflank.com/signup) if you don't already have one.
+3. Click **Deploy OpenClaw now**.
+4. Set the required environment variable: `OPENCLAW_GATEWAY_TOKEN` (use a strong random value).
+5. Click **Deploy stack** to build and run the OpenClaw template.
+6. Wait for the deployment to complete, then click **View resources**.
+7. Open the OpenClaw service.
+8. Open the public OpenClaw URL at `/openclaw` and connect using the configured shared secret. This template uses `OPENCLAW_GATEWAY_TOKEN` by default; if you replace it with password auth, use that password instead.
+
+## What you get
+
+- Hosted OpenClaw Gateway + Control UI
+- Persistent storage via Northflank Volume (`/data`) so `openclaw.json`,
+  per-agent `auth-profiles.json`, channel/provider state, sessions, and
+  workspace survive redeploys
+
+## Connect a channel
+
+Use the Control UI at `/openclaw` or run `openclaw onboard` via SSH for channel setup instructions:
+
+- [Telegram](/channels/telegram) (fastest — just a bot token)
+- [Discord](/channels/discord)
+- [All channels](/channels)
+
+## Next steps
+
+- Set up messaging channels: [Channels](/channels)
+- Configure the Gateway: [Gateway configuration](/gateway/configuration)
+- Keep OpenClaw up to date: [Updating](/install/updating)

package/docs/install/oracle.md

@@ -0,0 +1,158 @@
+---
+summary: "Host Durar on Oracle Cloud's Always Free ARM tier"
+read_when:
+  - Setting up Durar on Oracle Cloud
+  - Looking for free VPS hosting for Durar
+  - Want 24/7 Durar on a small server
+title: "Oracle Cloud"
+---
+
+# Oracle Cloud
+
+Run a persistent Durar Gateway on Oracle Cloud's **Always Free** ARM tier (up to 4 OCPU, 24 GB RAM, 200 GB storage) at no cost.
+
+## Prerequisites
+
+- Oracle Cloud account ([signup](https://www.oracle.com/cloud/free/)) -- see [community signup guide](https://gist.github.com/rssnyder/51e3cfedd730e7dd5f4a816143b25dbd) if you hit issues
+- Tailscale account (free at [tailscale.com](https://tailscale.com))
+- An SSH key pair
+- About 30 minutes
+
+## Setup
+
+<Steps>
+  <Step title="Create an OCI instance">
+    1. Log into [Oracle Cloud Console](https://cloud.oracle.com/).
+    2. Navigate to **Compute > Instances > Create Instance**.
+    3. Configure:
+       - **Name:** `Durar`
+       - **Image:** Ubuntu 24.04 (aarch64)
+       - **Shape:** `VM.Standard.A1.Flex` (Ampere ARM)
+       - **OCPUs:** 2 (or up to 4)
+       - **Memory:** 12 GB (or up to 24 GB)
+       - **Boot volume:** 50 GB (up to 200 GB free)
+       - **SSH key:** Add your public key
+    4. Click **Create** and note the public IP address.
+
+    <Tip>
+    If instance creation fails with "Out of capacity", try a different availability domain or retry later. Free tier capacity is limited.
+    </Tip>
+
+  </Step>
+
+  <Step title="Connect and update the system">
+    ```bash
+    ssh ubuntu@YOUR_PUBLIC_IP
+
+    sudo apt update && sudo apt upgrade -y
+    sudo apt install -y build-essential
+    ```
+
+    `build-essential` is required for ARM compilation of some dependencies.
+
+  </Step>
+
+  <Step title="Configure user and hostname">
+    ```bash
+    sudo hostnamectl set-hostname Durar
+    sudo passwd ubuntu
+    sudo loginctl enable-linger ubuntu
+    ```
+
+    Enabling linger keeps user services running after logout.
+
+  </Step>
+
+  <Step title="Install Tailscale">
+    ```bash
+    curl -fsSL https://tailscale.com/install.sh | sh
+    sudo tailscale up --ssh --hostname=Durar
+    ```
+
+    From now on, connect via Tailscale: `ssh ubuntu@Durar`.
+
+  </Step>
+
+  <Step title="Install Durar">
+    ```bash
+    curl -fsSL https://Durar.ai/install.sh | bash
+    source ~/.bashrc
+    ```
+
+    When prompted "How do you want to hatch your bot?", select **Do this later**.
+
+  </Step>
+
+  <Step title="Configure the gateway">
+    Use token auth with Tailscale Serve for secure remote access.
+
+    ```bash
+    Durar config set gateway.bind loopback
+    Durar config set gateway.auth.mode token
+    Durar doctor --generate-gateway-token
+    Durar config set gateway.tailscale.mode serve
+    Durar config set gateway.trustedProxies '["127.0.0.1"]'
+
+    systemctl --user restart Durar-gateway.service
+    ```
+
+    `gateway.trustedProxies=["127.0.0.1"]` here is only for the local Tailscale Serve proxy's forwarded-IP/local-client handling. It is **not** `gateway.auth.mode: "trusted-proxy"`. Diff viewer routes keep fail-closed behavior in this setup: raw `127.0.0.1` viewer requests without forwarded proxy headers can return `Diff not found`. Use `mode=file` / `mode=both` for attachments, or intentionally enable remote viewers and set `plugins.entries.diffs.config.viewerBaseUrl` (or pass a proxy `baseUrl`) if you need shareable viewer links.
+
+  </Step>
+
+  <Step title="Lock down VCN security">
+    Block all traffic except Tailscale at the network edge:
+
+    1. Go to **Networking > Virtual Cloud Networks** in the OCI Console.
+    2. Click your VCN, then **Security Lists > Default Security List**.
+    3. **Remove** all ingress rules except `0.0.0.0/0 UDP 41641` (Tailscale).
+    4. Keep default egress rules (allow all outbound).
+
+    This blocks SSH on port 22, HTTP, HTTPS, and everything else at the network edge. You can only connect via Tailscale from this point on.
+
+  </Step>
+
+  <Step title="Verify">
+    ```bash
+    Durar --version
+    systemctl --user status Durar-gateway.service
+    tailscale serve status
+    curl http://localhost:18789
+    ```
+
+    Access the Control UI from any device on your tailnet:
+
+    ```
+    https://Durar.<tailnet-name>.ts.net/
+    ```
+
+    Replace `<tailnet-name>` with your tailnet name (visible in `tailscale status`).
+
+  </Step>
+</Steps>
+
+## Fallback: SSH tunnel
+
+If Tailscale Serve is not working, use an SSH tunnel from your local machine:
+
+```bash
+ssh -L 18789:127.0.0.1:18789 ubuntu@Durar
+```
+
+Then open `http://localhost:18789`.
+
+## Troubleshooting
+
+**Instance creation fails ("Out of capacity")** -- Free tier ARM instances are popular. Try a different availability domain or retry during off-peak hours.
+
+**Tailscale will not connect** -- Run `sudo tailscale up --ssh --hostname=Durar --reset` to re-authenticate.
+
+**Gateway will not start** -- Run `Durar doctor --non-interactive` and check logs with `journalctl --user -u Durar-gateway.service -n 50`.
+
+**ARM binary issues** -- Most npm packages work on ARM64. For native binaries, look for `linux-arm64` or `aarch64` releases. Verify architecture with `uname -m`.
+
+## Next steps
+
+- [Channels](/channels) -- connect Telegram, WhatsApp, Discord, and more
+- [Gateway configuration](/gateway/configuration) -- all config options
+- [Updating](/install/updating) -- keep Durar up to date

package/docs/install/podman.md

@@ -0,0 +1,210 @@
+---
+summary: "Run Durar in a rootless Podman container"
+read_when:
+  - You want a containerized gateway with Podman instead of Docker
+title: "Podman"
+---
+
+# Podman
+
+Run the Durar Gateway in a rootless Podman container, managed by your current non-root user.
+
+The intended model is:
+
+- Podman runs the gateway container.
+- Your host `Durar` CLI is the control plane.
+- Persistent state lives on the host under `~/.Durar` by default.
+- Day-to-day management uses `Durar --container <name> ...` instead of `sudo -u Durar`, `podman exec`, or a separate service user.
+
+## Prerequisites
+
+- **Podman** in rootless mode
+- **Durar CLI** installed on the host
+- **Optional:** `systemd --user` if you want Quadlet-managed auto-start
+- **Optional:** `sudo` only if you want `loginctl enable-linger "$(whoami)"` for boot persistence on a headless host
+
+## Quick start
+
+<Steps>
+  <Step title="One-time setup">
+    From the repo root, run `./scripts/podman/setup.sh`.
+  </Step>
+
+  <Step title="Start the Gateway container">
+    Start the container with `./scripts/run-Durar-podman.sh launch`.
+  </Step>
+
+  <Step title="Run onboarding inside the container">
+    Run `./scripts/run-Durar-podman.sh launch setup`, then open `http://127.0.0.1:18789/`.
+  </Step>
+
+  <Step title="Manage the running container from the host CLI">
+    Set `Durar_CONTAINER=Durar`, then use normal `Durar` commands from the host.
+  </Step>
+</Steps>
+
+Setup details:
+
+- `./scripts/podman/setup.sh` builds `Durar:local` in your rootless Podman store by default, or uses `Durar_IMAGE` / `Durar_PODMAN_IMAGE` if you set one.
+- It creates `~/.Durar/Durar.json` with `gateway.mode: "local"` if missing.
+- It creates `~/.Durar/.env` with `Durar_GATEWAY_TOKEN` if missing.
+- For manual launches, the helper reads only a small allowlist of Podman-related keys from `~/.Durar/.env` and passes explicit runtime env vars to the container; it does not hand the full env file to Podman.
+
+Quadlet-managed setup:
+
+```bash
+./scripts/podman/setup.sh --quadlet
+```
+
+Quadlet is a Linux-only option because it depends on systemd user services.
+
+You can also set `Durar_PODMAN_QUADLET=1`.
+
+Optional build/setup env vars:
+
+- `Durar_IMAGE` or `Durar_PODMAN_IMAGE` -- use an existing/pulled image instead of building `Durar:local`
+- `Durar_DOCKER_APT_PACKAGES` -- install extra apt packages during image build
+- `Durar_EXTENSIONS` -- pre-install extension dependencies at build time
+
+Container start:
+
+```bash
+./scripts/run-Durar-podman.sh launch
+```
+
+The script starts the container as your current uid/gid with `--userns=keep-id` and bind-mounts your Durar state into the container.
+
+Onboarding:
+
+```bash
+./scripts/run-Durar-podman.sh launch setup
+```
+
+Then open `http://127.0.0.1:18789/` and use the token from `~/.Durar/.env`.
+
+Host CLI default:
+
+```bash
+export Durar_CONTAINER=Durar
+```
+
+Then commands such as these will run inside that container automatically:
+
+```bash
+Durar dashboard --no-open
+Durar gateway status --deep   # includes extra service scan
+Durar doctor
+Durar channels login
+```
+
+On macOS, Podman machine may make the browser appear non-local to the gateway.
+If the Control UI reports device-auth errors after launch, use the Tailscale guidance in
+[Podman + Tailscale](#podman--tailscale).
+
+<a id="podman--tailscale"></a>
+
+## Podman + Tailscale
+
+For HTTPS or remote browser access, follow the main Tailscale docs.
+
+Podman-specific note:
+
+- Keep the Podman publish host at `127.0.0.1`.
+- Prefer host-managed `tailscale serve` over `Durar gateway --tailscale serve`.
+- On macOS, if local browser device-auth context is unreliable, use Tailscale access instead of ad hoc local tunnel workarounds.
+
+See:
+
+- [Tailscale](/gateway/tailscale)
+- [Control UI](/web/control-ui)
+
+## Systemd (Quadlet, optional)
+
+If you ran `./scripts/podman/setup.sh --quadlet`, setup installs a Quadlet file at:
+
+```bash
+~/.config/containers/systemd/Durar.container
+```
+
+Useful commands:
+
+- **Start:** `systemctl --user start Durar.service`
+- **Stop:** `systemctl --user stop Durar.service`
+- **Status:** `systemctl --user status Durar.service`
+- **Logs:** `journalctl --user -u Durar.service -f`
+
+After editing the Quadlet file:
+
+```bash
+systemctl --user daemon-reload
+systemctl --user restart Durar.service
+```
+
+For boot persistence on SSH/headless hosts, enable lingering for your current user:
+
+```bash
+sudo loginctl enable-linger "$(whoami)"
+```
+
+## Config, env, and storage
+
+- **Config dir:** `~/.Durar`
+- **Workspace dir:** `~/.Durar/workspace`
+- **Token file:** `~/.Durar/.env`
+- **Launch helper:** `./scripts/run-Durar-podman.sh`
+
+The launch script and Quadlet bind-mount host state into the container:
+
+- `Durar_CONFIG_DIR` -> `/home/node/.Durar`
+- `Durar_WORKSPACE_DIR` -> `/home/node/.Durar/workspace`
+
+By default those are host directories, not anonymous container state, so
+`Durar.json`, per-agent `auth-profiles.json`, channel/provider state,
+sessions, and workspace survive container replacement.
+The Podman setup also seeds `gateway.controlUi.allowedOrigins` for `127.0.0.1` and `localhost` on the published gateway port so the local dashboard works with the container's non-loopback bind.
+
+Useful env vars for the manual launcher:
+
+- `Durar_PODMAN_CONTAINER` -- container name (`Durar` by default)
+- `Durar_PODMAN_IMAGE` / `Durar_IMAGE` -- image to run
+- `Durar_PODMAN_GATEWAY_HOST_PORT` -- host port mapped to container `18789`
+- `Durar_PODMAN_BRIDGE_HOST_PORT` -- host port mapped to container `18790`
+- `Durar_PODMAN_PUBLISH_HOST` -- host interface for published ports; default is `127.0.0.1`
+- `Durar_GATEWAY_BIND` -- gateway bind mode inside the container; default is `lan`
+- `Durar_PODMAN_USERNS` -- `keep-id` (default), `auto`, or `host`
+
+The manual launcher reads `~/.Durar/.env` before finalizing container/image defaults, so you can persist these there.
+
+If you use a non-default `Durar_CONFIG_DIR` or `Durar_WORKSPACE_DIR`, set the same variables for both `./scripts/podman/setup.sh` and later `./scripts/run-Durar-podman.sh launch` commands. The repo-local launcher does not persist custom path overrides across shells.
+
+Quadlet note:
+
+- The generated Quadlet service intentionally keeps a fixed, hardened default shape: `127.0.0.1` published ports, `--bind lan` inside the container, and `keep-id` user namespace.
+- It pins `Durar_NO_RESPAWN=1`, `Restart=on-failure`, and `TimeoutStartSec=300`.
+- It publishes both `127.0.0.1:18789:18789` (gateway) and `127.0.0.1:18790:18790` (bridge).
+- It reads `~/.Durar/.env` as a runtime `EnvironmentFile` for values such as `Durar_GATEWAY_TOKEN`, but it does not consume the manual launcher's Podman-specific override allowlist.
+- If you need custom publish ports, publish host, or other container-run flags, use the manual launcher or edit `~/.config/containers/systemd/Durar.container` directly, then reload and restart the service.
+
+## Useful commands
+
+- **Container logs:** `podman logs -f Durar`
+- **Stop container:** `podman stop Durar`
+- **Remove container:** `podman rm -f Durar`
+- **Open dashboard URL from host CLI:** `Durar dashboard --no-open`
+- **Health/status via host CLI:** `Durar gateway status --deep` (RPC probe + extra
+  service scan)
+
+## Troubleshooting
+
+- **Permission denied (EACCES) on config or workspace:** The container runs with `--userns=keep-id` and `--user <your uid>:<your gid>` by default. Ensure the host config/workspace paths are owned by your current user.
+- **Gateway start blocked (missing `gateway.mode=local`):** Ensure `~/.Durar/Durar.json` exists and sets `gateway.mode="local"`. `scripts/podman/setup.sh` creates this if missing.
+- **Container CLI commands hit the wrong target:** Use `Durar --container <name> ...` explicitly, or export `Durar_CONTAINER=<name>` in your shell.
+- **`Durar update` fails with `--container`:** Expected. Rebuild/pull the image, then restart the container or the Quadlet service.
+- **Quadlet service does not start:** Run `systemctl --user daemon-reload`, then `systemctl --user start Durar.service`. On headless systems you may also need `sudo loginctl enable-linger "$(whoami)"`.
+- **SELinux blocks bind mounts:** Leave the default mount behavior alone; the launcher auto-adds `:Z` on Linux when SELinux is enforcing or permissive.
+
+## Related
+
+- [Docker](/install/docker)
+- [Gateway background process](/gateway/background-process)
+- [Gateway troubleshooting](/gateway/troubleshooting)

package/docs/install/railway.mdx

@@ -0,0 +1,90 @@
+---
+summary: "Deploy OpenClaw on Railway with one-click template"
+read_when:
+  - Deploying OpenClaw to Railway
+  - You want a one-click cloud deploy with browser-based Control UI
+title: "Railway"
+---
+
+Deploy OpenClaw on Railway with a one-click template and access it through the web Control UI.
+This is the easiest "no terminal on the server" path: Railway runs the Gateway for you.
+
+## Quick checklist (new users)
+
+1. Click **Deploy on Railway** (below).
+2. Add a **Volume** mounted at `/data`.
+3. Set the required **Variables** (at least `OPENCLAW_GATEWAY_PORT` and `OPENCLAW_GATEWAY_TOKEN`).
+4. Enable **HTTP Proxy** on port `8080`.
+5. Open `https://<your-railway-domain>/openclaw` and connect using the configured shared secret. This template uses `OPENCLAW_GATEWAY_TOKEN` by default; if you replace it with password auth, use that password instead.
+
+## One-click deploy
+
+<a href="https://railway.com/deploy/clawdbot-railway-template" target="_blank" rel="noreferrer">
+  Deploy on Railway
+</a>
+
+After deploy, find your public URL in **Railway → your service → Settings → Domains**.
+
+Railway will either:
+
+- give you a generated domain (often `https://<something>.up.railway.app`), or
+- use your custom domain if you attached one.
+
+Then open:
+
+- `https://<your-railway-domain>/openclaw` — Control UI
+
+## What you get
+
+- Hosted OpenClaw Gateway + Control UI
+- Persistent storage via Railway Volume (`/data`) so `openclaw.json`,
+  per-agent `auth-profiles.json`, channel/provider state, sessions, and
+  workspace survive redeploys
+
+## Required Railway settings
+
+### Public Networking
+
+Enable **HTTP Proxy** for the service.
+
+- Port: `8080`
+
+### Volume (required)
+
+Attach a volume mounted at:
+
+- `/data`
+
+### Variables
+
+Set these variables on the service:
+
+- `OPENCLAW_GATEWAY_PORT=8080` (required — must match the port in Public Networking)
+- `OPENCLAW_GATEWAY_TOKEN` (required; treat as an admin secret)
+- `OPENCLAW_STATE_DIR=/data/.openclaw` (recommended)
+- `OPENCLAW_WORKSPACE_DIR=/data/workspace` (recommended)
+
+## Connect a channel
+
+Use the Control UI at `/openclaw` or run `openclaw onboard` via Railway's shell for channel setup instructions:
+
+- [Telegram](/channels/telegram) (fastest — just a bot token)
+- [Discord](/channels/discord)
+- [All channels](/channels)
+
+## Backups & migration
+
+Export your state, config, auth profiles, and workspace:
+
+```bash
+openclaw backup create
+```
+
+This creates a portable backup archive with OpenClaw state plus any configured
+workspace. See [Backup](/cli/backup) for details.
+
+## Next steps
+
+- Set up messaging channels: [Channels](/channels)
+- Configure the Gateway: [Gateway configuration](/gateway/configuration)
+- Keep OpenClaw up to date: [Updating](/install/updating)