@parall/parall 1.52.0 → 1.52.2

package/dist/index.bundle.mjs

@@ -51509,6 +51509,8 @@ var ENDPOINTS = {
   SLACK_HISTORY: (orgId) => `${API_BASE}/orgs/${orgId}/agents/me/slack/history`,
   SLACK_MEMBERS: (orgId) => `${API_BASE}/orgs/${orgId}/agents/me/slack/members`,
   SLACK_STATUS: (orgId) => `${API_BASE}/orgs/${orgId}/agents/me/slack/status`,
+  // WeChat tier-B read verb (agent-only; internal research preview).
+  WECHAT_CONTACTS: (orgId) => `${API_BASE}/orgs/${orgId}/agents/me/wechat/contacts`,
   // Invitations (org-scoped, admin)
   ORG_INVITATIONS: (orgId) => `${API_BASE}/orgs/${orgId}/invitations`,
   ORG_INVITATION: (orgId, invId) => `${API_BASE}/orgs/${orgId}/invitations/${invId}`,
@@ -51670,8 +51672,6 @@ var ENDPOINTS = {
   // Live viewer command — on api-server (API_BASE), not clip-service: it rides
   // the machine control-plane request/reply bridge that lives in api-server.
   BROWSER_PROFILE_VIEWER_COMMAND: (orgId, profileId) => `${API_BASE}/orgs/${orgId}/browser-profiles/${profileId}/viewer/command`,
-  // Clip registry (global, served by clip-service → Pinix Hub proxy)
-  CLIP_REGISTRY: () => `${CLIP_BASE}/registry/clips`,
   // Edge device endpoints
   ORG_EDGE: (orgId) => `/api/v1/orgs/${orgId}/edge`,
   ORG_EDGE_DEVICES: (orgId) => `/api/v1/orgs/${orgId}/edge/devices`,
@@ -51688,15 +51688,20 @@ var ENDPOINTS = {
   ORG_EDGE_VIEWER_COMMAND: (orgId, edgeId) => `/api/v1/orgs/${orgId}/edge/${edgeId}/viewer/command`,
   CLIP_CONNECTIONS: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}/connections`,
   CLIP_CONNECTION: (orgId, connId) => `/api/v1/orgs/${orgId}/clip-connections/${connId}`,
-  // Clip registry (v3, org-scoped, served by api-server — `crg_` entries; the
-  // Pinix Hub catalog proxy above is a different, id-less surface)
+  // Clip registry (v3, org-scoped, served by api-server — `crg_` entries)
   ORG_CLIP_REGISTRY: (orgId) => `/api/v1/orgs/${orgId}/clip-registry`,
+  ORG_CLIP_REGISTRY_CLIP: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}`,
+  ORG_CLIP_REGISTRY_PUBLISH: (orgId) => `/api/v1/orgs/${orgId}/clip-registry/publish`,
   ORG_CLIP_INSTALL: (orgId) => `/api/v1/orgs/${orgId}/clips/install`,
   ORG_CLIPS_INSTALLED: (orgId) => `/api/v1/orgs/${orgId}/clips/installed`,
+  ORG_CLIP_UNINSTALL: (orgId, clipId) => `/api/v1/orgs/${orgId}/clips/${clipId}/uninstall`,
+  // Per-org agent exec access for one clip (default all agents; PUT human-only)
+  ORG_CLIP_EXEC_ACCESS: (orgId, clipId) => `/api/v1/orgs/${orgId}/clips/${clipId}/exec-access`,
   // MCP clip server config (cap:clip-mcp; publisher-org only — cross-org gets
   // 403 MCP_CROSS_ORG_DISABLED on the whole family, reads included)
   ORG_CLIP_MCP_CONFIG: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}/mcp-config`,
-  ORG_CLIP_MCP_TOOLS_REFRESH: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}/mcp-config/tools/refresh`
+  ORG_CLIP_MCP_TOOLS_REFRESH: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}/mcp-config/tools/refresh`,
+  ORG_CLIP_MCP_OAUTH_DISCONNECT: (orgId, clipId) => `/api/v1/orgs/${orgId}/clip-registry/${clipId}/mcp-config/oauth/disconnect`
 };
 var WS_EVENTS = {
   // Client -> Server
@@ -53192,6 +53197,14 @@ var ParallClient = class _ParallClient {
   async setSlackStatus(orgId, input) {
     await this.request("POST", ENDPOINTS.SLACK_STATUS(orgId), input);
   }
+  /**
+   * WeChat tier-B read verb (agent-only; internal research preview): the
+   * account's address book — friend wxids, saved group room ids, followed
+   * official accounts. Same live gate as the send verb.
+   */
+  async listWechatContacts(orgId) {
+    return this.request("GET", ENDPOINTS.WECHAT_CONTACTS(orgId));
+  }
   async listChannelConversations(orgId, connectionId) {
     return this.request("GET", ENDPOINTS.CHANNEL_CONNECTION_CONVERSATIONS(orgId, connectionId));
   }
@@ -53730,17 +53743,11 @@ var ParallClient = class _ParallClient {
   async revokeBrowserProfileConsent(orgId, profileId, clipId) {
     await this.request("DELETE", ENDPOINTS.BROWSER_PROFILE_CONSENT(orgId, profileId, clipId));
   }
-  async listRegistryClips(q) {
-    const url = ENDPOINTS.CLIP_REGISTRY() + (q ? `?q=${encodeURIComponent(q)}` : "");
-    const resp = await this.request("GET", url);
-    return resp.data;
-  }
   // ---- Clip registry (v3, api-server org registry — `crg_` entries) ----
   /**
    * List registry clips visible to the org: its own plus public+approved
    * cross-org entries. This is the surface `installRegistryClip` and clip
-   * connections operate on — NOT the Pinix catalog proxy
-   * ({@link listRegistryClips}), whose entries carry no `crg_` id.
+   * connections operate on.
    */
   async listOrgRegistryClips(orgId) {
     const resp = await this.request("GET", `${ENDPOINTS.ORG_CLIP_REGISTRY(orgId)}?limit=100`);
@@ -53755,11 +53762,58 @@ var ParallClient = class _ParallClient {
   async installRegistryClip(orgId, clipId) {
     return this.request("POST", ENDPOINTS.ORG_CLIP_INSTALL(orgId), { clip_id: clipId });
   }
+  /**
+   * Remove an org's install of a registry clip. Keyed by the REGISTRY id
+   * (`crg_`), the same id {@link installRegistryClip} takes — the v2
+   * `deleteClip` operates on a different table and cannot reach these.
+   */
+  async uninstallRegistryClip(orgId, clipId) {
+    await this.request("DELETE", ENDPOINTS.ORG_CLIP_UNINSTALL(orgId, clipId));
+  }
   /** List the org's installed registry clips (full entries). */
   async listInstalledRegistryClips(orgId) {
     const resp = await this.request("GET", ENDPOINTS.ORG_CLIPS_INSTALLED(orgId));
     return resp ?? [];
   }
+  /**
+   * Fetch one registry clip by its `crg_` id. For a clip OWNED by the calling
+   * org the entry additionally carries `review_status`/`review_note` — the
+   * state of the latest submitted version and the reviewer's rejection
+   * feedback. This is the polling surface for "did platform review approve my
+   * public publish yet"; cross-org callers see only public+approved entries
+   * and never any review-state fields.
+   */
+  async getRegistryClip(orgId, clipId) {
+    return this.request("GET", ENDPOINTS.ORG_CLIP_REGISTRY_CLIP(orgId, clipId));
+  }
+  /**
+   * Publish (create, or author-only update) a clip in the org registry,
+   * replacing its whole file set. See {@link PublishRegistryClipRequest} for
+   * the visibility/review semantics; the returned entry carries
+   * `review_status` when a public publish queued a review submission — poll
+   * {@link getRegistryClip} for the outcome.
+   */
+  async publishRegistryClip(orgId, req) {
+    return this.request("POST", ENDPOINTS.ORG_CLIP_REGISTRY_PUBLISH(orgId), req, void 0, false, {
+      timeoutMs: 6e4
+    });
+  }
+  /**
+   * Read a clip's per-org agent exec access. Org-member readable (agents
+   * included, so a denied agent can learn why exec answered
+   * `CLIP_AGENT_NOT_ALLOWED`).
+   */
+  async getClipAgentExecAccess(orgId, clipId) {
+    return this.request("GET", ENDPOINTS.ORG_CLIP_EXEC_ACCESS(orgId, clipId));
+  }
+  /**
+   * Replace a clip's per-org agent exec access. Human-only (agent principals
+   * get 403); under `all_agents` the `agent_ids` must be empty. Every granted
+   * id must be an active agent of this org (else `400 INVALID_INPUT`).
+   */
+  async putClipAgentExecAccess(orgId, clipId, access) {
+    return this.request("PUT", ENDPOINTS.ORG_CLIP_EXEC_ACCESS(orgId, clipId), access);
+  }
   // ---- Edge devices ----
   async listEdgeDevices(orgId) {
     return this.request("GET", ENDPOINTS.ORG_EDGE_DEVICES(orgId));
@@ -54509,10 +54563,16 @@ function buildSendMessageHint(event) {
         const replyTo = event.channelExternalMessageId ? ` --reply-to "${event.channelExternalMessageId}"` : "";
         return `
 <system-reminder>To reply, use the platform verb: \`parall slack send${channelArg}${replyTo} --text <your reply>\`. In channels --reply-to is REQUIRED (the reply lands in that message's thread); in DMs it is optional (DMs are linear). \`parall slack send\` is the ONLY outbound path \u2014 your plain text output is NOT delivered to the external conversation.</system-reminder>`;
