@bitseek/claw 1.2.0 → 1.2.2

package/docs/install/index.md

@@ -75,15 +75,15 @@ For VPS/cloud hosts, avoid third-party "1-click" marketplace images when possibl
     <Tabs>
       <Tab title="npm">
         ```bash
-        npm install -g openclaw@latest
-        openclaw onboard --install-daemon
+        npm install -g @bitseek/claw@latest
+        bitseek-claw onboard --install-daemon
         ```
 
         <Accordion title="sharp build errors?">
           If you have libvips installed globally (common on macOS via Homebrew) and `sharp` fails, force prebuilt binaries:
 
           ```bash
-          SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g openclaw@latest
+          SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g @bitseek/claw@latest
           ```
 
           If you see `sharp: Please add node-gyp to your dependencies`, either install build tooling (macOS: Xcode CLT + `npm install -g node-gyp`) or use the env var above.
@@ -91,9 +91,9 @@ For VPS/cloud hosts, avoid third-party "1-click" marketplace images when possibl
       </Tab>
       <Tab title="pnpm">
         ```bash
-        pnpm add -g openclaw@latest
-        pnpm approve-builds -g        # approve openclaw, node-llama-cpp, sharp, etc.
-        openclaw onboard --install-daemon
+        pnpm add -g @bitseek/claw@latest
+        pnpm approve-builds -g        # approve @bitseek/claw, node-llama-cpp, sharp, etc.
+        bitseek-claw onboard --install-daemon
         ```
 
         <Note>
@@ -130,7 +130,7 @@ For VPS/cloud hosts, avoid third-party "1-click" marketplace images when possibl
       </Step>
       <Step title="Run onboarding">
         ```bash
-        openclaw onboard --install-daemon
+        bitseek-claw onboard --install-daemon
         ```
       </Step>
     </Steps>
@@ -165,9 +165,9 @@ For VPS/cloud hosts, avoid third-party "1-click" marketplace images when possibl
 Verify everything is working:
 
 ```bash
-openclaw doctor         # check for config issues
-openclaw status         # gateway status
-openclaw dashboard      # open the browser UI
+bitseek-claw doctor         # check for config issues
+bitseek-claw status         # gateway status
+bitseek-claw dashboard      # open the browser UI
 ```
 
 If you need custom runtime paths, use:
@@ -178,7 +178,7 @@ If you need custom runtime paths, use:
 
 See [Environment vars](/help/environment) for precedence and full details.
 
-## Troubleshooting: `openclaw` not found
+## Troubleshooting: `bitseek-claw` not found
 
 <Accordion title="PATH diagnosis and fix">
   Quick diagnosis:
@@ -190,7 +190,7 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** in your `$PATH`, your shell can't find global npm binaries (including `openclaw`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** in your `$PATH`, your shell can't find global npm binaries (including `bitseek-claw`).
 
 Fix — add it to your shell startup file (`~/.zshrc` or `~/.bashrc`):
 

package/docs/install/updating.md

@@ -31,7 +31,6 @@ Notes:
 
   The installer will `git pull --rebase` **only** if the repo is clean.
 
-- For **global installs**, the script uses `npm install -g openclaw@latest` under the hood.
 - Legacy note: `clawdbot` remains available as a compatibility shim.
 
 ## Before you update
@@ -48,11 +47,11 @@ Notes:
 Global install (pick one):
 
 ```bash
-npm i -g openclaw@latest
+npm i -g @bitseek/claw@latest
 ```
 
 ```bash
-pnpm add -g openclaw@latest
+pnpm add -g @bitseek/claw@latest
 ```
 
 We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs).
@@ -60,9 +59,9 @@ We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs).
 To switch update channels (git + npm installs):
 
 ```bash
-openclaw update --channel beta
-openclaw update --channel dev
-openclaw update --channel stable
+bitseek-claw update --channel beta
+bitseek-claw update --channel dev
+bitseek-claw update --channel stable
 ```
 
 Use `--tag <dist-tag|version>` for a one-off install tag/version.
@@ -95,27 +94,27 @@ Behavior:
 - `beta`: checks on `betaCheckIntervalHours` cadence (default: hourly) and applies when an update is available.
 - `dev`: no automatic apply; use manual `openclaw update`.
 
-Use `openclaw update --dry-run` to preview update actions before enabling automation.
+Use `bitseek-claw update --dry-run` to preview update actions before enabling automation.
 
 Then:
 
 ```bash
-openclaw doctor
-openclaw gateway restart
-openclaw health
+bitseek-claw doctor
+bitseek-claw gateway restart
+bitseek-claw health
 ```
 
 Notes:
 
-- If your Gateway runs as a service, `openclaw gateway restart` is preferred over killing PIDs.
+- If your Gateway runs as a service, `bitseek-claw gateway restart` is preferred over killing PIDs.
 - If you’re pinned to a specific version, see “Rollback / pinning” below.
 
-## Update (`openclaw update`)
+## Update (`bitseek-claw update`)
 
 For **source installs** (git checkout), prefer:
 
 ```bash
-openclaw update
+bitseek-claw update
 ```
 
 It runs a safe-ish update flow:
@@ -123,16 +122,16 @@ It runs a safe-ish update flow:
 - Requires a clean worktree.
 - Switches to the selected channel (tag or branch).
 - Fetches + rebases against the configured upstream (dev channel).
-- Installs deps, builds, builds the Control UI, and runs `openclaw doctor`.
+- Installs deps, builds, builds the Control UI, and runs `bitseek-claw doctor`.
 - Restarts the gateway by default (use `--no-restart` to skip).
 
