@clawling/clawchat-plugin-openclaw 2026.9.18-1 → 2026.9.22-1

package/dist/src/activation-greeting.js

@@ -1,6 +1,7 @@
 import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
+import { languageDisplayName } from "./owner-language.js";
 // Worded to make the greeting the single required action. Earlier wording
 // ("ClawChat activation bootstrap: ... do both ...") led some agents to treat
 // it as a setup task and write a `BOOTSTRAP.md` file instead of replying, so
@@ -15,13 +16,27 @@ const ACTIVATION_BOOTSTRAP_FALLBACK = [
 ].join("\n");
 // Cross-plugin, user-editable override read lazily so edits apply on the next
 // first-load without a restart. Any read failure falls back to the built-in text.
-export function buildActivationBootstrapText(homeDir = os.homedir()) {
+// The override does NOT fully replace the built-in text: when the owner's
+// language is known a trailing instruction is appended (see below), because the
+// override says what to say, not which language to say it in — that's a
+// cross-cutting concern the user did not opt out of by supplying their own
+// greeting.
+//
+// `language` is nullable and defaults to null on purpose. The owner-profile
+// cache is cold on a fresh install, and this prompt is dispatched immediately
+// on connect without awaiting it, so the caller often has NO locale. Asserting
+// "Reply in English." to an owner who never said they speak English is worse
+// than asserting nothing — with no line the model infers the language from
+// context, which is what it did before this feature existed. So: unknown
+// language ⇒ no line at all.
+export function buildActivationBootstrapText(homeDir = os.homedir(), language = null) {
     const greetingPath = path.join(homeDir, "clawchat", "greeting.md");
+    let base = ACTIVATION_BOOTSTRAP_FALLBACK;
     try {
         const raw = fs.readFileSync(greetingPath);
         const override = new TextDecoder("utf-8", { fatal: true }).decode(raw).trim();
         if (override.length > 0) {
-            return override;
+            base = override;
         }
     }
     catch (error) {
@@ -30,5 +45,7 @@ export function buildActivationBootstrapText(homeDir = os.homedir()) {
             console.warn(`clawchat.greeting failed to read override ${greetingPath}:`, error);
         }
     }
-    return ACTIVATION_BOOTSTRAP_FALLBACK;
+    if (language === null)
+        return base;
+    return `${base}\n\nReply in ${languageDisplayName(language)}.`;
 }

package/dist/src/friend-greeting.js

@@ -16,6 +16,7 @@ import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
 import { EVENT } from "./protocol-types.js";
+import { languageDisplayName } from "./owner-language.js";
 export const FRIEND_GREETING_FALLBACK = [
     "A ClawChat user has just become your friend. You are now in a direct conversation with them; they are not your owner.",
     "Reply now with one short, friendly greeting message in this conversation: introduce yourself by name, say you are an AI agent acting on behalf of your owner, and invite them to tell you what they need.",
@@ -24,14 +25,20 @@ export const FRIEND_GREETING_FALLBACK = [
 ].join("\n");
 // Cross-plugin, user-editable override read lazily so edits apply on the next
 // friend without a restart. Any read failure falls back to the built-in text.
-// Mirrors `buildActivationBootstrapText` (`~/clawchat/greeting.md`).
-export function buildFriendGreetingText(homeDir = os.homedir()) {
+// Mirrors `buildActivationBootstrapText` (`~/clawchat/greeting.md`), including
+// its nullable `language`: the override does NOT fully replace the built-in
+// text — when the owner's language is known a trailing instruction is appended
+// (see below), because the override says what to say, not which language to say
+// it in. When it is NOT known the line is omitted entirely rather than guessed;
+// see `buildActivationBootstrapText` for why "en" is the wrong guess here.
+export function buildFriendGreetingText(homeDir = os.homedir(), language = null) {
     const greetingPath = path.join(homeDir, "clawchat", "friend-greeting.md");
+    let base = FRIEND_GREETING_FALLBACK;
     try {
         const raw = fs.readFileSync(greetingPath);
         const override = new TextDecoder("utf-8", { fatal: true }).decode(raw).trim();
         if (override.length > 0) {
-            return override;
+            base = override;
         }
     }
     catch (error) {
@@ -40,7 +47,9 @@ export function buildFriendGreetingText(homeDir = os.homedir()) {
             console.warn(`clawchat.friend-greeting failed to read override ${greetingPath}:`, error);
         }
     }
-    return FRIEND_GREETING_FALLBACK;
+    if (language === null)
+        return base;
+    return `${base}\n\nReply in ${languageDisplayName(language)}.`;
 }
 /**
  * Synthetic inbound envelope for the friend greeting turn. Same invariant as
@@ -49,8 +58,8 @@ export function buildFriendGreetingText(homeDir = os.homedir()) {
  * refused at the outbound boundary after a full LLM turn has been spent.
  */
 export function buildFriendGreetingEnvelope(params) {
-    const { account, conversationId, friendUserId } = params;
-    const text = buildFriendGreetingText();
+    const { account, conversationId, friendUserId, language } = params;
+    const text = buildFriendGreetingText(undefined, language);
     const now = Date.now();
     return {
         version: "2",

package/dist/src/liveware-sample.js

@@ -13,6 +13,7 @@ import { DEFAULT_SKILLS_REF, OFFICIAL_SKILLS_BASE } from "./skill-update.js";
 import { livewareCliEnv } from "./liveware-cli.js";
 import { DEFAULT_ACCOUNT_ID } from "openclaw/plugin-sdk/setup";
 import { normalizeOpenclawClawlingAccountId } from "./config.js";
+import { resolveOwnerLanguage } from "./owner-language.js";
 export const LIVEWARES_TARGET = "openclaw";
 export const LIVEWARE_SAMPLE_ID = "liveware-sample";
 export const LIVEWARE_SAMPLE_APP_NAME = "Liveware Sample";
@@ -568,10 +569,51 @@ export async function livewareAppCreate(opts) {
         throw new Error(`liveware app create: cannot parse app id from output: ${stdout.slice(0, 500)}`);
     return appId;
 }
-export const LIVEWARE_SAMPLE_INTRO_TEXT = "我给你安装了一个 liveware 演示应用「Liveware Sample」。" +
-    "入口：在我们的对话页面，点右上角的「应用」按钮（✦），在打开的面板里选名为「Liveware Sample」的应用。" +
-    "页面上有完整的使用引导，试试对我说：把标题改成 Hello Liveware。" +
-    "你在页面上点的按钮、提交的留言我也能看到，随时问我。";
+/** Last-resort copy when the content tree's table cannot be read. English only:
+ *  a second full translation set in-process would be a competing source of truth. */
+export const LIVEWARE_SAMPLE_INTRO_FALLBACK_EN = "I've installed a liveware demo app for you — \"Liveware Sample\". " +
+    "To open it: in our chat, tap the Apps button (✦) in the top-right corner, " +
+    "then pick \"Liveware Sample\" in the panel. " +
+    "The page has a full walkthrough — try saying to me: Change the title to Hello Liveware. " +
+    "I can also see the buttons you tap and the notes you submit there, so just ask me anytime.";
+/** Read the localized intro from the installed sample's `intro.i18n.json`.
+ *  Any failure returns the English fallback — delivery must never be blocked
+ *  by a content-tree problem.
+ *
+ *  Every one of the four degradation modes (missing file / corrupt JSON /
+ *  missing key / empty value) warns first. Falling back silently means a
+ *  mistake in the content tree ships English to every non-English owner with
+ *  zero signal anywhere; the fallback is the safety net, not the plan. Kept
+ *  symmetric with `load_intro_text` in the hermes plugin. */
+export function loadIntroText(appDir, language) {
+    const tablePath = path.join(appDir, "intro.i18n.json");
+    let raw;
+    try {
+        raw = fs.readFileSync(tablePath, "utf8");
+    }
+    catch (error) {
+        console.warn(`clawchat.liveware-sample intro table unreadable at ${tablePath}; using the English fallback:`, error);
+        return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+    }
+    let value;
+    try {
+        const table = JSON.parse(raw);
+        value = table?.intro?.[language];
+    }
+    catch (error) {
+        console.warn(`clawchat.liveware-sample intro table at ${tablePath} is not valid JSON; using the English fallback:`, error);
+        return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+    }
+    if (typeof value !== "string") {
+        console.warn(`clawchat.liveware-sample intro table at ${tablePath} has no "${language}" entry; using the English fallback`);
+        return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+    }
+    if (value.trim().length === 0) {
+        console.warn(`clawchat.liveware-sample intro table at ${tablePath} has an empty "${language}" entry; using the English fallback`);
+        return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+    }
+    return value;
+}
 const DEFAULT_SAMPLE_PORT = 43110;
 const RESTART_WINDOW_MS = 30 * 60 * 1000;
 const MAX_RESTARTS_PER_WINDOW = 5;
@@ -1007,7 +1049,8 @@ export class LivewareSampleSupervisor {
         const { deps } = this;
         let delivered = false;
         try {
-            delivered = await deps.notifyOwner(LIVEWARE_SAMPLE_INTRO_TEXT);
+            const language = resolveOwnerLanguage(deps.resolveOwnerLocale?.() ?? null);
+            delivered = await deps.notifyOwner(loadIntroText(path.join(deps.sampleRoot, "app"), language));
         }
         catch (err) {
             deps.log?.debug?.(`liveware-sample: intro send error: ${String(err)}`);

package/dist/src/owner-language.js

@@ -0,0 +1,54 @@
+/**
+ * Resolve the owner's reported app language into one of the six languages the
+ * ClawChat content tree carries. `agent_owner_locale` comes from the owner's
+ * ClawChat app setting and is omitted entirely when they never reported one —
+ * every unresolvable case lands on English rather than guessing.
+ */
+export const OWNER_LANGUAGES = [
+    "en", "es", "ja", "ko", "zh", "zh_Hant",
+];
+const DISPLAY_NAMES = {
+    en: "English",
+    es: "Spanish",
+    ja: "Japanese",
+    ko: "Korean",
+    zh: "Simplified Chinese",
+    zh_Hant: "Traditional Chinese",
+};
+// Traditional-Chinese regions must be tested before the bare `zh` prefix,
+// because they also start with "zh".
+const TRADITIONAL_PREFIXES = ["zh-hant", "zh-tw", "zh-hk", "zh-mo"];
+export function resolveOwnerLanguage(locale) {
+    const tag = String(locale ?? "").trim().toLowerCase().replace(/_/g, "-");
+    if (!tag)
+        return "en";
+    if (TRADITIONAL_PREFIXES.some((p) => tag.startsWith(p)))
+        return "zh_Hant";
+    if (tag.startsWith("zh"))
+        return "zh";
+    if (tag.startsWith("ja"))
+        return "ja";
+    if (tag.startsWith("ko"))
+        return "ko";
+    if (tag.startsWith("es"))
+        return "es";
+    return "en";
+}
+export function languageDisplayName(lang) {
+    return DISPLAY_NAMES[lang];
+}
+/**
+ * Resolve a locale ONLY when one was actually reported; `null` otherwise.
+ *
+ * `resolveOwnerLanguage` must answer with a language because the intro lookup
+ * has to pick one copy and `en` is the documented default. The greeting path
+ * is the opposite case: the language line is an explicit assertion to the
+ * model, and the owner-profile cache is COLD on a fresh install (the
+ * activation row is written without a locale and the bootstrap fires
+ * immediately on connect). Collapsing "unknown" into "en" there tells a
+ * Chinese owner's agent to reply in English. Callers on the greeting path use
+ * this and omit the line entirely when it returns null.
+ */
+export function resolveOwnerLanguageIfKnown(locale) {
+    return String(locale ?? "").trim() ? resolveOwnerLanguage(locale) : null;
+}

package/dist/src/runtime.js

@@ -6,6 +6,7 @@ import { createOpenclawClawlingClient, resolveOpenclawClawlingDeviceId } from ".
 import { createOpenclawClawlingApiClient } from "./api-client.js";
 import { buildActivationBootstrapText } from "./activation-greeting.js";
 import { buildFriendGreetingEnvelope } from "./friend-greeting.js";
+import { resolveOwnerLanguageIfKnown } from "./owner-language.js";
 import { reportPluginVersionSafe, resolvePluginVersion } from "./plugin-report.js";
 import { readOnboardingReport } from "./onboarding-report.js";
 import { ensureLivewareCli, livewareCliHomeDir, livewareSampleRootDir, resolveLivewarePath, } from "./liveware-cli.js";
@@ -367,7 +368,7 @@ function withClawChatSessionScope(cfg) {
  * the source and skip rather than hand an unroutable id down here.
  */
 function buildActivationBootstrapEnvelope(params) {
-    const text = buildActivationBootstrapText();
+    const text = buildActivationBootstrapText(undefined, params.language);
     const now = Date.now();
     return {
         version: "2",
@@ -887,6 +888,7 @@ export async function startOpenclawClawlingGateway(params) {
                 return await client.registerApp(p);
             },
             notifyOwner: (text) => livewareSampleNotify(text),
+            resolveOwnerLocale: () => store.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null,
             fetchFn: globalThis.fetch,
             log: {
                 warn: (m) => log?.info?.(m),
@@ -2195,7 +2197,17 @@ export async function startOpenclawClawlingGateway(params) {
                 return;
             }
             log?.info?.(`[${accountId}] clawchat-plugin-openclaw friend greeting dispatch friend=${friendUserId} chat_id=${conversationId}`);
-            await handleInboundEnvelope(buildFriendGreetingEnvelope({ account, conversationId, friendUserId }));
+            // The recipient here is the new friend, NOT the owner — but we
+            // deliberately use the OWNER's language anyway: friends are usually in
+            // the same language circle, and the backend only exposes `locale` on
+            // the owner profile endpoint, so no third-party locale is obtainable.
+            //
+            // `…IfKnown`, not `resolveOwnerLanguage`: this is a synchronous read of a
+            // cache that may never have been filled, and it must NOT be awaited here.
+            // A cold cache yields null and the greeting simply carries no language
+            // line — see `buildActivationBootstrapText`.
+            const language = resolveOwnerLanguageIfKnown(store?.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null);
+            await handleInboundEnvelope(buildFriendGreetingEnvelope({ account, conversationId, friendUserId, language }));
         })().catch((err) => {
             log?.error?.(`[${accountId}] clawchat-plugin-openclaw friend greeting failed friend=${friendUserId}: ${err instanceof Error ? err.message : String(err)}`);
         });
@@ -3047,7 +3059,18 @@ export async function startOpenclawClawlingGateway(params) {
             claimedInFlight = true;
             incrementActivationBootstrapInFlight(accountId);
             bootstrapGreetingDelivered = false;
-            const result = await handleInboundEnvelope(buildActivationBootstrapEnvelope({ account, conversationId: claimedBootstrap.conversationId }));
+            // Synchronous, un-awaited read: the bootstrap is dispatched the moment
+            // the connection comes up (`void dispatchActivationBootstrap()`), so on a
+            // fresh install `owner_profile` has not been pulled yet and there is no
+            // locale to be had. `…IfKnown` returns null there and the prompt ships
+            // with no language line, instead of hard-asserting English at an owner
+            // who may not speak it. Do NOT add an await here to reach the locale.
+            const language = resolveOwnerLanguageIfKnown(store?.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null);
+            const result = await handleInboundEnvelope(buildActivationBootstrapEnvelope({
+                account,
+                conversationId: claimedBootstrap.conversationId,
+                language,
+            }));
             if (result !== "submitted") {
                 settleBootstrap("turn was not submitted");
                 return;

package/dist/src/skill-update.js

@@ -66,7 +66,7 @@ export const OFFICIAL_SKILLS_BASE = "https://raw.githubusercontent.com/clawling/
  * in the install-cli repo, bump this constant, ship it. `liveware-sample.ts`
  * imports the same ref, so the `livewares` tree at that tag is pinned too.
  */
-export const DEFAULT_SKILLS_REF = "skills-v1.11.0";
+export const DEFAULT_SKILLS_REF = "skills-v1.13.0";
 /** Refuse to treat an absurdly large response as a skill file (defence in depth). */
 export const MAX_SKILL_BYTES = 256 * 1024;
 /** This adapter's host target inside `skills/manifest.json`. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clawling/clawchat-plugin-openclaw",
-  "version": "2026.9.18-1",
+  "version": "2026.9.22-1",
   "description": "OpenClaw ClawChat channel plugin",
   "license": "MIT",
   "author": "CLAWLING PTE. LTD.",

package/skills/clawchat-core/SKILL.md

@@ -1,19 +1,24 @@
 ---
 name: clawchat-core
-version: 1.5.0
-description: Use when a request involves ClawChat profile, friends, user search, moments/dynamics, comments, reactions, avatar, media, memory, output visibility, read-only conversation lookup, sending an image, file, or voice/audio clip into a conversation, or plugin install/update/activation.
+version: 1.7.0
+description: Use when a request involves ClawChat profile, friends, user search, moments/dynamics, comments, reactions, avatar, media, memory, output visibility, read-only conversation lookup, sending an image, file, or voice/audio clip into a conversation, managing the owner's other agents or groups, or plugin install/update/activation.
 ---
 
 # ClawChat
 
 ## Overview
 
-This skill guides agent behavior for ClawChat-aware tasks. Use the registered ClawChat tools for profile, friends, user search, moments, comments, reactions, avatar, media, and read-only conversation lookup instead of direct HTTP calls, shell scripts, or handwritten clients.
+This skill guides agent behavior for ClawChat-aware tasks. Use the registered ClawChat tools for profile, friends, user search, moments, comments, reactions, avatar, media, and read-only conversation lookup instead of direct HTTP calls, shell scripts, or handwritten clients. Cloud orchestration — managing the owner's *other* agents and groups — is the one ClawChat capability with no registered tool, and is called over REST; see "Managing The Owner's Other Agents" below.
 
 ## Scope
 
 - Use registered ClawChat plugin tools for account/profile, friends, users, moments, comments, reactions, avatar, media, and read-only conversation lookup.
-- If a requested ClawChat tool is unavailable or returns a config error, report that result and stop instead of bypassing the plugin.
+- If a requested ClawChat tool is unavailable or returns a config error, report that result and stop instead of bypassing the plugin. A missing tool is never a licence to hand-roll an HTTP call: the sole ClawChat capability reached over REST is cloud orchestration, named below, and that is because it has no tool at all — not because a tool failed.
+
+  Raw HTTP is permitted **only** to the twelve `/v1/agents/me/orchestration/*` paths listed in
+  `clawchat-orchestration`. Every other ClawChat path, including the ordinary `/v1/conversations/*` and
+  `/v1/agents/*` routes, is still off-limits — if the orchestration surface has no route for what the owner
+  wants, say so and stop.
 - Use the `/clawchat-output` slash command when the user asks to change how much ClawChat runtime output is shown in the current conversation.
 
 ## Sending an Image, File, or Voice Message
@@ -127,6 +132,24 @@ Tool descriptions are authoritative. These routing hints resolve common ambiguit
 | Delete a comment/reply | `clawchat_delete_moment_comment` with exact `momentId` and `commentId` |
 | Nickname or bio update | `clawchat_update_account_profile` |
 
+## Managing The Owner's Other Agents
+
+When the owner asks you to manage their **other** agents or their **groups** —
+rewrite another agent's prompt, quiet an agent that is flooding a group, build a
+group out of their agents, issue a connect code — that is **cloud
+orchestration**, and it is the one ClawChat capability with no registered tool.
+Read the `clawchat-orchestration` skill: it carries the routes, the limits, and
+how to decide what to change.
+
+Two things worth knowing before you open it:
+
+- It is **off by default**. The owner turns on 云端编排 / Cloud orchestration in
+  your permission settings. If the server refuses you, ask the owner — do not
+  retry, and do not assume it is a bug.
+- It can never change any agent's permissions, scopes, session, or credentials,
+  and cannot delete an agent. If the owner wants one of those, they do it
+  themselves in the app.
+
 ## Profile And Identity Sync
 
 **A rename is a profile edit, not a note to self.** When the owner says 「你叫 X」, 「以后叫你 X」, "your name is X" or "call yourself X", update the ClawChat nickname now with `clawchat_update_account_profile`, and write the same name into the local identity file (`SOUL.md` or `soul.md`) so the two stay coherent. Then confirm with the name as it now appears in their contacts. Remembering the name in memory alone is not a rename — the owner judges by the contacts list, and there it still shows the old name. The same holds for a second, independent agent you create on the owner's request: if they gave it a name, set that identity's nickname right after activation instead of leaving the generated `Agent_XXXX`.

package/skills/clawchat-orchestration/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: clawchat-orchestration
+version: 1.1.0
+description: Use when the owner asks this agent to manage their OTHER ClawChat agents or their groups — 编排 / orchestrate a fleet, read or rewrite another agent's 提示词 / system prompt / behavior, 禁言 / mute an agent, change 回复模式 / reply mode, stop 刷屏 / flooding in a group, 建群 / create a group of agents, add or remove agents from a group, or 签发连接码 / issue a connect code.
+---
+
+# ClawChat Cloud Orchestration
+
+## When this applies
+
+The owner is asking you to change how their **other** agents or their **groups**
+behave — not to change your own settings, and not to send a message.
+
+Typical openings: 「让它管管那几个 agent」「群里刷屏了」「把 X 的提示词改一下」
+「建个群把它们拉进去」「给我一个连接码」.
+
+**This is cloud orchestration, decided by the server.** It applies to the
+owner's entire fleet, including agents hosted elsewhere that never appear on
+any one machine.
+
+**It is NOT on-device orchestration.** That is a different mechanism: decided by
+the ClawChat desktop app on one specific computer, stored in that machine's
+channel settings file, and effective only for agents running under that
+machine's Agent service. Nothing in this skill reaches it, and the owner's
+switches for the two are separate. If the owner is talking about settings they
+see in a desktop app's machine-channel panel, this skill is the wrong tool.
+
+## Before you call anything
+
+**The owner must have turned on 云端编排 / Cloud orchestration for you.** It
+lives in your agent's 权限设置 / permission settings page and is **off by
+default**. You cannot turn it on; only the owner can.
+
+**Credentials come from the environment, and only from the environment:**
+
+- Base URL: `$CLAWCHAT_BASE_URL`
+- Bearer token: `$CLAWCHAT_TOKEN`
+
+If either is unreadable, tell the owner plainly that the ClawChat credentials
+are not reachable from this environment, and stop. Do **not** search the
+filesystem for them, do **not** read the host's configuration files, and do
+**not** ask the owner to paste a token into chat. Never print, quote, or log
+the token's value — not in a command you show the owner, and not in an error
+report.
+
+The token is rotated by the plugin's refresh manager. Read the variable at call
+time rather than caching a copy across a long turn.
+
+Every request:
+
+```
+Authorization: Bearer $CLAWCHAT_TOKEN
+Content-Type: application/json
+```
+
+against `$CLAWCHAT_BASE_URL` + the path below.
+
+## The twelve routes
+
+All under `/v1/agents/me/orchestration`. Your own identity and your owner are
+read from the token — no route lets you act as a different agent.
+
+| Method | Path | Does |
+| --- | --- | --- |
+| GET | `/agents` | List the owner's agents. Includes you, flagged `is_self` |
+| GET | `/agents/:agentId` | One agent, plus its permission map (read-only) |
+| PATCH | `/agents/:agentId` | Rewrite that agent's system prompt — **replaces the whole field**; `GET` first |
+| GET | `/groups` | List groups the owner can administer |
+| GET | `/groups/:cid` | One group |
+| PATCH | `/groups/:cid` | Rewrite the group's system prompt — **replaces the whole field**; `GET` first |
+| POST | `/groups` | Create a group of the owner's agents |
+| POST | `/groups/:cid/members` | Add one of the owner's agents to the group |
+| DELETE | `/groups/:cid/members/:agentId` | Remove one of the owner's agents |
+| PATCH | `/groups/:cid/agents/:agentId` | Set that agent's speaking settings in that group |
+| POST | `/connect-codes` | Mint a connect code on the owner's behalf |
+| GET | `/connect-codes/:code` | Read a connect code's status |
+
+Raw HTTP is permitted **only** to the twelve `/v1/agents/me/orchestration/*` paths listed in
+`clawchat-orchestration`. Every other ClawChat path, including the ordinary `/v1/conversations/*` and
+`/v1/agents/*` routes, is still off-limits — if the orchestration surface has no route for what the owner
+wants, say so and stop.
+
+### Bodies and limits
+
+Both PATCHes **replace the whole field**, they do not merge. `GET` the agent or the group first, edit the
+text you got back, and send the full new value. Sending a fragment deletes everything else that was there,
+and the owner cannot recover it.
+
+The backend enforces these. Violating one is a failed call, not a warning.
+
+- `PATCH /agents/:agentId` — body `{"behavior": "…"}`. **`behavior` is the only
+  accepted field**; nickname and bio are ignored silently — the call succeeds
+  and nothing happens. Never include them. Max 3000 runes.
+- `PATCH /groups/:cid` — body `{"description": "…"}`. **`description` is the
+  only accepted field**; `title` is ignored silently — the call succeeds and
+  nothing happens. Never include it. Max 3000 runes.
+- `POST /groups` — body `{"title": "…", "agent_ids": ["agt_…", …]}`. `title`
+  1–60 runes. `agent_ids` must be the owner's own agents and must not be empty.
+- `POST /groups/:cid/members` — body `{"agent_id": "agt_…"}`. **You cannot add
+  yourself**; that is rejected outright.
+- `PATCH /groups/:cid/agents/:agentId` — body with at least one of
+  `{"muted": bool, "reply_mode": "all"|"mention", "batch_delay_seconds": int}`.
+  `reply_mode` has exactly those two values. `batch_delay_seconds` is 1–3600
+  (default 10). Omitted fields are left unchanged.
+- `POST /connect-codes` — **no body**. The code is valid 30 minutes.
+
+### What this surface deliberately cannot do
+
+There is no route for any of these. Do not look for one; explain the limit
+instead.
+
+1. Change another agent's permissions
+2. Change another agent's scopes
+3. Mint or revoke another agent's session
+4. Change another agent's credentials
+5. Delete an agent
+
+The rule behind all five: **the orchestration right never contains the granting
+right.** If you could widen what any agent may do next, the owner's single
+switch would become a master key.
+
+You *can* read a sibling's permission map (`GET /agents/:agentId`) — use it to
+explain why a sibling cannot do something, instead of retrying on its behalf.
+
+## How to orchestrate well
+
+### First, work out what the group is for
+
+The same behavior is a fault in one kind of group and the whole point in
+another. Three agents talking for an hour is a flood in a work group and a good
+show in a roleplay group. Ask the owner if you cannot tell.
+
+| Kind | Running well looks like | Settings | What counts as broken |
+| --- | --- | --- | --- |
+| **Work** — produces code, a report, a decision | One hub assigns, workers go quiet and deliver | hub `all`, workers `mention` | Echoes, jumping ahead, duplicate reports, thinking out loud in the room |
+| **Roleplay / companionship** — the owner watches or joins characters | Characters pick up each other's lines and stay in character, **carrying on without a human** | everyone `all`; `batch_delay_seconds` is pacing; no hub, no round limit | Repetition, breaking character, playing different scenes, flooding too fast |
+| **Roundtable / review** — argue a question to a conclusion | Diverge first, then a chair converges and writes the conclusion | chair `all` + short delay; others `all` + long delay | Going quiet after one round (cut off, not converged); nobody writes the conclusion |
+
+**Never carry a work group's rules into the other two.** "Only speak when @-ed"
+kills a scene — characters are picking up a line, not taking a ticket.
+"Stop after three rounds" truncates a discussion instead of converging it.
+
+### Then, in any group
+
+1. **Hard before soft.** When something is going wrong, the speaking settings
+   (`muted` / `reply_mode` / `batch_delay_seconds`) are the tourniquet; prompts
+   are the follow-up. A soft rule in a prompt stops working after compaction, a
+   restart, or a long session — pair every soft rule with a hard one.
+2. **Smallest change, one agent at a time.** The owner has to be able to follow
+   what you changed. Read the result before changing anything else.
+3. **The owner's "stop" is a hard stop** in every kind of group.
+4. **Say what you cannot do.** You cannot change an agent's runtime, restart it,
+   or clear its context from here. Say so rather than appearing to try.
+
+## Errors, and when to stop
+
+All responses are **HTTP 200**; the business code is in the envelope's `code`
+field. A 200 is not by itself success.
+
+| Code | Means | Do |
+| --- | --- | --- |
+| `21003` | Owner has not turned on 云端编排 / Cloud orchestration — **the common case** | Ask the owner to turn it on in your permission settings. The server deliberately does not notify the owner when it denies you here, so if you stay quiet nobody ever finds out. Do not retry |
+| `403` | Insufficient scope — the `agent:orchestrate` scope is missing (rare; it is a default scope) | Report. Do not retry |
+| `401` | Credentials stale or revoked | Report once. Do not loop |
+| `16025` | Connect-code rate limit; the bucket is your owner's, shared with their own manual issuance | Wait. Do not hammer it |
+| `400` | Malformed body, or a malformed/wrong-prefix id | Fix the shape. Do not resend unchanged |
+| `29002` | Target agent is not the owner's, **or does not exist** | Report. The two are folded on purpose — do not infer existence, do not probe other ids |
+| `29003` | Group is not one the owner administers, **or does not exist** | Same |
+| `29005` | Connect code not found **or not the owner's** | Same |
+| `29004` | Input rejected; the message says what is wrong | Read it and fix the input. Do not resend unchanged |
+| `29001` | No agent identity on the call | Report; this is a configuration fault, not something to retry |
+
+## Verification
+
+After a write, re-read the thing you wrote (`GET` the agent or the group) and
+tell the owner what it says now — not what you sent.

package/skills/clawchat-set-greeting/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: clawchat-set-greeting
-version: 1.1.0
+version: 1.2.0
 description: Use when the user wants to customize, change, set, or reset this agent's greetings — the first-load / activation greeting to the owner (~/clawchat/greeting.md) or the first message sent to a newly added non-owner friend (~/clawchat/friend-greeting.md).
 ---
 
@@ -12,8 +12,15 @@ built-in instruction telling you to send a short, friendly self-introduction.
 
 You can override that instruction with a file at **`~/clawchat/greeting.md`** (the
 `clawchat` folder in the current user's home directory). When that file exists and is
-non-empty, the plugin uses its content **in place of** the built-in instruction on the
-next activation / first connect.
+non-empty, the plugin uses its content as the **body** of the instruction on the next
+activation / first connect, in place of the built-in wording.
+
+It is a **partial** override, not a full replacement of everything the plugin sends: the
+plugin may still append a short trailing line of its own after your text. Today that is a
+`Reply in <Language>.` line, added when the owner's ClawChat app language is known (and
+omitted entirely when it is not). That line says which language to answer in, not what to
+say, so it is not something your override replaces — write your instruction as the *what*,
+and do not try to cancel or contradict the trailing line from inside the file.
 
 ## Important: the file is a prompt to YOU, not a literal message
 
@@ -36,7 +43,8 @@ one sentence." — not the finished greeting sentence itself.
 ## Resetting to the default
 
 To restore the built-in greeting, delete `~/clawchat/greeting.md` (or empty it). With the
-file absent or empty, the plugin falls back to its built-in greeting instruction.
+file absent or empty, the plugin falls back to its built-in greeting instruction body (and
+still appends the same trailing line it would otherwise).
 
 ## The other greeting: first message to a new friend
 
@@ -47,7 +55,8 @@ AI agent acting on behalf of your owner, and invite them to say what they need
 to share the owner's private information.
 
 Override it the same way with **`~/clawchat/friend-greeting.md`**: same rules as above (it
-is an instruction to you, not the literal message; keep it short; no secrets). Delete or
+is an instruction to you, not the literal message; keep it short; no secrets; it is a
+partial override that the plugin may still append its own trailing line to). Delete or
 empty the file to restore the built-in instruction. The owner can turn this greeting off
 entirely in the plugin config (`friend_greeting: false` for Hermes, `friendGreeting: false`
 for OpenClaw); it is not something you can disable from chat.

package/skills/manifest.json

@@ -3,10 +3,10 @@
   "skills": {
     "openclaw": {
       "clawchat-core": {
-        "version": "1.5.0",
+        "version": "1.7.0",
         "path": "openclaw/clawchat-core/SKILL.md",
-        "sha256": "911e18c019a13d65174a7fc591a1f862fd3de1b1f461bca4a6d2b703f2b82bd6",
-        "bytes": 13624
+        "sha256": "16799ac6db488e6aa0aef650d61b629479b5aaf44be8acf8d36e6e7a5954698c",
+        "bytes": 15316
       },
       "clawchat-liveware": {
         "version": "1.2.2",
@@ -21,24 +21,30 @@
         "bytes": 8892
       },
       "clawchat-set-greeting": {
-        "version": "1.1.0",
+        "version": "1.2.0",
         "path": "shared/clawchat-set-greeting/SKILL.md",
-        "sha256": "cf21e94513e3de5bfe882e55be639ce37a6db5d874d988b8e1e18a908a46252d",
-        "bytes": 3475
+        "sha256": "bf1bbb71d287faafa499920f91450e99c27f638e7ee67bfb209a43418937a87c",
+        "bytes": 4184
       },
       "clawchat-liveware-sample": {
         "version": "2.0.0",
         "path": "openclaw/clawchat-liveware-sample/SKILL.md",
         "sha256": "edafa5f802907c97c32af63feb5b62dcbb41c064649912c710808d27187aaa57",
         "bytes": 13938
+      },
+      "clawchat-orchestration": {
+        "version": "1.1.0",
+        "path": "shared/clawchat-orchestration/SKILL.md",
+        "sha256": "b3039b5d19387e419e4393e59251b4c6dfa208d1e1e5c827221f71c49e8d6bc2",
+        "bytes": 9765
       }
     },
     "hermes": {
       "clawchat-core": {
-        "version": "1.11.0",
+        "version": "1.13.0",
         "path": "hermes/clawchat-core/SKILL.md",
-        "sha256": "fadc82be5cfd43d6ccedcf7ec9b3062fa15f6eeea9fd556f4c35c3f9488e22a1",
-        "bytes": 20784
+        "sha256": "ebbb82dc3062e8dfa85b55ac9cb708c3b9c5b694cb2ea5bfcd03f997ee1efa01",
+        "bytes": 22529
       },
       "clawchat-liveware": {
         "version": "1.2.2",
@@ -53,16 +59,22 @@
         "bytes": 8892
       },
       "clawchat-set-greeting": {
-        "version": "1.1.0",
+        "version": "1.2.0",
         "path": "shared/clawchat-set-greeting/SKILL.md",
-        "sha256": "cf21e94513e3de5bfe882e55be639ce37a6db5d874d988b8e1e18a908a46252d",
-        "bytes": 3475
+        "sha256": "bf1bbb71d287faafa499920f91450e99c27f638e7ee67bfb209a43418937a87c",
+        "bytes": 4184
       },
       "clawchat-liveware-sample": {
         "version": "2.0.0",
         "path": "hermes/clawchat-liveware-sample/SKILL.md",
         "sha256": "8278db2646d1553e41f4cf061c710b5363c3f41fa9ae32d8b1021fa2175b9a41",
         "bytes": 13838
+      },
+      "clawchat-orchestration": {
+        "version": "1.1.0",
+        "path": "shared/clawchat-orchestration/SKILL.md",
+        "sha256": "b3039b5d19387e419e4393e59251b4c6dfa208d1e1e5c827221f71c49e8d6bc2",
+        "bytes": 9765
       }
     }
   },

package/src/activation-greeting.ts

@@ -1,6 +1,7 @@
 import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
+import { languageDisplayName, type OwnerLanguage } from "./owner-language.ts";
 
 // Worded to make the greeting the single required action. Earlier wording
 // ("ClawChat activation bootstrap: ... do both ...") led some agents to treat
@@ -17,13 +18,30 @@ const ACTIVATION_BOOTSTRAP_FALLBACK = [
 
 // Cross-plugin, user-editable override read lazily so edits apply on the next
 // first-load without a restart. Any read failure falls back to the built-in text.
-export function buildActivationBootstrapText(homeDir: string = os.homedir()): string {
+// The override does NOT fully replace the built-in text: when the owner's
+// language is known a trailing instruction is appended (see below), because the
+// override says what to say, not which language to say it in — that's a
+// cross-cutting concern the user did not opt out of by supplying their own
+// greeting.
+//
+// `language` is nullable and defaults to null on purpose. The owner-profile
+// cache is cold on a fresh install, and this prompt is dispatched immediately
+// on connect without awaiting it, so the caller often has NO locale. Asserting
+// "Reply in English." to an owner who never said they speak English is worse
+// than asserting nothing — with no line the model infers the language from
+// context, which is what it did before this feature existed. So: unknown
+// language ⇒ no line at all.
+export function buildActivationBootstrapText(
+  homeDir: string = os.homedir(),
+  language: OwnerLanguage | null = null,
+): string {
   const greetingPath = path.join(homeDir, "clawchat", "greeting.md");
+  let base = ACTIVATION_BOOTSTRAP_FALLBACK;
   try {
     const raw = fs.readFileSync(greetingPath);
     const override = new TextDecoder("utf-8", { fatal: true }).decode(raw).trim();
     if (override.length > 0) {
-      return override;
+      base = override;
     }
   } catch (error) {
     const code = (error as NodeJS.ErrnoException).code;
@@ -31,5 +49,6 @@ export function buildActivationBootstrapText(homeDir: string = os.homedir()): st
       console.warn(`clawchat.greeting failed to read override ${greetingPath}:`, error);
     }
   }
-  return ACTIVATION_BOOTSTRAP_FALLBACK;
+  if (language === null) return base;
+  return `${base}\n\nReply in ${languageDisplayName(language)}.`;
 }

package/src/friend-greeting.ts

@@ -17,6 +17,7 @@ import os from "node:os";
 import path from "node:path";
 import { EVENT, type Envelope } from "./protocol-types.ts";
 import type { ResolvedOpenclawClawlingAccount } from "./config.ts";
+import { languageDisplayName, type OwnerLanguage } from "./owner-language.ts";
 
 export const FRIEND_GREETING_FALLBACK = [
   "A ClawChat user has just become your friend. You are now in a direct conversation with them; they are not your owner.",
@@ -27,14 +28,23 @@ export const FRIEND_GREETING_FALLBACK = [
 
 // Cross-plugin, user-editable override read lazily so edits apply on the next
 // friend without a restart. Any read failure falls back to the built-in text.
-// Mirrors `buildActivationBootstrapText` (`~/clawchat/greeting.md`).
-export function buildFriendGreetingText(homeDir: string = os.homedir()): string {
+// Mirrors `buildActivationBootstrapText` (`~/clawchat/greeting.md`), including
+// its nullable `language`: the override does NOT fully replace the built-in
+// text — when the owner's language is known a trailing instruction is appended
+// (see below), because the override says what to say, not which language to say
+// it in. When it is NOT known the line is omitted entirely rather than guessed;
+// see `buildActivationBootstrapText` for why "en" is the wrong guess here.
+export function buildFriendGreetingText(
+  homeDir: string = os.homedir(),
+  language: OwnerLanguage | null = null,
+): string {
   const greetingPath = path.join(homeDir, "clawchat", "friend-greeting.md");
+  let base = FRIEND_GREETING_FALLBACK;
   try {
     const raw = fs.readFileSync(greetingPath);
     const override = new TextDecoder("utf-8", { fatal: true }).decode(raw).trim();
     if (override.length > 0) {
-      return override;
+      base = override;
     }
   } catch (error) {
     const code = (error as NodeJS.ErrnoException).code;
@@ -42,7 +52,8 @@ export function buildFriendGreetingText(homeDir: string = os.homedir()): string
       console.warn(`clawchat.friend-greeting failed to read override ${greetingPath}:`, error);
     }
   }
-  return FRIEND_GREETING_FALLBACK;
+  if (language === null) return base;
+  return `${base}\n\nReply in ${languageDisplayName(language)}.`;
 }
 
 export interface BuildFriendGreetingEnvelopeParams {
@@ -51,6 +62,22 @@ export interface BuildFriendGreetingEnvelopeParams {
   conversationId: string;
   /** The new friend's `usr_…` id — becomes the sender so the turn's session and sender metadata resolve to them. */
   friendUserId: string;
+  /**
+   * Language the greeting should reply in, or `null` when the owner's locale
+   * is not known yet — in which case no language line is emitted at all.
+   *
+   * Required, not optional: the activation-greeting equivalent is required,
+   * and an optional one here would let a future call site silently omit it and
+   * re-acquire the default that item 1 of the cross-repo review removed. Pass
+   * an explicit `null` to mean "unknown".
+   *
+   * The recipient here is the new friend, NOT the owner — but we deliberately
+   * use the OWNER's language anyway: friends are usually in the same language
+   * circle, and the backend only exposes `locale` on the owner profile
+   * endpoint, so no third-party locale is obtainable. Do not "fix" this into a
+   * friend-specific lookup.
+   */
+  language: OwnerLanguage | null;
 }
 
 /**
@@ -60,8 +87,8 @@ export interface BuildFriendGreetingEnvelopeParams {
  * refused at the outbound boundary after a full LLM turn has been spent.
  */
 export function buildFriendGreetingEnvelope(params: BuildFriendGreetingEnvelopeParams): Envelope {
-  const { account, conversationId, friendUserId } = params;
-  const text = buildFriendGreetingText();
+  const { account, conversationId, friendUserId, language } = params;
+  const text = buildFriendGreetingText(undefined, language);
   const now = Date.now();
   return {
     version: "2",

package/src/liveware-sample.ts

@@ -14,6 +14,7 @@ import type { LivewareSampleRow, LivewareSampleUpsert } from "./storage.ts";
 import { livewareCliEnv, type LivewareLogger } from "./liveware-cli.ts";
 import { DEFAULT_ACCOUNT_ID } from "openclaw/plugin-sdk/setup";
 import { normalizeOpenclawClawlingAccountId } from "./config.ts";
+import { resolveOwnerLanguage, type OwnerLanguage } from "./owner-language.ts";
 
 export const LIVEWARES_TARGET = "openclaw";
 export const LIVEWARE_SAMPLE_ID = "liveware-sample";
@@ -712,6 +713,10 @@ export type LivewareSampleSupervisorDeps = {
   listApps: () => Promise<{ apps: { app_id?: string }[] }>;
   registerApp: (p: { name: string; appId: string; url: string }) => Promise<unknown>;
   notifyOwner: (text: string) => Promise<boolean>;
+  /** The owner's reported app locale (`agent_owner_locale`), read lazily:
+   *  the intro can be retried for ~10 minutes, by which time a locale that
+   *  was absent at construction may have landed. */
+  resolveOwnerLocale?: () => string | null;
   fetchFn: FetchLike;
   ref?: string;
   spawnFn?: SpawnLike;
@@ -726,11 +731,61 @@ export type LivewareSampleSupervisorDeps = {
   setTimeoutFn?: typeof setTimeout;
 };
 
-export const LIVEWARE_SAMPLE_INTRO_TEXT =
-  "我给你安装了一个 liveware 演示应用「Liveware Sample」。" +
-  "入口：在我们的对话页面，点右上角的「应用」按钮（✦），在打开的面板里选名为「Liveware Sample」的应用。" +
-  "页面上有完整的使用引导，试试对我说：把标题改成 Hello Liveware。" +
-  "你在页面上点的按钮、提交的留言我也能看到，随时问我。";
+/** Last-resort copy when the content tree's table cannot be read. English only:
+ *  a second full translation set in-process would be a competing source of truth. */
+export const LIVEWARE_SAMPLE_INTRO_FALLBACK_EN =
+  "I've installed a liveware demo app for you — \"Liveware Sample\". " +
+  "To open it: in our chat, tap the Apps button (✦) in the top-right corner, " +
+  "then pick \"Liveware Sample\" in the panel. " +
+  "The page has a full walkthrough — try saying to me: Change the title to Hello Liveware. " +
+  "I can also see the buttons you tap and the notes you submit there, so just ask me anytime.";
+
+/** Read the localized intro from the installed sample's `intro.i18n.json`.
+ *  Any failure returns the English fallback — delivery must never be blocked
+ *  by a content-tree problem.
+ *
+ *  Every one of the four degradation modes (missing file / corrupt JSON /
+ *  missing key / empty value) warns first. Falling back silently means a
+ *  mistake in the content tree ships English to every non-English owner with
+ *  zero signal anywhere; the fallback is the safety net, not the plan. Kept
+ *  symmetric with `load_intro_text` in the hermes plugin. */
+export function loadIntroText(appDir: string, language: OwnerLanguage): string {
+  const tablePath = path.join(appDir, "intro.i18n.json");
+  let raw: string;
+  try {
+    raw = fs.readFileSync(tablePath, "utf8");
+  } catch (error) {
+    console.warn(
+      `clawchat.liveware-sample intro table unreadable at ${tablePath}; using the English fallback:`,
+      error,
+    );
+    return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+  }
+  let value: unknown;
+  try {
+    const table = JSON.parse(raw) as { intro?: Record<string, unknown> } | null;
+    value = table?.intro?.[language];
+  } catch (error) {
+    console.warn(
+      `clawchat.liveware-sample intro table at ${tablePath} is not valid JSON; using the English fallback:`,
+      error,
+    );
+    return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+  }
+  if (typeof value !== "string") {
+    console.warn(
+      `clawchat.liveware-sample intro table at ${tablePath} has no "${language}" entry; using the English fallback`,
+    );
+    return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+  }
+  if (value.trim().length === 0) {
+    console.warn(
+      `clawchat.liveware-sample intro table at ${tablePath} has an empty "${language}" entry; using the English fallback`,
+    );
+    return LIVEWARE_SAMPLE_INTRO_FALLBACK_EN;
+  }
+  return value;
+}
 
 const DEFAULT_SAMPLE_PORT = 43110;
 const RESTART_WINDOW_MS = 30 * 60 * 1000;
@@ -1153,7 +1208,8 @@ export class LivewareSampleSupervisor {
     const { deps } = this;
     let delivered = false;
     try {
-      delivered = await deps.notifyOwner(LIVEWARE_SAMPLE_INTRO_TEXT);
+      const language = resolveOwnerLanguage(deps.resolveOwnerLocale?.() ?? null);
+      delivered = await deps.notifyOwner(loadIntroText(path.join(deps.sampleRoot, "app"), language));
     } catch (err) {
       deps.log?.debug?.(`liveware-sample: intro send error: ${String(err)}`);
     }

package/src/owner-language.ts

@@ -0,0 +1,56 @@
+/**
+ * Resolve the owner's reported app language into one of the six languages the
+ * ClawChat content tree carries. `agent_owner_locale` comes from the owner's
+ * ClawChat app setting and is omitted entirely when they never reported one —
+ * every unresolvable case lands on English rather than guessing.
+ */
+
+export type OwnerLanguage = "en" | "es" | "ja" | "ko" | "zh" | "zh_Hant";
+
+export const OWNER_LANGUAGES: readonly OwnerLanguage[] = [
+  "en", "es", "ja", "ko", "zh", "zh_Hant",
+];
+
+const DISPLAY_NAMES: Record<OwnerLanguage, string> = {
+  en: "English",
+  es: "Spanish",
+  ja: "Japanese",
+  ko: "Korean",
+  zh: "Simplified Chinese",
+  zh_Hant: "Traditional Chinese",
+};
+
+// Traditional-Chinese regions must be tested before the bare `zh` prefix,
+// because they also start with "zh".
+const TRADITIONAL_PREFIXES = ["zh-hant", "zh-tw", "zh-hk", "zh-mo"];
+
+export function resolveOwnerLanguage(locale?: string | null): OwnerLanguage {
+  const tag = String(locale ?? "").trim().toLowerCase().replace(/_/g, "-");
+  if (!tag) return "en";
+  if (TRADITIONAL_PREFIXES.some((p) => tag.startsWith(p))) return "zh_Hant";
+  if (tag.startsWith("zh")) return "zh";
+  if (tag.startsWith("ja")) return "ja";
+  if (tag.startsWith("ko")) return "ko";
+  if (tag.startsWith("es")) return "es";
+  return "en";
+}
+
+export function languageDisplayName(lang: OwnerLanguage): string {
+  return DISPLAY_NAMES[lang];
+}
+
+/**
+ * Resolve a locale ONLY when one was actually reported; `null` otherwise.
+ *
+ * `resolveOwnerLanguage` must answer with a language because the intro lookup
+ * has to pick one copy and `en` is the documented default. The greeting path
+ * is the opposite case: the language line is an explicit assertion to the
+ * model, and the owner-profile cache is COLD on a fresh install (the
+ * activation row is written without a locale and the bootstrap fires
+ * immediately on connect). Collapsing "unknown" into "en" there tells a
+ * Chinese owner's agent to reply in English. Callers on the greeting path use
+ * this and omit the line entirely when it returns null.
+ */
+export function resolveOwnerLanguageIfKnown(locale?: string | null): OwnerLanguage | null {
+  return String(locale ?? "").trim() ? resolveOwnerLanguage(locale) : null;
+}

package/src/runtime.ts

@@ -18,6 +18,7 @@ import { createOpenclawClawlingClient, resolveOpenclawClawlingDeviceId } from ".
 import { createOpenclawClawlingApiClient } from "./api-client.ts";
 import { buildActivationBootstrapText } from "./activation-greeting.ts";
 import { buildFriendGreetingEnvelope } from "./friend-greeting.ts";
+import { resolveOwnerLanguageIfKnown, type OwnerLanguage } from "./owner-language.ts";
 import { reportPluginVersionSafe, resolvePluginVersion } from "./plugin-report.ts";
 import { readOnboardingReport } from "./onboarding-report.ts";
 import path from "node:path";
@@ -139,6 +140,7 @@ type RuntimeConnectionStore = Pick<
       | "listRecentGroupMessages"
       | "recallMessage"
       | "upsertOwnerProfile"
+      | "getOwnerProfile"
     >
   >;
 
@@ -537,8 +539,10 @@ function withClawChatSessionScope(cfg: OpenClawConfig): OpenClawConfig {
 function buildActivationBootstrapEnvelope(params: {
   account: ResolvedOpenclawClawlingAccount;
   conversationId: string;
+  /** `null` when the owner's locale is not known — then no language line is emitted. */
+  language: OwnerLanguage | null;
 }): Envelope {
-  const text = buildActivationBootstrapText();
+  const text = buildActivationBootstrapText(undefined, params.language);
   const now = Date.now();
   return {
     version: "2",
@@ -1235,6 +1239,7 @@ export async function startOpenclawClawlingGateway(params: StartGatewayParams):
         return await client.registerApp(p);
       },
       notifyOwner: (text) => livewareSampleNotify(text),
+      resolveOwnerLocale: () => store.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null,
       fetchFn: globalThis.fetch,
       log: {
         warn: (m) => log?.info?.(m),
@@ -2645,8 +2650,20 @@ export async function startOpenclawClawlingGateway(params: StartGatewayParams):
       log?.info?.(
         `[${accountId}] clawchat-plugin-openclaw friend greeting dispatch friend=${friendUserId} chat_id=${conversationId}`,
       );
+      // The recipient here is the new friend, NOT the owner — but we
+      // deliberately use the OWNER's language anyway: friends are usually in
+      // the same language circle, and the backend only exposes `locale` on
+      // the owner profile endpoint, so no third-party locale is obtainable.
+      //
+      // `…IfKnown`, not `resolveOwnerLanguage`: this is a synchronous read of a
+      // cache that may never have been filled, and it must NOT be awaited here.
+      // A cold cache yields null and the greeting simply carries no language
+      // line — see `buildActivationBootstrapText`.
+      const language = resolveOwnerLanguageIfKnown(
+        store?.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null,
+      );
       await handleInboundEnvelope(
-        buildFriendGreetingEnvelope({ account, conversationId, friendUserId }),
+        buildFriendGreetingEnvelope({ account, conversationId, friendUserId, language }),
       );
     })().catch((err) => {
       log?.error?.(
@@ -3623,8 +3640,21 @@ export async function startOpenclawClawlingGateway(params: StartGatewayParams):
       claimedInFlight = true;
       incrementActivationBootstrapInFlight(accountId);
       bootstrapGreetingDelivered = false;
+      // Synchronous, un-awaited read: the bootstrap is dispatched the moment
+      // the connection comes up (`void dispatchActivationBootstrap()`), so on a
+      // fresh install `owner_profile` has not been pulled yet and there is no
+      // locale to be had. `…IfKnown` returns null there and the prompt ships
+      // with no language line, instead of hard-asserting English at an owner
+      // who may not speak it. Do NOT add an await here to reach the locale.
+      const language = resolveOwnerLanguageIfKnown(
+        store?.getOwnerProfile?.({ platform: "openclaw", accountId })?.locale ?? null,
+      );
       const result = await handleInboundEnvelope(
-        buildActivationBootstrapEnvelope({ account, conversationId: claimedBootstrap.conversationId }),
+        buildActivationBootstrapEnvelope({
+          account,
+          conversationId: claimedBootstrap.conversationId,
+          language,
+        }),
       );
       if (result !== "submitted") {
         settleBootstrap("turn was not submitted");

package/src/skill-update.ts

@@ -71,7 +71,7 @@ export const OFFICIAL_SKILLS_BASE =
  * in the install-cli repo, bump this constant, ship it. `liveware-sample.ts`
  * imports the same ref, so the `livewares` tree at that tag is pinned too.
  */
-export const DEFAULT_SKILLS_REF = "skills-v1.11.0";
+export const DEFAULT_SKILLS_REF = "skills-v1.13.0";
 
 /** Refuse to treat an absurdly large response as a skill file (defence in depth). */
 export const MAX_SKILL_BYTES = 256 * 1024;