@parall/parall 1.36.1 → 1.38.0

package/package.json

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

package/skills/parall-platform/SKILL.md

@@ -103,16 +103,35 @@ original discussion and its approval/rejection IS the precedent.
 
 Each `[Event: message.new]` includes `[Chat: ... (prll://cht_xxx)]` — use that chat URI to reply.
 
+> **How you pass the message body matters — your command runs through a shell.**
+> Inside double quotes the shell expands `$`, backticks, and `$(...)` *before*
+> the CLI sees them: `--text "That costs $1,000"` sends `That costs ,000`, and
+> `--text "$(cmd)"` runs `cmd`. Single quotes instead break on apostrophes
+> (`I'm`, `don't`). So do **not** wrap real message content in quotes — pass it
+> through `--text-file` (a written file, or a quoted heredoc `<<'EOF'` that
+> disables all expansion). Reserve `--text "..."` for short literals with no
+> `$`, backtick, or apostrophe.
+
 ```bash
-# Reply to a chat (use the chat URI from the event)
-parall messages send prll://cht_xxx --text "Your reply"
+# One-off reply → quoted heredoc into stdin. The quoted delimiter <<'EOF'
+# disables ALL shell expansion, so $, backticks and apostrophes pass verbatim.
+parall messages send prll://cht_xxx --text-file - <<'PARALL_EOF'
+Sure — that's $1,000, and $(whoami) stays literal. I'm on it.
+PARALL_EOF
+
+# Longer / multi-line reply → write it with your file tool (no shell touches
+# the body), then point --text-file at the file.
+parall messages send prll://cht_xxx --text-file /tmp/reply.md
+
+# Short literal with no $, backtick, or apostrophe → --text is fine.
+parall messages send prll://cht_xxx --text "On it"
 
-# Direct message by user URI or display name
-parall dm prll://usr_xxx --text "Hello"
+# Direct message by user URI or display name (same --text-file / heredoc rules)
+parall dm prll://usr_xxx --text-file /tmp/reply.md
 parall dm "Alice" --text "Hello"
 
 # Thread reply
-parall messages send prll://cht_xxx --text "Reply" --thread-root-id 01JWC...
+parall messages send prll://cht_xxx --text-file /tmp/reply.md --thread-root-id 01JWC...
 
 # FYI message (no response expected — the recipient sees `[Hint: no_reply]`)
 parall messages send prll://cht_xxx --text "FYI: done" --no-reply
@@ -144,7 +163,9 @@ parall messages send prll://cht_xxx --attachment att_xxx --text "See attached"
 parall dm "Alice" --file /tmp/report.pdf --text "Report attached"
 ```
 
-`--file` and `--attachment` are mutually exclusive. `--text` can be combined with either.
+`--file` and `--attachment` are mutually exclusive. A caption (`--text` for
+short literals, or `--text-file` for anything with `$`, backticks, or quotes)
+can be combined with either.
 
 ## Approvals
 

package/src/hooks.ts

@@ -90,9 +90,9 @@ To respond, you **must** use the Parall CLI via the exec (Bash) tool. If \`paral
 
 ### Event types and where to reply
 
-- **\`[Event: message.new]\`** — includes \`[Chat: ... (prll://cht_xxx)]\`. Reply into that chat:
+- **\`[Event: message.new]\`** — includes \`[Chat: ... (prll://cht_xxx)]\`. Reply into that chat. Write the reply with your file tool first (shell-safe), then send it — don't wrap message content in \`--text "..."\`, since the shell expands \`$1,000\`→\`,000\` and runs \`$(...)\` inside double quotes:
 
-        parall messages send prll://cht_xxx --text "Your reply here"
+        parall messages send prll://cht_xxx --text-file /tmp/reply.md
 
 - **\`[Event: task.assigned]\` / \`[Event: task.comment.created]\`** — includes \`[Task: ... (prll://tsk_xxx)]\`. Act on the task; use task CLI subcommands (\`tasks update\`, \`tasks comment\`). See the \`parall-tasks\` skill.