-If you installed via **npm/pnpm** (no git metadata), `openclaw update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
+If you installed via **npm/pnpm** (no git metadata), `bitseek-claw update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
 
 ## Update (Control UI / RPC)
 
 The Control UI has **Update & Restart** (RPC: `update.run`). It:
 
-1. Runs the same source-update flow as `openclaw update` (git checkout only).
+1. Runs the same source-update flow as `bitseek-claw update` (git checkout only).
 2. Writes a restart sentinel with a structured report (stdout/stderr tail).
 3. Restarts the gateway and pings the last active session with the report.
 
@@ -145,7 +144,7 @@ From the repo checkout:
 Preferred:
 
 ```bash
-openclaw update
+bitseek-claw update
 ```
 
 Manual (equivalent-ish):
@@ -155,8 +154,8 @@ git pull
 pnpm install
 pnpm build
 pnpm ui:build # auto-installs UI deps on first run
-openclaw doctor
-openclaw health
+bitseek-claw doctor
+bitseek-claw health
 ```
 
 Notes:
@@ -164,13 +163,13 @@ Notes:
 - `pnpm build` matters when you run the packaged `openclaw` binary ([`openclaw.mjs`](https://github.com/openclaw/openclaw/blob/main/openclaw.mjs)) or use Node to run `dist/`.
 - If you run from a repo checkout without a global install, use `pnpm openclaw ...` for CLI commands.
 - If you run directly from TypeScript (`pnpm openclaw ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
-- Switching between global and git installs is easy: install the other flavor, then run `openclaw doctor` so the gateway service entrypoint is rewritten to the current install.
+- Switching between global and git installs is easy: install the other flavor, then run `bitseek-claw doctor` so the gateway service entrypoint is rewritten to the current install.
 
-## Always Run: `openclaw doctor`
+## Always Run: `bitseek-claw doctor`
 
 Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn.
 
-Note: if you’re on a **source install** (git checkout), `openclaw doctor` will offer to run `openclaw update` first.
+Note: if you’re on a **source install** (git checkout), `bitseek-claw doctor` will offer to run `bitseek-claw update` first.
 
 Typical things it does:
 
@@ -187,11 +186,11 @@ Details: [Doctor](/gateway/doctor)
 CLI (works regardless of OS):
 
 ```bash
-openclaw gateway status
-openclaw gateway stop
-openclaw gateway restart
-openclaw gateway --port 18789
-openclaw logs --follow
+bitseek-claw gateway status
+bitseek-claw gateway stop
+bitseek-claw gateway restart
+bitseek-claw gateway --port 18789
+bitseek-claw logs --follow
 ```
 
 If you’re supervised:
@@ -199,7 +198,7 @@ If you’re supervised:
 - macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/ai.openclaw.gateway` (use `ai.openclaw.<profile>`; legacy `com.openclaw.*` still works)
 - Linux systemd user service: `systemctl --user restart openclaw-gateway[-<profile>].service`
 - Windows (WSL2): `systemctl --user restart openclaw-gateway[-<profile>].service`
-  - `launchctl`/`systemctl` only work if the service is installed; otherwise run `openclaw gateway install`.
+  - `launchctl`/`systemctl` only work if the service is installed; otherwise run `bitseek-claw gateway install`.
 
 Runbook + exact service labels: [Gateway runbook](/gateway)
 
@@ -210,20 +209,20 @@ Runbook + exact service labels: [Gateway runbook](/gateway)
 Install a known-good version (replace `<version>` with the last working one):
 
 ```bash
-npm i -g openclaw@<version>
+npm i -g @bitseek/claw@<version>
 ```
 
 ```bash
-pnpm add -g openclaw@<version>
+pnpm add -g @bitseek/claw@<version>
 ```
 
-Tip: to see the current published version, run `npm view openclaw version`.
+Tip: to see the current published version, run `npm view @bitseek/claw version`.
 
 Then restart + re-run doctor:
 
 ```bash
-openclaw doctor
-openclaw gateway restart
+bitseek-claw doctor
+bitseek-claw gateway restart
 ```
 
 ### Pin (source) by date

package/docs/plans/2026-03-11-bitseek-update-package-design.md

@@ -0,0 +1,25 @@
+# BitSeek Update Package Design
+
+## Context
+
+BitSeek Claw now publishes from the npm package `@bitseek/claw`, but the core
+update flow and top-level installation docs still point users to `openclaw`.
+That mismatch can make `bitseek-claw update` suggest or execute the wrong npm
+package spec.
+
+## Decisions
+
+- Make `@bitseek/claw` the default npm package target for package-manager
+  updates.
+- Preserve detection of legacy package roots such as `openclaw` so existing
+  installs can still be recognized safely.
+- Update CLI dry-run output and failure hints to show the BitSeek package spec.
+- Update the main English install and update docs to use `@bitseek/claw`.
+
+## Guardrails
+
+- Do not change the CLI binary name; it remains `bitseek-claw`.
+- Do not touch generated `docs/zh-CN/**`.
+- Do not modify the separate website installer repo in this change.
+- Keep old package-name detection in update helpers so legacy installs do not
+  become invisible to the updater.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bitseek/claw",
-  "version": "1.2.0",
+  "version": "1.2.2",
   "description": "BitSeek-branded OpenClaw distribution with a multi-channel AI gateway",
   "keywords": [],
   "homepage": "https://github.com/adv-org/bitseek-claw#readme",