@parall/parall 1.14.5 → 1.15.1

package/package.json

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

package/skills/parall-platform/SKILL.md

@@ -18,33 +18,33 @@ npx @parall/cli@latest whoami
 ```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 @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 @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 @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"
+# Direct message by user URI or display name
+npx @parall/cli@latest dm prll://usr_xxx --text "Hello"
 npx @parall/cli@latest dm "Alice" --text "Hello"
 
 # Thread reply
-npx @parall/cli@latest messages send cht_xxx --text "Reply" --thread-root-id 01JWC...
+npx @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
+npx @parall/cli@latest messages send prll://cht_xxx --text "FYI: done" --no-reply
 ```
 
 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/hooks.ts

@@ -1,4 +1,5 @@
 import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+import { PRLL_REFERENCE_GUIDE } from "@parall/agent-core";
 import { extractAccountIdFromSessionKey } from "./session.js";
 import { clearDispatchGroupKey, getDispatchGroupKey, getDispatchMessageId, getParallAccountState, getSessionChatId } from "./runtime.js";
 
@@ -25,9 +26,9 @@ Messages from the Parall channel arrive as \`[Event: ...]\` blocks.
 Your text output is **not delivered to the user** — it is discarded silently.
 To reply, you **must** use the Parall CLI via the exec (Bash) tool.
 
-Each event includes \`[Chat: ... (cht_xxx)]\` — use that chat ID to reply:
+Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) to reply:
 
-    npx @parall/cli@latest messages send cht_xxx --text "Your reply here"
+    npx @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.
@@ -37,9 +38,9 @@ A dispatch may contain multiple events — only skip replies to the hinted ones.
 export function registerParallHooks(api: OpenClawPluginApi) {
   const log = api.logger;
 
-  // Append Parall channel context AFTER workspace files so it takes precedence
+  // Append Parall channel context + reference guide AFTER workspace files so it takes precedence
   api.on("before_prompt_build", () => {
-    return { appendSystemContext: PRLL_CHANNEL_CONTEXT };
+    return { appendSystemContext: PRLL_CHANNEL_CONTEXT + "\n\n" + PRLL_REFERENCE_GUIDE };
   });
 
   // before_tool_call -> (1) await step creation to get step ID, (2) ENV injection for exec tool