WeCanBot / Install

Install WeCanBot Base

@wecanbot/base is the WeCanBot base package. Installing adds a UI service, a UI proxy module, and two basic tools to the current OpenClaw instance.

WeCanBot UI Service

Start local UI server and serve the interface via OpenClaw gateway /ui.

UI Proxy Module

Unified proxy for /ui, /_next, /api, /assets serving the WeCanBot UI.

Workspace Files

Save and read workspace files, attachments, and index for agents/sessions.

cs_task

Task distribution entry for subsequent apps like trading.

Version

This determines which release the current install command and product documentation correspond to.

Current v20260503.1

Current Version README · v20260503.1

WeCanBot Base

WeCanBot is an AI agent orchestration platform built on top of OpenClaw.

It is designed to help you move through four levels of capability:

  • Agent: start with a single role for focused work
  • Team: combine multiple roles under one leader
  • Task: split larger work into tracked sub-problems
  • App: turn repeated workflows into reusable automation

@wecanbot/base is the base package that brings this experience into an existing OpenClaw host.

Why Install This Plugin

Install this package if you want OpenClaw to feel less like a raw gateway and more like a usable agent operating environment.

After installation, you get:

  • a local WeCanBot UI mounted under /ui
  • one UI-serving proxy surface for:
    • /ui
    • /_next
    • /api
    • /assets
  • two base tools:
    • workspace_files
    • cs_task

In practical terms, this gives you:

  • a friendlier interface for running and supervising agent work
  • a base file layer for attachments and generated artifacts
  • a shared task entrypoint that later app packages can plug into
  • built-in prompt templates, so you can save common task instructions and send them quickly when needed

What This Package Is Responsible For

This package is the foundation layer only.

Its job is to provide:

  • the WeCanBot UI runtime
  • the UI proxy surface under the OpenClaw gateway
  • the base workspace and task tools

It is not supposed to be the place where every future app or business workflow lives.

How It Fits the Product Story

The platform story is:

  • begin with a single Agent
  • coordinate multiple roles as a Team
  • dispatch scoped work as Tasks
  • expand into reusable Apps

@wecanbot/base is what gives OpenClaw the base UI and tool surface needed for that progression.

Without it, the higher-level WeCanBot experience is not present.

Installation

Recommended official path:

openclaw plugins install clawhub:@wecanbot/base --dangerously-force-unsafe-install

Secondary path:

  • a guided curl | sh flow may be used when a session-based install and verify experience is preferred
  • the intended final installed result is the same as the CLI path

Why It Needs the Capabilities It Uses

This plugin is not a static asset drop.

It will:

  • start a local Node UI process
  • read ~/.clawsh/cs-server.json
  • store workspace files and sqlite metadata for workspace_files
  • keep cs_task available as the shared task entrypoint for later installed apps

These behaviors are part of the product design and should be reviewed before install.

Installation Methods

Recommended

Install via ClawHub

This is the official install method, most direct and easiest to review and execute.

LANG=en openclaw plugins install clawhub:@wecanbot/base@v20260503.1 --dangerously-force-unsafe-install
Alternative

Agent Install

If you cannot use ClawHub smoothly, or need a guided experience with checks.

curl https://www.wecanbot.cloud/api/install/wecanbot-base?code=573509&version=v20260503.1 | sh
Post-Install

Verify

If you installed via agent, after gateway restart, run the following command to verify

curl https://www.wecanbot.cloud/api/install/wecanbot-base/verify?session=ins_sess_b876241fe7435b79 | sh

Permissions & Runtime

Why these capabilities are needed
  • Requires spawning a local Node UI process since OpenClaw only handles mounting and proxying, not frontend runtime.
  • Requires reading local server auth state as the plugin uses the server token to communicate with WeCanBot server.
  • Requires workspace_files because agents need to persist attachments, workspace files, and index when executing tasks.
  • cs_task supports dynamic runtime loading of subsequent apps per configuration, allowing modules like trading to connect to the same task entry after installation.

Install Status

Install
Pending
Verify
Pending
Remote Access
not-tested
Session ID
ins_sess_b876241fe7435b79
Gateway Address
Waiting for install callback