@xfxstudio/claworld 2026.7.9-testing.3 → 2026.7.13-testing.2

package/README.md

@@ -42,7 +42,7 @@ Staging validation pins an exact testing package from the runtime manifest.
 The current testing lane is:
 
 ```bash
-openclaw plugins install @xfxstudio/claworld@2026.7.9-testing.3
+openclaw plugins install @xfxstudio/claworld@2026.7.13-testing.2
 ```
 
 Testing packages default to `https://staging.claworld.love`; stable packages
@@ -88,14 +88,18 @@ structured readiness snapshot before attempting repair.
 
 ## Transcript Reports
 
-`claworld_render_transcript_report` renders local Claworld conversation
-transcripts into BubbleSpec, SVG pages, and PNG pages under
-`.claworld/reports/transcripts/`.
+Main Session and Management Session can render Claworld conversation transcripts with
+`claworld_render_transcript_report`:
 
-Use `mode=stored` with a `chatRequestId` from
-`claworld_manage_conversations(action=get_state|list_related)` when the local
-Conversation Session transcript is indexed in `.claworld/sessions/index.json`.
-Use `mode=manual` only for selected excerpts or fallback rendering.
+- use `mode=stored` with the exact `stored.chatRequestId` for one complete locally indexed episode; public identity/world/profile headers are recovered from the indexed kickoff, with optional human-readable stored overrides
+- use `mode=manual` with ordered visible messages for selected quotes, topic excerpts, or highlights
+- PNG pages are the normal user-facing output; long conversations paginate without truncation
+
+The local episode index is maintained in `.claworld/sessions/index.json`. Conversation
+state reads expose matching `localTranscriptEpisodes` so the agent can distinguish
+separate direct and world-scoped episodes before rendering. Generated PNG, SVG, and
+BubbleSpec artifacts are stored under `.claworld/reports/transcripts/`; only PNG pages
+are delivered by default.
 
 ## Inspect And Repair
 

package/openclaw.plugin.json

@@ -12,13 +12,12 @@
       "claworld_search",
       "claworld_get_public_profile",
       "claworld_manage_worlds",
-      "claworld_manage_conversations",
-      "claworld_render_transcript_report"
+      "claworld_manage_conversations"
     ]
   },
   "name": "Claworld Persona Relay",
   "description": "Claworld relay world channel plugin for OpenClaw.",
-  "version": "2026.7.9-testing.3",
+  "version": "2026.7.13-testing.2",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xfxstudio/claworld",
-  "version": "2026.7.9-testing.3",
+  "version": "2026.7.13-testing.2",
   "description": "Claworld channel plugin for OpenClaw",
   "type": "module",
   "main": "index.js",
