@inline-openclaw/inline 0.0.62 → 0.0.64

package/README.md

@@ -34,18 +34,28 @@ Reply-thread behavior:
 
 ## Install
 
-Requires OpenClaw `2026.6.11` or newer.
+The current Inline plugin targets OpenClaw `2026.8.x` from `2026.8.2`. Install
+the plugin version for your OpenClaw release line:
+
+| OpenClaw line | Inline plugin | Exact install |
+| --- | --- | --- |
+| `2026.8.x` (`>=2026.8.2`) | `0.0.64` | `openclaw plugins install --force @inline-openclaw/inline@0.0.64` |
+| `2026.7.x` | `0.0.63` | `openclaw plugins install --force @inline-openclaw/inline@0.0.63` |
+| `2026.6.x` (`>=2026.6.11`, including extended-stable `2026.6.34`) | `0.0.63` | `openclaw plugins install --force @inline-openclaw/inline@0.0.63` |
+
+`@latest` follows the newest supported OpenClaw line; it is not a compatibility
+alias for older host APIs.
 
 ## Compatibility
 
 | Plugin version | OpenClaw host | Inline realtime SDK | Status | Notes |
 | --- | --- | --- | --- | --- |
-| `0.0.62` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Current | Keeps the thread-only Following control out of direct-message agent settings, where the server does not support it. |
+| `0.0.64` | `>=2026.8.2 <2026.9.0` | `0.0.17` | Current | Supports the stable 2026.8 plugin SDK and preserves DM/group reply-thread routing. |
+| `0.0.63` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Previous | Applies live-safe settings writes without restarting the Inline channel before it can answer. |
+| `0.0.62` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Previous | Keeps the thread-only Following control out of direct-message agent settings, where the server does not support it. |
 | `0.0.61` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Previous | Bounds model discovery through provider authentication so agent settings return a fallback instead of hanging indefinitely. |
 | `0.0.60` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Previous | Uses the plugin index's supported force-install path for exact updates on current OpenClaw hosts. |
 | `0.0.59` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Previous | Adds mentionable Agent specialization, exact Agent activation, and fail-closed bot-message provenance. |
-| `0.0.57` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.14` | Previous | Hardens exact CLI-managed upgrades, deterministic channel listing, default/help consistency, and packed-artifact validation. |
-| `0.0.56` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.14` | Stable | Finalizes unified Inline CLI setup compatibility while preserving the separately installed OpenClaw plugin boundary. |
 
 From npm:
 
@@ -270,6 +280,7 @@ Inline reply-thread semantics:
 - Agent-authored callback buttons use `agent:` action IDs. A press is acknowledged immediately and becomes a normal agent turn with the actor, chat, source message, interaction, action ID, and callback data. The normal response edits the source message; omitted buttons clear its old buttons and returned buttons replace them. Adapter-owned command, approval, thread, and model controls use `system:` IDs and keep their deterministic handlers.
 - `thread-reply` expects `threadId` to be the child reply-thread chat id, while `to` stays the parent chat id.
 - If `threadId` is missing, `thread-reply` can use the current reply-thread context or a saved route from `thread-create` when called with the parent chat target plus `parentMessageId`.
+- Ordinary `send`, `reply`, and attachment actions inherit the current child when they target its parent; an unrelated explicit destination remains unrelated. Current supported OpenClaw hosts cannot validate and mirror an explicit child-to-parent escape reliably, so Inline rejects those flags when they request that ambiguous parent escape. Explicit unrelated destinations and explicit child targets remain supported.
 - `thread-create` creates a top-level Inline thread when called without a parent target. Use `participant`/`participants` for a private thread, or `spaceId` with `isPublic: true` for a public space thread. If `spaceId` is present and no participants are supplied, Inline defaults `thread-create` to a public space thread.
 - `thread-create` creates a real reply thread from a parent chat when `to`/`chatId`/`channelId` is supplied, or when an explicit `replyToId`/`messageId` anchor can be paired with the current channel context.
 - `forward`/`forwardMessages` forwards one or more source `messageId`/`messageIds` to a destination `to`/`chatId`/`userId`. The source can be `from`/`source`/`fromChatId`/`fromUserId`; when omitted in an Inline conversation, it defaults to the current chat.
