@parall/claude-agent 1.16.0 → 1.17.0

package/dist/dispatch.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"dispatch.d.ts","sourceRoot":"","sources":["../src/dispatch.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EACV,eAAe,EACf,eAAe,EACf,YAAY,EACZ,QAAQ,EACR,YAAY,EACb,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAErD,OAAO,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAE5D,KAAK,wBAAwB,GAAG,IAAI,CAClC,iBAAiB,EACf,gBAAgB,GAChB,cAAc,GACd,oBAAoB,GACpB,WAAW,GACX,YAAY,GACZ,iBAAiB,GACjB,OAAO,GACP,gBAAgB,GAChB,cAAc,CACjB,GAAG;IACF,cAAc,EAAE,oBAAoB,CAAC;CACtC,CAAC;AAiDF,qBAAa,iBAAkB,YAAW,eAAe;IAC3C,OAAO,CAAC,QAAQ,CAAC,IAAI;gBAAJ,IAAI,EAAE,wBAAwB;IAEpD,QAAQ,CAAC,EAAE,YAAY,EAAE,UAAU,EAAE,OAAO,EAAE,EAAE,YAAY,GAAG,aAAa,CAAC,YAAY,CAAC;IAwGjG,WAAW,CAAC,EAAE,UAAU,EAAE,EAAE,QAAQ;IAIpC,WAAW,CAAC,EAAE,IAAI,EAAE,EAAE,eAAe;IAIrC,OAAO,CAAC,SAAS;CAkClB"}
+{"version":3,"file":"dispatch.d.ts","sourceRoot":"","sources":["../src/dispatch.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EACV,eAAe,EACf,eAAe,EACf,YAAY,EACZ,QAAQ,EACR,YAAY,EACb,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAErD,OAAO,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAE5D,KAAK,wBAAwB,GAAG,IAAI,CAClC,iBAAiB,EACf,gBAAgB,GAChB,cAAc,GACd,oBAAoB,GACpB,WAAW,GACX,YAAY,GACZ,iBAAiB,GACjB,OAAO,GACP,gBAAgB,GAChB,cAAc,CACjB,GAAG;IACF,cAAc,EAAE,oBAAoB,CAAC;CACtC,CAAC;AAEF,qBAAa,iBAAkB,YAAW,eAAe;IAC3C,OAAO,CAAC,QAAQ,CAAC,IAAI;gBAAJ,IAAI,EAAE,wBAAwB;IAEpD,QAAQ,CAAC,EAAE,YAAY,EAAE,UAAU,EAAE,OAAO,EAAE,EAAE,YAAY,GAAG,aAAa,CAAC,YAAY,CAAC;IAwFjG,WAAW,CAAC,EAAE,UAAU,EAAE,EAAE,QAAQ;IAIpC,WAAW,CAAC,EAAE,IAAI,EAAE,EAAE,eAAe;IAIrC,OAAO,CAAC,SAAS;CAkClB"}

package/dist/dispatch.js

@@ -1,60 +1,6 @@
 import { randomUUID } from "node:crypto";
 import { spawn } from "node:child_process";
 import { parseClaudeStreamJson } from "./output-parser.js";
-function extractBashCommand(input) {
-    if (!input || typeof input !== "object")
-        return undefined;
-    const command = input.command;
-    return typeof command === "string" && command.trim() ? command.trim() : undefined;
-}
-// Returns the non-flag tokens that follow a Parall CLI invocation in `command`,
-// or null if the command isn't a Parall CLI call. Handles all the documented
-// forms — bare `parall`, `npx [--yes|-y] @parall/cli[@version]`,
-// `pnpm (exec|dlx) parall` — and skips `npx` flags so that `npx --yes`
-// matches as well as `npx -y`. Tokenization avoids the regex false-match
-// where `messages send --no-reply` looked like the receiver-side `no-reply`.
-function parseParallCliInvocation(command) {
-    const tokens = command.replace(/\s+/g, " ").trim().split(" ");
-    let i = 0;
-    if (tokens[i] === "parall") {
-        i++;
-    }
-    else if (tokens[i] === "npx") {
-        i++;
-        while (i < tokens.length && tokens[i].startsWith("-"))
-            i++;
-        if (i >= tokens.length || !/^@parall\/cli(?:@.+)?$/.test(tokens[i]))
-            return null;
-        i++;
-    }
-    else if (tokens[i] === "pnpm") {
-        i++;
-        if (i < tokens.length && (tokens[i] === "exec" || tokens[i] === "dlx"))
-            i++;
-        if (i >= tokens.length || tokens[i] !== "parall")
-            return null;
-        i++;
-    }
-    else {
-        return null;
-    }
-    return tokens.slice(i).filter((t) => !t.startsWith("-"));
-}
-function isParallSendCommand(command) {
-    if (!command)
-        return false;
-    const sub = parseParallCliInvocation(command);
-    if (!sub || sub.length === 0)
-        return false;
-    // `dm <user>` or `messages send <chat>`
-    return sub[0] === "dm" || (sub[0] === "messages" && sub[1] === "send");
-}
-function isParallNoReplyCommand(command) {
-    if (!command)
-        return false;
-    const sub = parseParallCliInvocation(command);
-    return sub?.[0] === "no-reply";
-}
 export class ClaudeCodeAdapter {
     opts;
     constructor(opts) {
@@ -93,11 +39,6 @@ export class ClaudeCodeAdapter {
         });
         const groupKey = randomUUID();
         let sawError = false;
-        let suppressProjectedText = false;
-        // Sticky for the whole dispatch: set when the agent explicitly calls
-        // `parall no-reply` to silence the turn. All subsequent text events are
-        // emitted with project=false so the bridge never leaks a chat message.
-        let noReplyCalled = false;
         let completed = false;
         try {
             for await (const event of parseClaudeStreamJson(proc.stdout)) {
@@ -105,30 +46,19 @@ export class ClaudeCodeAdapter {
                     this.opts.sessionManager.recordSessionId(sessionKey, event.sessionId);
                     continue;
                 }
-                if (event.type === "tool_call") {
-                    const cmd = extractBashCommand(event.input);
-                    if (isParallNoReplyCommand(cmd)) {
-                        noReplyCalled = true;
-                    }
-                    else if (isParallSendCommand(cmd)) {
-                        suppressProjectedText = true;
-                    }
-                }
                 if (event.type === "error") {
                     sawError = true;
                     yield event;
                     continue;
                 }
                 if (event.type === "text") {
-                    const project = noReplyCalled
-                        ? false
-                        : suppressProjectedText
-                            ? false
-                            : event.project;
-                    suppressProjectedText = false;
+                    // Runtime output contract (symmetric with OpenClaw channel): Claude's
+                    // plain text is never projected as a chat message. To reply, the agent
+                    // must explicitly run `parall messages send` / `dm` via Bash. Text
+                    // events are still recorded as suppressed session steps for audit.
                     yield {
                         ...event,
-                        project,
+                        project: false,
                         groupKey,
                     };
                     continue;

package/dist/workspace.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"workspace.d.ts","sourceRoot":"","sources":["../src/workspace.ts"],"names":[],"mappings":"AAiCA,wBAAgB,qBAAqB,CACnC,YAAY,EAAE,MAAM,EACpB,GAAG,CAAC,EAAE;IAAE,IAAI,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,IAAI,CAAA;CAAE,QA0BtC"}
+{"version":3,"file":"workspace.d.ts","sourceRoot":"","sources":["../src/workspace.ts"],"names":[],"mappings":"AAkCA,wBAAgB,qBAAqB,CACnC,YAAY,EAAE,MAAM,EACpB,GAAG,CAAC,EAAE;IAAE,IAAI,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,IAAI,CAAA;CAAE,QA0BtC"}

package/dist/workspace.js

@@ -2,32 +2,33 @@ import * as fs from "node:fs";
 import * as path from "node:path";
 const CLAUDE_MD = `# CLAUDE.md
 
-You are an agent in Parall IM. You participate in chats, handle tasks, and can use Parall CLI commands for advanced operations.
+You are an agent in Parall IM. You participate in chats, handle tasks, and interact exclusively through the Parall CLI.
 
 ## Message Model
 
 Incoming events are rendered as structured \`[Event: ...]\` blocks.
-Reply with plain text when you want Parall to project your response back into the triggering chat.
+Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) when replying.
+
+**Your plain-text output is not delivered to anyone** — it is recorded as suppressed thinking in your session steps and discarded from the chat.
+To say something in a chat, you **must** invoke the Parall CLI via the Bash tool. To stay silent, simply do not invoke it.
 
 ## Parall CLI
 
-Use CLI only when you need an explicit side effect instead of plain-text projection:
+All outbound interactions go through \`@parall/cli\`. Credentials are pre-injected as environment variables — no setup needed.
 
-- \`npx --yes @parall/cli@latest messages send CHT_ID --text "..." \`
-- \`npx --yes @parall/cli@latest tasks update TSK_ID --status in_progress\`
-- \`npx --yes @parall/cli@latest dm USER_ID --text "..." --no-reply\`
-- \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — end this turn without any visible reply
+- \`npx --yes @parall/cli@latest messages send prll://cht_xxx --text "..."\` — reply into the triggering chat
+- \`npx --yes @parall/cli@latest dm prll://usr_xxx --text "..." [--no-reply]\` — direct message another user
+- \`npx --yes @parall/cli@latest tasks update prll://tsk_xxx --status in_progress\` — task state
+- \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — explicitly declare this turn silent (audit signal; not required for silence, just clarifies intent)
 
-Credentials are already injected through environment variables:
-\`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
+Available env: \`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
 
 ## Guardrails
 
-- If an event includes \`[Hint: no_reply]\`, **run \`npx --yes @parall/cli@latest no-reply\` as your first action** and do not type anything — not even "No response needed" / "Noted" / "OK". Plain text becomes a projected chat message; only the \`no-reply\` command silences the turn.
-- Text emitted BEFORE \`no-reply\` in the same turn is already projected as a message and cannot be retracted; text AFTER is dropped by the bridge.
-- A single dispatch may carry several events coalesced together. Once you call \`no-reply\` in a dispatch, **plain text suppression is sticky for the whole turn** — if some events still need a reply, send them explicitly via \`messages send\` / \`dm\`. Plain-text replies after \`no-reply\` are dropped silently.
-- Prefer plain text over CLI for normal chat replies.
-- Keep replies concise and task-focused.
+- A dispatch may coalesce multiple events. Decide per event whether to reply via \`messages send\` / \`dm\` — events you do not act on simply receive no reply.
+- If an event carries \`[Hint: no_reply]\`, do not send anything for that event. \`no-reply\` is optional and only useful as an explicit intent marker.
+- Never try to "speak" by typing sentences like "No response needed" / "Noted" / "OK" — they are discarded, so they accomplish nothing except polluting your session log.
+- Keep CLI replies concise and task-focused.
 `;
 export function ensureClaudeWorkspace(workspaceDir, log) {
     fs.mkdirSync(workspaceDir, { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parall/claude-agent",
-  "version": "1.16.0",
+  "version": "1.17.0",
   "description": "Claude Code bridge runtime for self-hosted Parall agents",
   "license": "MIT",
   "repository": {
@@ -25,9 +25,9 @@
     "src"
   ],
   "dependencies": {
-    "@parall/agent-core": "1.16.0",
-    "@parall/cli": "1.16.0",
-    "@parall/sdk": "1.16.0"
+    "@parall/sdk": "1.17.0",
+    "@parall/agent-core": "1.17.0",
+    "@parall/cli": "1.17.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",

package/src/dispatch.ts

@@ -26,53 +26,6 @@ type ClaudeCodeAdapterOptions = Pick<
   sessionManager: ClaudeSessionManager;
 };
 
-function extractBashCommand(input: unknown): string | undefined {
-  if (!input || typeof input !== "object") return undefined;
-  const command = (input as { command?: unknown }).command;
-  return typeof command === "string" && command.trim() ? command.trim() : undefined;
-}
-
-// Returns the non-flag tokens that follow a Parall CLI invocation in `command`,
-// or null if the command isn't a Parall CLI call. Handles all the documented
-// forms — bare `parall`, `npx [--yes|-y] @parall/cli[@version]`,
-// `pnpm (exec|dlx) parall` — and skips `npx` flags so that `npx --yes`
-// matches as well as `npx -y`. Tokenization avoids the regex false-match
-// where `messages send --no-reply` looked like the receiver-side `no-reply`.
-function parseParallCliInvocation(command: string): string[] | null {
-  const tokens = command.replace(/\s+/g, " ").trim().split(" ");
-  let i = 0;
-  if (tokens[i] === "parall") {
-    i++;
-  } else if (tokens[i] === "npx") {
-    i++;
-    while (i < tokens.length && tokens[i].startsWith("-")) i++;
-    if (i >= tokens.length || !/^@parall\/cli(?:@.+)?$/.test(tokens[i])) return null;
-    i++;
-  } else if (tokens[i] === "pnpm") {
-    i++;
-    if (i < tokens.length && (tokens[i] === "exec" || tokens[i] === "dlx")) i++;
-    if (i >= tokens.length || tokens[i] !== "parall") return null;
-    i++;
-  } else {
-    return null;
-  }
-  return tokens.slice(i).filter((t) => !t.startsWith("-"));
-}
-
-function isParallSendCommand(command: string | undefined): boolean {
-  if (!command) return false;
-  const sub = parseParallCliInvocation(command);
-  if (!sub || sub.length === 0) return false;
-  // `dm <user>` or `messages send <chat>`
-  return sub[0] === "dm" || (sub[0] === "messages" && sub[1] === "send");
-}
-
-function isParallNoReplyCommand(command: string | undefined): boolean {
-  if (!command) return false;
-  const sub = parseParallCliInvocation(command);
-  return sub?.[0] === "no-reply";
-}
-
 export class ClaudeCodeAdapter implements DispatchAdapter {
   constructor(private readonly opts: ClaudeCodeAdapterOptions) {}
 
@@ -115,11 +68,6 @@ export class ClaudeCodeAdapter implements DispatchAdapter {
 
     const groupKey = randomUUID();
     let sawError = false;
-    let suppressProjectedText = false;
-    // Sticky for the whole dispatch: set when the agent explicitly calls
-    // `parall no-reply` to silence the turn. All subsequent text events are
-    // emitted with project=false so the bridge never leaks a chat message.
-    let noReplyCalled = false;
     let completed = false;
 
     try {
@@ -129,15 +77,6 @@ export class ClaudeCodeAdapter implements DispatchAdapter {
           continue;
         }
 
-        if (event.type === "tool_call") {
-          const cmd = extractBashCommand(event.input);
-          if (isParallNoReplyCommand(cmd)) {
-            noReplyCalled = true;
-          } else if (isParallSendCommand(cmd)) {
-            suppressProjectedText = true;
-          }
-        }
-
         if (event.type === "error") {
           sawError = true;
           yield event;
@@ -145,15 +84,13 @@ export class ClaudeCodeAdapter implements DispatchAdapter {
         }
 
         if (event.type === "text") {
-          const project = noReplyCalled
-            ? false
-            : suppressProjectedText
-              ? false
-              : event.project;
-          suppressProjectedText = false;
+          // Runtime output contract (symmetric with OpenClaw channel): Claude's
+          // plain text is never projected as a chat message. To reply, the agent
+          // must explicitly run `parall messages send` / `dm` via Bash. Text
+          // events are still recorded as suppressed session steps for audit.
           yield {
             ...event,
-            project,
+            project: false,
             groupKey,
           };
           continue;

package/src/workspace.ts

@@ -3,32 +3,33 @@ import * as path from "node:path";
 
 const CLAUDE_MD = `# CLAUDE.md
 
-You are an agent in Parall IM. You participate in chats, handle tasks, and can use Parall CLI commands for advanced operations.
+You are an agent in Parall IM. You participate in chats, handle tasks, and interact exclusively through the Parall CLI.
 
 ## Message Model
 
 Incoming events are rendered as structured \`[Event: ...]\` blocks.
-Reply with plain text when you want Parall to project your response back into the triggering chat.
+Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) when replying.
+
+**Your plain-text output is not delivered to anyone** — it is recorded as suppressed thinking in your session steps and discarded from the chat.
+To say something in a chat, you **must** invoke the Parall CLI via the Bash tool. To stay silent, simply do not invoke it.
 
 ## Parall CLI
 
-Use CLI only when you need an explicit side effect instead of plain-text projection:
+All outbound interactions go through \`@parall/cli\`. Credentials are pre-injected as environment variables — no setup needed.
 
-- \`npx --yes @parall/cli@latest messages send CHT_ID --text "..." \`
-- \`npx --yes @parall/cli@latest tasks update TSK_ID --status in_progress\`
-- \`npx --yes @parall/cli@latest dm USER_ID --text "..." --no-reply\`
-- \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — end this turn without any visible reply
+- \`npx --yes @parall/cli@latest messages send prll://cht_xxx --text "..."\` — reply into the triggering chat
+- \`npx --yes @parall/cli@latest dm prll://usr_xxx --text "..." [--no-reply]\` — direct message another user
+- \`npx --yes @parall/cli@latest tasks update prll://tsk_xxx --status in_progress\` — task state
+- \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — explicitly declare this turn silent (audit signal; not required for silence, just clarifies intent)
 
-Credentials are already injected through environment variables:
-\`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
+Available env: \`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
 
 ## Guardrails
 
-- If an event includes \`[Hint: no_reply]\`, **run \`npx --yes @parall/cli@latest no-reply\` as your first action** and do not type anything — not even "No response needed" / "Noted" / "OK". Plain text becomes a projected chat message; only the \`no-reply\` command silences the turn.
-- Text emitted BEFORE \`no-reply\` in the same turn is already projected as a message and cannot be retracted; text AFTER is dropped by the bridge.
-- A single dispatch may carry several events coalesced together. Once you call \`no-reply\` in a dispatch, **plain text suppression is sticky for the whole turn** — if some events still need a reply, send them explicitly via \`messages send\` / \`dm\`. Plain-text replies after \`no-reply\` are dropped silently.
-- Prefer plain text over CLI for normal chat replies.
-- Keep replies concise and task-focused.
+- A dispatch may coalesce multiple events. Decide per event whether to reply via \`messages send\` / \`dm\` — events you do not act on simply receive no reply.
+- If an event carries \`[Hint: no_reply]\`, do not send anything for that event. \`no-reply\` is optional and only useful as an explicit intent marker.
+- Never try to "speak" by typing sentences like "No response needed" / "Noted" / "OK" — they are discarded, so they accomplish nothing except polluting your session log.
+- Keep CLI replies concise and task-focused.
 `;
 
 export function ensureClaudeWorkspace(