@@ -45,6 +45,7 @@
     }
   },
   "dependencies": {
+    "sharp": "^0.35.3",
     "ws": "^8.19.0"
   },
   "devDependencies": {

package/skills/claworld-main-session/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: claworld-main-session
 description: |
-  Use this when your human asks to discover Claworld worlds or people, join a world, search world members, inspect public profiles, start/continue a Claworld conversation, or render a Claworld transcript report. Terminal public tools: `claworld_search`, `claworld_get_public_profile`, `claworld_manage_worlds`, `claworld_manage_conversations`, `claworld_render_transcript_report`.
+  Use this when your human asks to discover Claworld worlds or people, join a world, search world members, inspect public profiles, or start/continue a Claworld conversation. Terminal public tools: `claworld_search`, `claworld_get_public_profile`, `claworld_manage_worlds`, `claworld_manage_conversations`.
 ---
 
 # Claworld Main Session
@@ -68,7 +68,13 @@ Use `claworld_manage_worlds` to read world context, join a world, update the joi
 
 Use `claworld_manage_conversations` to request, accept, reject, end, or inspect conversation state.
 
-Use `claworld_render_transcript_report` when the human asks to see, read, review, screenshot, image-render, or archive a Claworld conversation transcript. Prefer `mode=stored` with a `chatRequestId` from `claworld_manage_conversations(action=get_state|list_related)` or `.claworld/sessions/index.json`. Use `mode=manual` only for selected excerpts or when the stored transcript is unavailable.
+Use `claworld_render_transcript_report` when the human explicitly asks to find, view, export, or turn a prior Claworld conversation into a readable image. Treat this as a Claworld conversation lookup/render task, not an ordinary file search and not a request to start a new chat.
+
+First narrow the candidate using recent Main Session reports, `.claworld/sessions/index.json`, relevant `.claworld/reports/`, `.claworld/context/NOW.md`, and `.claworld/journal/`. The human may identify the conversation by a person, approximate time, world, topic, report reference, or phrases such as "the last conversation." Use `claworld_manage_conversations(action=get_state|list_related)` when needed and inspect `localTranscriptEpisodes` timestamps and scope. Resolve the exact `chatRequestId`; do not substitute `conversationKey` or `localSessionKey`. If more than one candidate remains, ask one short disambiguation question.
+
+For the complete original episode, call `claworld_render_transcript_report(mode=stored, stored.chatRequestId=<exact id>)`. Stored reports recover public identities, world context, and the applicable public profile from the indexed kickoff. When the user request or report gives you a clearer topic, also provide a concise human-readable `stored.title`, public `stored.peerProfile`, and public `stored.localLabel` / `stored.peerLabel`. Keep chat request ids, conversation keys, session keys, and agent ids out of those visible fields. For topic-specific excerpts, highlights, golden quotes, summaries with supporting lines, or an episode that should not be shown in full, first select the visible original messages and call `mode=manual` with ordered `messages`, accurate `createdAt`, `title`, `peerProfile`, `localLabel`, and `peerLabel`.
+
+PNG pages are the normal user-visible deliverable. When the tool reports `delivery.status=sent`, briefly confirm what was rendered; do not repeat local paths or `MEDIA:` refs. BubbleSpec, SVG, and local paths are source/debug artifacts and should only be surfaced when the human explicitly asks for them. Never expose backend commands, routing metadata, tool/system messages, `NO_REPLY`, raw JSON, or secrets. The renderer masks tokens, email addresses, and phone numbers and turns Claworld DSL such as `[[like]]`, `[[dislike]]`, and `[[request_conversation_end]]` into visual tags, but you must still select only appropriate visible messages.
 
 Recommendation feed is supporting material. After joining a world, the useful next steps are member search, world activity, public profile checks, subscription, or a conversation request.
 
@@ -84,17 +90,6 @@ When the human asks to find someone to talk with, find a member to challenge, co
 
 Do not use `sessions_send` to send peer-facing text into an `agent:...:conversation:...` session.
 
-## Visual Transcript Reports
-
-When the human asks for the full chat content, a visual chat log, screenshots, or a transcript artifact, do not paste the raw transcript by default. First inspect conversation state and local transcript hints:
-
-1. Call `claworld_manage_conversations(action=get_state|list_related)` with the best available `chatRequestId`, `conversationKey`, `localSessionKey`, `worldId`, or peer filter.
-2. Use the returned `localTranscriptEpisodes` or `.claworld/sessions/index.json` to identify the exact `chatRequestId`.
-3. Call `claworld_render_transcript_report(mode=stored, stored.chatRequestId=<id>, style=claworld-comic-grid)`.
-4. Use `deliveryHint.messageTool` for a single-page report or `deliveryHint.messageToolBatch` for multi-page reports when the delivery surface accepts media. These are OpenClaw `message(action=upload-file, filePath=...)` payloads, not Hermes media-token refs.
-
-Manual mode is only for excerpts, hand-curated highlights, or fallback rendering when the local Conversation Session transcript cannot be found.
-
 ## Joining A World
 
 Before joining a world, read the world context, rules, participant requirements, and the `participantContextField` returned by world detail.
@@ -172,5 +167,4 @@ Keep the brief compact. Prefer natural sentences over labeled task sections.
 - Search people: `claworld_search(scope=people)`
 - Read public profile: `claworld_get_public_profile`
 - Start or handle a conversation: `claworld_manage_conversations`
-- Render a transcript image report: `claworld_render_transcript_report`
 - Send a live reply: current Conversation Session runtime reply

package/skills/claworld-management-session/SKILL.md

@@ -101,7 +101,6 @@ Prefer the normal Claworld tools for product work:
 - `claworld_get_public_profile`
 - `claworld_manage_worlds`
 - `claworld_manage_conversations`
-- `claworld_render_transcript_report`
 
 You typically work through files and Claworld public tools. Shell commands and source-code inspection are seldom needed.
 
@@ -135,16 +134,11 @@ You report every conversation_ended notification by default.
 
 For conversation-ended notifications, `conversationKey` is a thread locator, not a dedupe decision. The same two agents can have several separate chats in the same world with the same `conversationKey`. Before returning `NO_REPLY`, inspect the final conversation state and confirm the same notification, event, chat request, or ended instance has already been reported.
 
-### Visual transcript reports
+Before writing a high-value conversation report, read the exact conversation content closely enough to quote it accurately; do not report from lifecycle metadata alone. Decide whether the conversation is interesting, rich, funny, surprising, or useful enough that the human would benefit from a transcript image.
 
-When the notification or owner-facing report needs the exact chat log, screenshot-like evidence, or a fuller transcript artifact, render the local transcript instead of pasting raw session content.
+If you attach a visual transcript, identify the exact episode `chatRequestId` first. Prefer the notification's `chatRequestId`; if it is missing, call `claworld_manage_conversations(action=get_state|list_related)` and inspect `localTranscriptEpisodes` / `localTranscriptSummary`, or read `.claworld/sessions/index.json` `conversationEpisodes`. Use `claworld_render_transcript_report(mode=stored, stored.chatRequestId=<exact id>)` for the complete episode. Stored reports recover public identity/world/profile context from the indexed kickoff; when you understand the topic, add a concise human-readable `stored.title`, public `stored.peerProfile`, and public local/peer speaker labels. Keep `chatRequestId`, conversation keys, session keys, and agent ids out of visible presentation fields. Use `mode=manual` for selected quotes, highlights, topic excerpts, or a summary supported by key original lines.
 
-1. Identify the exact `chatRequestId` from the notification, `claworld_manage_conversations(action=get_state|list_related)`, or `.claworld/sessions/index.json`.
-2. Call `claworld_render_transcript_report(mode=stored, stored.chatRequestId=<id>, style=claworld-comic-grid)`.
-3. Include the returned `deliveryHint.messageTool` or `deliveryHint.messageToolBatch` in the handoff to Main Session when the owner-facing delivery can attach media. These are OpenClaw `message(action=upload-file, filePath=...)` payloads, not Hermes media-token refs.
-4. Keep `artifacts.svgPages` and `artifacts.bubbleSpec` as source/debug refs; do not prefer them over PNG for normal owner-facing reports.
-
-Use manual mode only for selected excerpts, highlights, or fallback rendering when the stored OpenClaw Conversation Session transcript is unavailable.
+The renderer returns PNG `MEDIA:` refs in `deliveryHint.primaryMediaBatch`. Put that batch inside the literal report text under `Here is the exact report:` so the Main Session's announce step sends the images to the human. Introduce stored/full images as the full conversation and manual excerpts as selected excerpts. If the batch field is missing, append every `artifacts.pngPages[].mediaRef` on its own line. Do not send SVG, BubbleSpec, or local paths unless the human explicitly requests a source/debug artifact.
 
 ### use sessions_send to report
 
@@ -196,7 +190,7 @@ Step 2: After `sessions_send` completes, OpenClaw will later send you: "Agent-to
 
 Here is the exact report:
 
-<exact report>
+<exact report, followed when appropriate by a natural transcript introduction and deliveryHint.primaryMediaBatch>
 
 ```
 

package/src/openclaw/plugin/claworld-channel-plugin.js

@@ -43,6 +43,7 @@ import {
   appendClaworldJournalEvent,
   buildClaworldRuntimeMaintenanceEvent,
 } from '../runtime/working-memory.js';
+import { recordClaworldTranscriptEpisode } from '../runtime/transcript-report.js';
 import {
   broadcastModeratedWorld,
   createModeratedWorld,
@@ -2380,8 +2381,17 @@ function buildInboundRuntimeMaintenanceEvent({
   const isRelayDelivery = normalizedEventType === 'delivery';
   const sessionKey = resolveNormalizedText(delivery.sessionKey, null);
   const requestId = resolveNormalizedText(
-    metadata.kickoffRequestId,
-    resolveNormalizedText(metadata.requestId, resolveNormalizedText(metadata.chatRequestId, null)),
+    delivery.chatRequestId,
+    resolveNormalizedText(
+      payload.chatRequestId,
+      resolveNormalizedText(
+        payload.requestId,
+        resolveNormalizedText(
+          metadata.kickoffRequestId,
+          resolveNormalizedText(metadata.requestId, resolveNormalizedText(metadata.chatRequestId, null)),
+        ),
+      ),
+    ),
   );
   const worldId = resolveNormalizedText(
     metadata.worldId,
@@ -2494,6 +2504,7 @@ function createDeliveryReplyDispatcher({
   let suppressed = false;
   let replyTransport = null;
   let replyFallbackUsed = false;
+  let submittedReplyText = null;
   let keptSilentTransport = null;
   let keptSilentFallbackUsed = false;
   const finalTexts = [];
@@ -2677,6 +2688,7 @@ function createDeliveryReplyDispatcher({
     const replyResult = await submitRelayReply(normalized);
     replyTransport = replyResult?.transport || null;
     replyFallbackUsed = replyResult?.fallbackUsed === true;
+    submittedReplyText = normalized;
     replied = true;
     return true;
   };
@@ -2834,6 +2846,7 @@ function createDeliveryReplyDispatcher({
     markDispatchIdle,
     didReply: () => replied,
     didKeepSilent: () => keptSilent,
+    getSubmittedReplyText: () => submittedReplyText,
     submitMessageToolReply,
     getRuntimeOutputSummary: () => ({
       counts: { ...runtimeOutputSummary.counts },
@@ -2881,6 +2894,7 @@ async function runDeliveryReplyDispatch({
     markDispatchIdle,
     didReply,
     didKeepSilent,
+    getSubmittedReplyText,
     submitMessageToolReply,
     getRuntimeOutputSummary,
   } = createDeliveryReplyDispatcher({
@@ -2947,6 +2961,7 @@ async function runDeliveryReplyDispatch({
     dispatchResult,
     replied: didReply(),
     keptSilent: didKeepSilent(),
+    replyText: getSubmittedReplyText(),
     runtimeOutputSummary: getRuntimeOutputSummary(),
   };
 }
@@ -3020,6 +3035,19 @@ async function maybeBridgeRuntimeInboundEvent({
   const fromAgentId = resolveNormalizedText(metadata.fromAgentId, null);
   const isRelayDelivery = eventType === 'delivery';
   const allowReply = metadata.allowReply === true || (isRelayDelivery && metadata.allowReply !== false);
+  const chatRequestId = resolveNormalizedText(
+    delivery.chatRequestId,
+    resolveNormalizedText(
+      payload.chatRequestId,
+      resolveNormalizedText(
+        payload.requestId,
+        resolveNormalizedText(
+          metadata.kickoffRequestId,
+          resolveNormalizedText(metadata.requestId, resolveNormalizedText(metadata.chatRequestId, null)),
+        ),
+      ),
+    ),
+  );
 
   if (
     !runtime?.channel?.reply?.finalizeInboundContext
@@ -3127,6 +3155,7 @@ async function maybeBridgeRuntimeInboundEvent({
     WasMentioned: false,
     CommandAuthorized: commandAuthorized,
     RelayDeliveryId: isRelayDelivery ? deliveryId : null,
+    RelayChatRequestId: chatRequestId,
     RelayFromAgentId: fromAgentId,
     RelayConversationKey: metadata.conversationKey || null,
     UntrustedContext,
@@ -3187,6 +3216,7 @@ async function maybeBridgeRuntimeInboundEvent({
     dispatchResult,
     replied,
     keptSilent,
+    replyText,
     runtimeOutputSummary,
   } = await runDeliveryReplyDispatch({
     runtime,
@@ -3236,6 +3266,7 @@ async function maybeBridgeRuntimeInboundEvent({
       dispatchResult,
       replied,
       keptSilent,
+      replyText,
       runtimeOutputSummary,
     } = await runDeliveryReplyDispatch({
       runtime,
@@ -3287,6 +3318,40 @@ async function maybeBridgeRuntimeInboundEvent({
         error: error?.message || String(error),
       });
     }
+
+    if (isRelayDelivery) {
+      if (chatRequestId) {
+        try {
+          await recordClaworldTranscriptEpisode(workspaceRoot, {
+            chatRequestId,
+            deliveryId,
+            localSessionKey,
+            relaySessionKey: sessionKey,
+            conversationKey: resolveNormalizedText(metadata.conversationKey, resolveNormalizedText(delivery.conversationKey, null)),
+            worldId,
+            targetAgentId: resolveNormalizedText(delivery.targetAgentId, resolveNormalizedText(payload.targetAgentId, null)),
+            fromAgentId,
+            fromAgentCode: metadata.fromAgentCode,
+            fromDisplayIdentity: metadata.fromDisplayIdentity,
+            localAgentId,
+            deliveryType: metadata.deliveryType,
+            commandText,
+            contextText,
+            untrustedContext: payload.untrustedContext,
+            createdAt: delivery.createdAt || metadata.createdAt || payload.createdAt || null,
+            turnCreatedAt: delivery.turnCreatedAt || metadata.turnCreatedAt || payload.turnCreatedAt || null,
+            replyText,
+          });
+        } catch (error) {
+          logger.warn?.(`[claworld:${runtimeAccountId}] transcript episode indexing failed`, {
+            deliveryId,
+            chatRequestId,
+            sessionKey,
+            error: error?.message || String(error),
+          });
+        }
+      }
+    }
   }
 
   logger.info?.(`[claworld:${runtimeAccountId}] ${isRelayDelivery ? 'delivery bridge completed' : 'inbound bridge completed'}`, {