@parall/parall 1.15.0 → 1.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parall/parall",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "OpenClaw channel plugin for Parall IM",
   "license": "MIT",
   "repository": {
@@ -15,8 +15,8 @@
     "openclaw.plugin.json"
   ],
   "dependencies": {
-    "@parall/agent-core": "1.15.0",
-    "@parall/sdk": "1.15.0"
+    "@parall/agent-core": "1.16.0",
+    "@parall/sdk": "1.16.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",

package/skills/parall-platform/SKILL.md

@@ -10,41 +10,46 @@ Query organization data via the Parall CLI. Auth is pre-configured.
 ## Identity
 
 ```bash
-npx @parall/cli@latest whoami
+npx --yes @parall/cli@latest whoami
 ```
 
 ## Members & Agents
 
 ```bash
-npx @parall/cli@latest members list          # All org members (humans + agents)
-npx @parall/cli@latest agents list           # Agents only
-npx @parall/cli@latest users get usr_xxx     # Get user details by ID
+npx --yes @parall/cli@latest members list          # All org members (humans + agents)
+npx --yes @parall/cli@latest agents list           # Agents only
+npx --yes @parall/cli@latest users get prll://usr_xxx     # Get user details by ID
 ```
 
 ## Chats & Messages
 
 ```bash
-npx @parall/cli@latest chats list            # List all chats
-npx @parall/cli@latest messages list cht_xxx # Read chat message history
+npx --yes @parall/cli@latest chats list            # List all chats
+npx --yes @parall/cli@latest messages list prll://cht_xxx # Read chat message history
 ```
 
 ## Sending Messages
 
-Each `[Event: message.new]` includes `[Chat: ... (cht_xxx)]` — always use that chat ID explicitly.
+Each `[Event: message.new]` includes `[Chat: ... (prll://cht_xxx)]` — use that chat URI to reply.
 
 ```bash
-# Reply to a chat (use the chat ID from the event)
-npx @parall/cli@latest messages send cht_xxx --text "Your reply"
+# Reply to a chat (use the chat URI from the event)
+npx --yes @parall/cli@latest messages send prll://cht_xxx --text "Your reply"
 
-# Direct message by user ID or display name
-npx @parall/cli@latest dm usr_xxx --text "Hello"
-npx @parall/cli@latest dm "Alice" --text "Hello"
+# Direct message by user URI or display name
+npx --yes @parall/cli@latest dm prll://usr_xxx --text "Hello"
+npx --yes @parall/cli@latest dm "Alice" --text "Hello"
 
 # Thread reply
-npx @parall/cli@latest messages send cht_xxx --text "Reply" --thread-root-id 01JWC...
+npx --yes @parall/cli@latest messages send prll://cht_xxx --text "Reply" --thread-root-id 01JWC...
 
-# FYI message (no response expected)
-npx @parall/cli@latest messages send cht_xxx --text "FYI: done" --no-reply
+# FYI message (no response expected — the recipient sees `[Hint: no_reply]`)
+npx --yes @parall/cli@latest messages send prll://cht_xxx --text "FYI: done" --no-reply
+
+# Silence this turn entirely — no chat message produced. Use when you receive
+# `[Hint: no_reply]` or otherwise decide the turn needs no visible reply.
+# Run BEFORE any `messages send` / `dm`; those still deliver real messages.
+npx --yes @parall/cli@latest no-reply --reason "ack only, nothing to add"
 ```
 
 All CLI output is JSON.

package/skills/parall-tasks/SKILL.md

@@ -16,14 +16,14 @@ npx @parall/cli@latest tasks list --status todo
 npx @parall/cli@latest tasks list --status in_progress
 
 # Create a task
-npx @parall/cli@latest tasks create --title "Task title" [--assignee-id usr_xxx] [--project-id prj_xxx]
+npx @parall/cli@latest tasks create --title "Task title" [--assignee-id prll://usr_xxx] [--project-id prll://prj_xxx]
 
 # Update task status
-npx @parall/cli@latest tasks update tsk_xxx --status in_progress
-npx @parall/cli@latest tasks update tsk_xxx --status done
+npx @parall/cli@latest tasks update prll://tsk_xxx --status in_progress
+npx @parall/cli@latest tasks update prll://tsk_xxx --status done
 
 # Add a comment
-npx @parall/cli@latest tasks comments add tsk_xxx --body "Progress update..."
+npx @parall/cli@latest tasks comments add prll://tsk_xxx --body "Progress update..."
 ```
 
 ## Project Commands
@@ -36,8 +36,8 @@ npx @parall/cli@latest projects list
 
 When you receive `[Event: task.assigned]`:
 
-1. Acknowledge with a comment: `tasks comments add tsk_xxx --body "On it"`
-2. Update status: `tasks update tsk_xxx --status in_progress`
+1. Acknowledge with a comment: `tasks comments add prll://tsk_xxx --body "On it"`
+2. Update status: `tasks update prll://tsk_xxx --status in_progress`
 3. Do the work
 4. Report results via comment and update status to `done`
 

package/src/gateway.ts

@@ -48,7 +48,7 @@ function buildInboundCtx(
     BodyForAgent: bodyForAgent,
     RawBody: event.body,
     CommandBody: event.body,
-    ...(event.mediaFields ?? {}),
+    // Attachment metadata is now in event.attachments (structured), not mediaFields
     ...(inboundHistory?.length ? { InboundHistory: inboundHistory } : {}),
     From: `parall:${event.senderId}`,
     To: `parall:orchestrator`,
@@ -73,8 +73,11 @@ function buildInboundHistory(events: ParallEvent[]): Array<{ sender: string; bod
     meta.push(`[Message ID: ${event.messageId}]`);
     if (event.noReply) meta.push(`[Hint: no_reply]`);
     if (event.threadRootId) meta.push(`[Thread: ${event.threadRootId}]`);
-    if (event.mediaFields?.MediaUrl) {
-      meta.push(`[Attachment: ${event.mediaFields.MediaType ?? "file"} ${event.mediaFields.MediaUrl}]`);
+    if (event.attachments?.length) {
+      for (const att of event.attachments) {
+        const safeMime = att.mimeType.replace(/[\r\n[\]|]/g, " ").trim();
+        meta.push(`[Attachment: prll://${att.id} | ${safeMime}]`);
+      }
     }
     return {
       sender: event.senderName,

package/src/hooks.ts

@@ -1,5 +1,5 @@
 import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
-import { PRLL_REFERENCE_GUIDE } from "@parall/agent-core";
+import { PRLL_BEHAVIOR, PRLL_IDENTITY, PRLL_REFERENCE_GUIDE } from "@parall/agent-core";
 import { extractAccountIdFromSessionKey } from "./session.js";
 import { clearDispatchGroupKey, getDispatchGroupKey, getDispatchMessageId, getParallAccountState, getSessionChatId } from "./runtime.js";
 
@@ -28,19 +28,30 @@ To reply, you **must** use the Parall CLI via the exec (Bash) tool.
 
 Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) to reply:
 
-    npx @parall/cli@latest messages send prll://cht_xxx --text "Your reply here"
+    npx --yes @parall/cli@latest messages send prll://cht_xxx --text "Your reply here"
 
 Credentials are pre-configured in every Bash command — no setup needed.
 Load the \`parall-platform\` skill for full CLI reference.
 When an event has \`[Hint: no_reply]\`, do not reply to that specific event.
-A dispatch may contain multiple events — only skip replies to the hinted ones.`;
+A dispatch may contain multiple events — only skip replies to the hinted ones.
+
+To silence a turn without running any \`messages send\` / \`dm\`, call:
+
+    npx --yes @parall/cli@latest no-reply [--reason "..."]
+
+Do NOT emit polite acknowledgements like "No response needed" via \`messages send\` — they become real messages and start agent-to-agent loops.`;
 
 export function registerParallHooks(api: OpenClawPluginApi) {
   const log = api.logger;
 
-  // Append Parall channel context + reference guide AFTER workspace files so it takes precedence
+  // Append Parall identity + channel context + behavior charter + reference guide
+  // AFTER workspace files so it takes precedence. Order matters: identity anchors
+  // who the agent is, channel context is a hard interface constraint, behavior
+  // sets working principles, reference guide is the URI lookup reference.
   api.on("before_prompt_build", () => {
-    return { appendSystemContext: PRLL_CHANNEL_CONTEXT + "\n\n" + PRLL_REFERENCE_GUIDE };
+    return {
+      appendSystemContext: [PRLL_IDENTITY, PRLL_CHANNEL_CONTEXT, PRLL_BEHAVIOR, PRLL_REFERENCE_GUIDE].join("\n\n"),
+    };
   });
 
   // before_tool_call -> (1) await step creation to get step ID, (2) ENV injection for exec tool