+      }
+      if (event.channelProvider === "wechat") {
+        const toArg = event.channelExternalConversationId ? ` --to "${event.channelExternalConversationId}"` : " --to <wxid from this event>";
+        const atArg = event.channelConversationType === "group" ? event.senderId && event.senderId !== "external" ? ` --at "${event.senderId}"` : " --at <wxid of the person you are answering>" : "";
+        return `
+<system-reminder>To reply, use the platform verb: \`parall wechat send${toArg}${atArg} --text <your reply>\`. In group chats, --at @-mentions the person you are answering. \`parall wechat send\` is the ONLY outbound path \u2014 your plain text output is NOT delivered to the external conversation.</system-reminder>`;
       }
       if (!event.channelProvider) {
         return `
-<system-reminder>To reply, use the channel capability granted in your system prompt \u2014 for Feishu conversations that is \`lark-cli im\`, for Slack it is \`parall slack send\` (pass the message id from this event as --reply-to). That capability is the ONLY outbound path \u2014 your plain text output is NOT delivered to the external conversation.</system-reminder>`;
+<system-reminder>To reply, use the channel capability granted in your system prompt \u2014 for Feishu conversations that is \`lark-cli im\`, for Slack it is \`parall slack send\` (pass the message id from this event as --reply-to), for WeChat it is \`parall wechat send\`. That capability is the ONLY outbound path \u2014 your plain text output is NOT delivered to the external conversation.</system-reminder>`;
       }
       const convRef = event.channelExternalConversationId ? `chat_id "${event.channelExternalConversationId}"` : "the conversation id named in this event";
       const threadAlt = event.channelExternalMessageId ? ` To reply threaded to this specific message, reference message_id "${event.channelExternalMessageId}".` : "";