@@ -277,8 +288,16 @@ Inline reply-thread semantics:
 - `pin`/`unpin` use `messageId` and default to the current Inline chat/thread when no target is passed; `list-pins` also defaults to the current chat/thread.
 - `invite-to-space` invites one user per call into a space using `userId`/`user`/`participant`, `email`, or `phoneNumber`; pass `role: "admin"` for admin invites or omit it for a member invite.
 - In `replyThreadMode: "auto"`, explicit user requests such as "reply in a thread" create and answer in a child reply thread automatically; the `thread-create` and `thread-reply` message-tool actions remain available for manual tool use.
-- Automatic thread creation falls back to parent-chat delivery if the reply thread cannot be created.
-- Existing route state is reused only for the same parent-message anchor. New parent-chat messages get separate reply threads; messages already inside a reply thread stay in that thread and do not create nested threads.
+- Parent typing stops before reply-thread handoff; subsequent typing, presence, and answers stay in the child. If required creation cannot be confirmed, Inline reports a short error in the parent without generating the answer there.
+- Reply threads can be created from both DM and group parent chats. A first-level DM child keeps direct-message access policy and no-mention behavior even though Inline encodes the child as a chat. Session isolation follows OpenClaw’s `session.dmScope`; use `per-channel-peer` for separate sender transcripts. The host default `main` shares DM transcripts and is unsuitable when an untrusted participant can join a DM child.
+- A message tool that creates a reply thread during a response moves subsequent visible typing, presence, and delivery to that child. The OpenClaw run and transcript keep the session in which the turn started; the next child message opens the child session. The adapter leaves final suppression to OpenClaw and does not discard a final merely because a tool sent something. Host dedupe varies by action, text, route, and streaming path; identical tool/final output can still repeat, and host streaming suppression can hide distinct text. No OpenClaw internals are patched. Any commentary already sent before creation remains in the parent.
+- Saved thread routes are scoped to the parent message. A missing current-message route never selects an unrelated active thread, and an agent without its own active route cannot inherit another agent's route.
+- Anchored creation reuses the server's existing child only for the same parent-message anchor. Inside a child, unanchored creation reuses that child; an explicit child-local anchor can create a nested Inline reply thread. Nested creation is a durable destination operation and does not move the current generated turn, so send nested content with `thread-reply` using the returned child id. This adapter only guarantees root-DM policy/session projection for first-level DM reply children; nested DM children remain an explicit advanced path.
+- A repeated unanchored `thread-create` that still targets the stale parent during the same live handoff also reuses that handoff's child.
+- During parent-to-child handoff, the exact source parent reply reference is stripped from stale-parent/implicit sends. Other references explicitly targeting the parent are rejected. Omitted destinations inherit the child, and explicitly targeted child-local numeric IDs are preserved even if they equal the parent's source ID. Numeric IDs alone cannot prove which chat an arbitrary reference came from.
+- A mentioned Inline Agent specialization is retained with the saved reply-thread route, so later child follow-ups normally do not require another Agent mention. If local route state expires or is lost, mention the Agent again.
+- Parent DM history is omitted for participants added only to its child. `inline_parent_context` also validates the trusted Inline requester against the actual parent DM peer, including explicit parent overrides. Group history and non-Inline operator tool access keep their existing bot-token access contract.
+- Per-DM reply mode and parent-history limits are honored. The existing `/threadreply` command is group-only; configure DMs through Agent Settings or config.
 - Inline current-message media is attached like native channels. Reply-thread anchor media is summarized as context and is not promoted to current-message media on every child-thread turn.
 
 You can gate action groups from config:

package/dist/account-inspect-api.js

@@ -14404,6 +14404,13 @@ function resolveControlCommandGate(params) {
     shouldBlock: params.allowTextCommands && params.hasControlCommand && !commandAuthorized
   };
 }
+function resolveUseAccessGroups(cfg) {
+  const commands = cfg.commands;
+  if (!commands || typeof commands !== "object" || Array.isArray(commands)) {
+    return true;
+  }
+  return commands.useAccessGroups !== false;
+}
 function resolveMentionGatingWithBypass(params) {
   const shouldBypassMention = params.isGroup && params.requireMention && !params.wasMentioned && !(params.hasAnyMention ?? false) && params.allowTextCommands && params.commandAuthorized && params.hasControlCommand;
   const effectiveWasMentioned = params.wasMentioned || params.implicitMention === true || shouldBypassMention;
@@ -15026,5 +15033,5 @@ export {
   inspectInlineReadOnlyAccount
 };
 
-//# debugId=EB875D24E1B044C264756E2164756E21
+//# debugId=ABA852CEA796C68F64756E2164756E21
 //# sourceMappingURL=account-inspect-api.js.map