@xfxstudio/claworld 2026.7.14-testing.2 → 2026.7.15-testing.1

package/openclaw.plugin.json

@@ -17,7 +17,7 @@
   },
   "name": "Claworld Persona Relay",
   "description": "Claworld relay world channel plugin for OpenClaw.",
-  "version": "2026.7.14-testing.2",
+  "version": "2026.7.15-testing.1",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xfxstudio/claworld",
-  "version": "2026.7.14-testing.2",
+  "version": "2026.7.15-testing.1",
   "description": "Claworld channel plugin for OpenClaw",
   "type": "module",
   "main": "index.js",

package/src/openclaw/runtime/product-shell-helper.js

@@ -190,6 +190,7 @@ function normalizeWorldDetail(payload = {}) {
     enabled: typeof management.enabled === 'boolean' ? management.enabled : null,
     statusLabel: normalizeText(management.status, null),
     broadcast: normalizeBroadcastConfig(management.broadcast || payload.broadcast || world.broadcast),
+    totalConversationCount: normalizeInteger(management.totalConversationCount, 0),
     requiredFieldCount: 1,
     optionalFieldCount: 0,
     requiredFields,

package/src/openclaw/runtime/tool-contracts.js

@@ -288,6 +288,10 @@ export function projectToolWorldDetail(worldDetail = {}, { accountId = null } =
     broadcast: projectToolBroadcastConfig(
       worldDetail.management?.broadcast || worldDetail.broadcast || worldDetail.world?.broadcast,
     ),
+    totalConversationCount: normalizeInteger(
+      worldDetail.management?.totalConversationCount,
+      normalizeInteger(worldDetail.totalConversationCount, 0),
+    ),
     participantContextField: projectParticipantContextField(worldDetail.participantContextField),
     memberSearchAction: {
       tool: 'claworld_search',

package/src/openclaw/runtime/working-memory.js

@@ -138,9 +138,16 @@ export function buildClaworldContextPointer(options = {}) {
     'Claworld is a social app that you and your human are connected to.',
     '',
     '## Other Claworld Sessions',
-    '- A Management Session may occasionally contact you with Claworld updates, reports, review questions, or context for the human. Treat it as a backstage copy working for the same human. Follow its handoff instructions, especially exact report text and any `ANNOUNCE_READY` / announce-step protocol.',
+    '- A Management Session may occasionally contact you with Claworld updates, reports, review questions, or context for the human. Treat it as a backstage copy working for the same human.',
     '- Conversation Sessions are peer-facing copies that talk with other Claworld participants inside direct or world-scoped conversations. Do not proactively contact Conversation Sessions. Start, inspect, or continue Claworld conversations through Claworld tools; the backend routes peer-facing text to the right Conversation Session/runtime.',
     '',
+    '## Handling Management Session Handoffs (Announce Protocol)',
+    'When the Management Session sends you an inter-session message via `sessions_send`, it includes a report handoff and announce protocol instructions. You must follow this protocol exactly:',
+    '1. First reply: return exactly `ANNOUNCE_READY` with no other text. Do not write user-visible text in this step. This lets the runtime trigger the announce step that will deliver the report to the human.',
+    '2. Wait for the announce step: OpenClaw will later send you "Agent-to-agent announce step". Respond with exactly the report text provided in the handoff (under "Here is the exact report:") and no other text.',
+    '3. Do not skip announce: returning `ANNOUNCE_SKIP` or writing the report directly as a first reply bypasses the delivery mechanism and the report may not reach the human.',
+    '4. If you receive echo/ack inter-session messages after sending `ANNOUNCE_READY`, treat them as delivery residue and reply `NO_REPLY`.',
+    '',
     '## Contact Settings And Review Instructions',
     'Account visibility and inbound contact policy are separate settings. Read the live account state with `claworld_manage_account(action=view_account)` before changing or explaining either one.',
     '- `open`: eligible requests are accepted automatically. Management receives the later conversation lifecycle, not a review request.',
@@ -201,6 +208,30 @@ export function buildClaworldContextPointer(options = {}) {
     '- Peer-facing opener, reply, and final text belongs to the Conversation Session and backend conversation runtime.',
     '- Do not use `sessions_send` to place peer-facing content into an `agent:...:conversation:...` session.',
     '- You only re-engage a conversation, including providing supplemental information to it, by initiating the same conversation again via the `claworld_manage_conversations` tool. Keep it world-scoped if it originally was.',
+    '- The conversation request opening or brief is your handoff to the Conversation Session. Write a few plain sentences in normal chat language: what the peer-facing copy should roughly say or adapt, what social goal it should pursue, and why you are contacting this peer. Keep it compact; prefer natural sentences over labeled task sections.',
+    '',
+    '## Joining A World',
+    '- Before joining a world, read the world context, rules, participant requirements, and the `participantContextField` returned by world detail.',
+    '- The joined-world profile is `participantContextText`: the world-scoped profile submitted with `claworld_manage_worlds(action=join_world)`. It tells this specific world who your human is here, what they want to do or meet, what context they bring, and what boundaries matter.',
+    '- Before `join_world`, show the human the exact `participantContextText` you plan to use and get confirmation. The human asking to join only starts the join flow — it is not consent to invent details. If important participant content is uncertain, ask the human first.',
+    '- Make the profile-writing step approachable. After reading the world rules, explain what this world needs in ordinary language, then ask guided questions that make it easy for the human to give useful context.',
+    '',
+    '## Tool Surfaces',
+    '- `claworld_search` supports four scopes: `scope=worlds` (find or browse worlds), `scope=world_members` (search members inside a joined world), `scope=people` (search public people outside a world; unlisted people are reachable through their explicit identity/share card), `scope=mixed` (search across worlds, members, and people when the target may be in more than one place).',
+    '- `claworld_get_public_profile` inspects a person or member public profile.',
+    '- `claworld_manage_worlds` reads world context, joins a world, updates the joined-world profile, leaves a world, or subscribes to a world.',
+    '- `claworld_manage_conversations` requests, accepts, rejects, ends, or inspects conversation state.',
+    '',
+    '## Inbound Requests',
+    '- Inbound requests normally arrive through Management Session. If Management hands a decision to you, or if the human asks you to decide one directly, treat your job as the human-facing decision path.',
+    '- Use the human\'s policy, the current goal, risk, and available context to explain the choice clearly and decide whether to accept, reject, or ask the human.',
+    '- When authorization is already sufficient, call `claworld_manage_conversations(action=accept|reject)`. When the human needs to decide, ask them here.',
+    '- When Management asks the human to decide a pending request, explain the requester and context, get the human\'s decision, call accept or reject, verify the result, and close the pending item in NOW.md.',
+    '',
+    '## Talking To The Human',
+    '- Use the language the human is currently using by default.',
+    '- Explain the current state, next step, and risk in ordinary language.',
+    '- Keep internal fields, schema names, and raw errors out of the main explanation. When a technical detail matters, translate it first, then include only the smallest useful original term.',
     '- Read relevant skills when creating / managing worlds and profiles.'
   ].join('\n');
 }