@@ -54991,13 +55051,33 @@ var LaneLedger = class {
 };
 
 // ../agent-core/dist/gateway-lane-flow.js
+function shiftMainBufferGroup(host, groupKey, preserveInjectedFrameBoundary) {
+  const events = [];
+  while (host.dispatchState.mainBuffer[0] && host.dispatchGroupKey(host.dispatchState.mainBuffer[0]) === groupKey && (!preserveInjectedFrameBoundary || events.length === 0)) {
+    events.push(host.dispatchState.mainBuffer.shift());
+  }
+  return events;
+}
+function hasUninjectedSameLaneEventAhead(host, event) {
+  const eventIndex = host.dispatchState.mainBuffer.lastIndexOf(event);
+  if (eventIndex <= 0)
+    return false;
+  const groupKey = host.dispatchGroupKey(event);
+  return host.dispatchState.mainBuffer.slice(0, eventIndex).some((buffered) => host.dispatchGroupKey(buffered) === groupKey && !host.injectedMainBufferEvents.has(buffered));
+}
 async function steerLaneMessage(host, event) {
   const { laneLedger: ledger, opts } = host;
   const adapter = opts.dispatchAdapter;
   if (!ledger || !adapter.enqueueDuringDispatch)
     return;
+  if (hasUninjectedSameLaneEventAhead(host, event))
+    return;
   const folded = await ledger.steerLive(event);
-  if (folded && await adapter.enqueueDuringDispatch(opts.runtimeKey, buildEventBody(event), folded.inputLifecycle)) {
+  if (!folded)
+    return;
+  const injected = await adapter.enqueueDuringDispatch(opts.runtimeKey, buildEventBody(event), folded.inputLifecycle);
+  if (injected) {
+    host.injectedMainBufferEvents.add(event);
     opts.log?.info(`steer folded+injected for ${event.messageId} (will drain for bookkeeping)`);
   }
 }
@@ -55629,6 +55709,22 @@ All three forms work \u2014 pick whichever fits:
 Bare URIs and empty-context refs are preferred in most cases \u2014 the platform
 resolves and renders the entity title automatically.
 
+### Mentioning people and agents
+
+A real member mention is a \`prll://usr_...\` reference. Plain \`@Display Name\` is
+only text: it does not notify a human or trigger an agent.
+
+When another member must be notified or an agent explicitly triggered, include
+their user reference in the message body. Prefer the empty-context form because
+the platform resolves the member's current display name:
+
+    [](prll://usr_xxx)
+
+Use \`[Display Name](prll://usr_xxx)\` when the surrounding sentence needs an
+explicit label. Find the user ID in the incoming message or with
+\`parall members list\`. Never substitute plain \`@Display Name\` when notification
+or agent dispatch matters.
+
 ### URI format
 
 \`prll://\` follows standard URI structure: \`scheme://authority/path?query#fragment\`.
@@ -55858,9 +55954,12 @@ import * as path2 from "node:path";
 import { fileURLToPath } from "node:url";
 var CAPABILITY_FEISHU_CLI = "feishu-cli";
 var CAPABILITY_SLACK_SEND = "slack-send";
+var CAPABILITY_WECHAT_SEND = "wechat-send";
 function channelCapabilityKeyFor(provider) {
   if (provider === "slack")
     return CAPABILITY_SLACK_SEND;
+  if (provider === "wechat")
+    return CAPABILITY_WECHAT_SEND;
   return `${provider}-cli`;
 }
 var CHANNEL_POINTER_MAGIC = "parall channel capability pointer";
@@ -57043,6 +57142,7 @@ var ParallAgentGateway = class {
   // (stable mapping; avoids one connection fetch per inbound message).
   channelConnectionProviders = /* @__PURE__ */ new Map();
   dispatchedMessages = /* @__PURE__ */ new Set();
+  injectedMainBufferEvents = /* @__PURE__ */ new WeakSet();
   // Per-WorkItem failure backoff for typed dispatch consumption — see
   // LaneFlowHost.typedRedriveBackoff in gateway-lane-flow.ts.
   typedRedriveBackoff = /* @__PURE__ */ new Map();
@@ -58255,13 +58355,10 @@ var ParallAgentGateway = class {
           break;
         }
         const groupKey = this.dispatchGroupKey(this.dispatchState.mainBuffer[0]);
-        const events = [];
-        while (this.dispatchState.mainBuffer[0] && this.dispatchGroupKey(this.dispatchState.mainBuffer[0]) === groupKey) {
-          events.push(this.dispatchState.mainBuffer.shift());
-        }
+        const hasPendingInjections = this.opts.dispatchAdapter.hasPendingInjections?.(this.opts.runtimeKey) ?? false;
+        const events = shiftMainBufferGroup(this.laneFlowHost(), groupKey, hasPendingInjections && this.opts.dispatchAdapter.inputLifecycleMode === "explicit");
         const event = events[events.length - 1];
         const earlier = events.slice(0, -1);
-        const hasPendingInjections = this.opts.dispatchAdapter.hasPendingInjections?.(this.opts.runtimeKey) ?? false;
         const pendingFork = hasPendingInjections ? [] : this.dispatchState.pendingForkResults.splice(0);
         const forkPrefix = buildForkResultPrefix(pendingFork);
         this.dispatchState.mainCurrentTargetId = event.targetId;
@@ -58974,7 +59071,7 @@ var ParallAgentGateway = class {
       }
     }
     const keys = this.opts.getCapabilityKeys?.() ?? [];
-    const cliCapable = provider ? keys.includes(channelCapabilityKeyFor(provider)) : keys.some((k) => k.endsWith("-cli") || k === CAPABILITY_SLACK_SEND);
+    const cliCapable = provider ? keys.includes(channelCapabilityKeyFor(provider)) : keys.some((k) => k.endsWith("-cli") || k === CAPABILITY_SLACK_SEND || k === CAPABILITY_WECHAT_SEND);
     const event = {
       type: "channel_message",
       targetId: conv.id,

package/package.json

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

package/skills/parall-clips/SKILL.md

@@ -1,46 +1,60 @@
 ---
 name: parall-clips
-description: "Parall clip operations: list installed clips, invoke clip commands, inspect clip details. Use when: the task requires external capabilities (GitHub, web search, etc.), user asks about available tools/clips, or you need to call a clip command."
+description: "Parall clip operations: list installed clips and their connections, inspect clip commands/tools, execute clip commands on an explicit connection. Use when: the task requires external capabilities (GitHub, web search, etc.), user asks about available tools/clips, or you need to call a clip command."
 ---
 
 # Parall Clips
 
 Clips are packaged capabilities that let agents operate external systems —
-APIs and websites — through named commands installed in the org.
+APIs, websites, remote tools — through named commands installed in the org.
 
 ## Discover
 
 ```bash
-parall clip list            # clips installed in this org
-parall clip info <alias>    # commands, params, version
+parall clip list               # installed clips + each clip's connections
+parall clip info <clip>        # commands + per-command params (manifest)
+parall clip connections <clip> # one clip's connections, full rows
+parall clip tools <clip>       # MCP clips only: live tool schemas
 ```
 
-## Invoke
+`clip list` answers both discovery questions at once: WHICH clip (name,
+description, version) and WHERE it can run — every connection with its
+`ccn_…` id, alias, and target kind:
 
-```bash
-parall clip invoke <alias> <command> [input] [--timeout <ms>]   # timeout default 30s
-# input: JSON string or plain text, per the command's params in `info`
-parall clip invoke github-tools list-repos '{"org":"acme"}'
-```
-
-Results are JSON on stdout; failures print an error.
+- `cloud` — an org-shared cloud profile (a maintainer's signed-in browser)
+- `desktop` — a member's own device (only its owner can exec through it)
+- `mcp` — a remote MCP tool server
+- `device` — a device whose placement could not be resolved just now (the
+  device list was unavailable); don't guess which kind it is — re-run
+  discovery, and treat a persistent `device` like an unverified target
+- `orphaned` — the target device is gone; the connection is unusable
 
-## Execute on an Edge device (registry clips)
+Pick the connection whose alias names the account/device the task needs
+(e.g. `ins-nyc` vs `ins-boston`). A row without an alias can only be
+referenced by `ccn_` id — when aliases are missing and several connections
+could match, ask a human to name them in the Clip Console rather than
+guessing which signed-in account you are about to act through.
 
-Registry clips run on an Edge — a member's desktop, or an org-shared cloud
-profile. **Name the target explicitly.** A cloud profile has NO implicit
-route; omitting the target entirely is a desktop-only legacy form that
-reaches just YOUR OWN online desktop device — never a shared cloud profile.
+## Execute
 
 ```bash
-parall clip exec <clip> <command> [args] --connection <id|alias>  # the normal form
+parall clip exec <clip> <command> [args] --connection <ccn_|alias>  # the normal form
 parall clip exec browser-tools screenshot '{"url":"…"}' --connection cloud-main
 ```
 
+Build `args` as JSON per the command's params from `clip info` (or the
+tool's `inputSchema` from `clip tools` for MCP clips — tool names are NOT
+frozen in the manifest, so never guess a tool name or its argument shape).
+Results are JSON on stdout; failures print a typed error.
+
+**Name the target explicitly.** A cloud profile has NO implicit route;
+omitting the target entirely is a desktop-only legacy form that reaches just
+YOUR OWN online desktop device — never a shared cloud profile.
+
 - A cloud (hosted) profile is reachable ONLY via `--connection` — the clip
-  connection its maintainer bound (`ccn_…` id or alias). That binding IS your
-  authorization; without one the server answers `HOSTED_CONNECTION_REQUIRED`
-  and the fix is to ask an owner/admin to bind the clip, never to retry.
+  connection its maintainer bound. That binding IS your authorization;
+  without one the server answers `HOSTED_CONNECTION_REQUIRED` and the fix
+  is to ask an owner/admin to bind the clip, never to retry.
 - `--edge <edgeId>` targets only a desktop device YOU own.
 - Waiting on a cloud profile is handled by the CLI: `EDGE_ACTIVATING` (cold
   start), `EDGE_BUSY` (another exec is running) and
@@ -52,19 +66,10 @@ parall clip exec browser-tools screenshot '{"url":"…"}' --connection cloud-mai
 
 ## MCP clips (remote tool servers)
 
-Some registry clips are backed by a remote MCP server instead of an Edge
-device. The command is an MCP tool name and the args are that tool's JSON
-arguments — but **MCP tool names are NOT frozen in `clip info`, so discover
-them first; never guess a tool name or its argument shape**. Before invoking,
-find the connection AND the tool schemas:
-
-```bash
-parall clip connections <alias>   # the ccn_ id / alias to pass to --connection
-parall clip tools <alias>         # tool names + descriptions + inputSchema (JSON)
-```
-
-Read each tool's `inputSchema` from `clip tools` to build valid args, then
-exec against that explicit target — same form as an Edge clip:
+A connection with target `mcp` routes to a remote MCP server; the command
+is an MCP tool name and the args are that tool's JSON arguments. Read each
+tool's `inputSchema` from `clip tools` first, then exec against the
+explicit target — the same form as any other clip:
 
 ```bash
 parall clip exec <clip> <tool> [json-args] --connection <ccn_|alias>
@@ -82,13 +87,11 @@ parall clip exec <clip> <tool> [json-args] --connection <ccn_|alias>
 
 ## Behavior rules
 
-- An authorization error (clip not bound to you) is a fail-fast: ask the
-  clip's owner or an admin to bind it — do not retry or work around it.
-- If the executing runtime is offline or the call times out, report that
+- An authorization error (`HOSTED_CONNECTION_REQUIRED`, `FORBIDDEN`) is a
+  fail-fast: ask the clip's maintainer or an org admin to bind the clip or
+  grant the connection — do not retry or work around it.
+- If the target device is offline or the call times out, report that
   plainly; do not queue, and never fabricate a result for a run that errored.
-- Hosted browser activation is handled by the CLI: it waits (bounded) while a
-  cold hosted browser starts, so if the invoke still fails, report the error —
-  do not blind-retry in a loop.
 - **`OUTCOME_UNKNOWN` is never retryable.** It means the command was
   dispatched and MAY HAVE EXECUTED even though no result came back. Retrying
   could post, order or delete twice. Verify the effect through the system you
@@ -104,5 +107,7 @@ parall clip exec <clip> <tool> [json-args] --connection <ccn_|alias>
 - A clip may act through a person's real logged-in account — outward,
   irreversible, or spending actions (post, order, delete, pay) get the same
   caution as any shared-state change: confirm when intent isn't explicit.
+  The connection's alias/target tells you WHICH account you are acting as —
+  if that is ambiguous, resolve it with a human before acting, not after.
 - Reach for `parall clip list` whenever a task needs capabilities beyond
   built-in tools.