中文 | English

KWeaver DIP

KWeaver DIP is an enterprise-level digital employee platform, built on KWeaver Core. It provides an AI-native environment for developing and managing digital employees on business knowledge networks—for enterprise intelligence that is understandable, executable, and governable.

The platform builds digital employee capabilities on KWeaver Core and OpenClaw.
If you are new to the platform, see the product documentation.

Install, Configure, and Use KWeaver DIP

Notes

KWeaver DIP provides fast installation commands to deploy the services required by KWeaver Core and KWeaver DIP. For the complete installation workflow and resource configuration details, see deploy/README.zh.md.

Install OpenClaw

KWeaver DIP must be used with OpenClaw. OpenClaw supports two installation approaches:

Option 1: Install OpenClaw yourself based on the OpenClaw project and choose a compatible version.
Option 2: Use KWeaver DIP’s installation command to quickly install the bundled OpenClaw version.

Option 1: Install OpenClaw yourself

KWeaver DIP supports OpenClaw v2026.3.11. We recommend using the tested versions from v2026.3.11 to v2026.3.24. OpenClaw iterates quickly; other versions may have compatibility issues. You can install it from https://openclaw.ai or GitHub at https://github.com/openclaw/openclaw.
After installation, run openclaw gateway onboard to initialize OpenClaw.
Set gateway.bind in openclaw.json to "lan". Keep the value of gateway.auth.token, which is required later when configuring the OpenClaw connection in KWeaver DIP.
Run openclaw gateway restart to restart the OpenClaw gateway.
Run openclaw gateway status and record the gateway listen address, which is usually ws://0.0.0.0:18789.
Make sure the machine running deploy.sh can access the OpenClaw config file and workspace directory. Edit deploy/release-manifests/<version>/kweaver-dip.yaml:

dip-studio.values.studio.envFileHostPath: host path of the Studio ENV configuration file
dip-studio.values.studio.openClawHostPath: host path of the .openclaw/ root directory
dip-studio.values.studio.useExternalOpenClaw: whether to use a self-deployed OpenClaw instance

Install mcporter on the OpenClaw host and register the DIP Studio MCP endpoint in ~/.mcporter/mcporter.json:

npm install -g mcporter
mkdir -p ~/.mcporter
vi ~/.mcporter/mcporter.json

Use the following minimal configuration. Replace https://<node-ip>/studio/mcp with the DIP Studio MCP address reachable from the OpenClaw host.

{
  "mcpServers": {
    "dip-studio": {
      "description": "DIP Studio MCP service",
      "baseUrl": "https://<node-ip>/studio/mcp",
      "headers": {
        "Accept": "application/json, text/event-stream",
        "Content-Type": "application/json"
      }
    }
  }
}

Option 2: Use KWeaver DIP’s bundled OpenClaw

Run the KWeaver DIP installation and deployment command below first.
After KWeaver DIP is installed successfully, proceed to Initialize OpenClaw.

Install KWeaver DIP

Run install commands as root or through sudo.

# 1. Disable firewall
systemctl stop firewalld && systemctl disable firewalld

# 2. Disable swap
swapoff -a && sed -i '/ swap / s/^/#/' /etc/fstab

# 3. Set SELinux to permissive if needed
setenforce 0

# 4. Install containerd.io
dnf install containerd.io

# 1. Clone the repository
git clone https://github.com/kweaver-ai/kweaver-dip.git
cd kweaver-dip/deploy

# 2. Install KWeaver DIP
# a) For stability, we recommend installing the latest released version:
bash ./deploy.sh kweaver-dip install --version=0.6.0

# b) To try the latest features, you can also install the main branch:
bash ./deploy.sh kweaver-dip install

# 3. Install Kweaver-SDK
# Skip this step if you install OpenClaw via Option 2
npm install -g @kweaver-ai/kweaver-sdk

# 4. Install OpenClaw DIP extensions
# Skip this step if you install OpenClaw via Option 2
openclaw plugins install ./openclaw-extensions/dip

Option 2: Initialize KWeaver DIP OpenClaw

If you choose to use KWeaver DIP’s bundled OpenClaw, configure OpenClaw after deployment:

Run kubectl get pods -nkweaver | grep dip-studio on the host and copy the POD ID.
Run kubectl exec -it <POD ID> -nkweaver -- /bin/bash on the host to enter the container.
Run openclaw onboard inside the container to initialize OpenClaw.

Configure OpenClaw in KWeaver DIP

Sign in to KWeaver DIP Studio with the admin account first, then follow the UI instructions to finish the OpenClaw configuration.

Note:

If you deploy OpenClaw on the host yourself, use ws://<host-ip>:<port> as the connection address.
If you use the OpenClaw bundled with KWeaver DIP, use ws://127.0.0.1:<port> as the connection address.

Authorization

If you use the OpenClaw bundled with KWeaver DIP, you can skip authorization.

After deployment, authorize OpenClaw to connect with DIP Studio:

Run openclaw devices list and find the pending device shown below:

Pending (1)
┌──────────────────────────────────────┬──────────────────────────────────────────────────┬──────────┬───────────────┬──────────┬────────┐
│ Request                              │ Device                                           │ Role     │ IP            │ Age      │ Flags  │
├──────────────────────────────────────┼──────────────────────────────────────────────────┼──────────┼───────────────┼──────────┼────────┤
│ 3ef1700e-cc91-4978-a980-4fb783925028 │ cc8d2143cf8fcd04161ade9e5161006c410a0bee65f835e2 │ operator │ 192.169.0.104 │ just now │        │
│                                      │ 629792aa584bb119                                 │          │               │          │        │
└──────────────────────────────────────┴──────────────────────────────────────────────────┴──────────┴───────────────┴──────────┴────────┘

Run openclaw devices approve <Request> to approve it.

When you see:

Approved cc8d2143cf8fcd04161ade9e5161006c410a0bee65f835e2629792aa584bb119 (3ef1700e-cc91-4978-a980-4fb783925028)

the authorization has succeeded.

Initialize configuration and use KWeaver DIP

After deployment, sign in to KWeaver DIP:

https://<node-ip>/dip-hub

Default username: admin
Initial password: eisoo.com

Initialization: Use admin to complete the initial system configuration; other accounts can use the system features normally only after this is done. See Admin Quick Start.

Community Reading Path

Read this file for an overall view of the project’s value, goals, and scope of capabilities.
Open each business module directory and read its README.md to learn what each module does.

💬 Community

Scan to join the KWeaver community group

Support & Contact

Contributing: Contributing Guide
Issues: GitHub Issues
License: Apache License 2.0

Kweaver Dip

README