@inline-openclaw/inline 0.0.38 → 0.0.40

package/README.md

@@ -12,26 +12,23 @@ Supports:
 - Inline DMs (`ChatType=direct`)
 - Inline chats as conversations (`ChatType=group`)
 - Message replies: OpenClaw `replyToId` is mapped to Inline `replyToMsgId` (message id).
-- Optional Inline reply threads: enable `channels.inline.capabilities.replyThreads: true` to expose Inline reply-thread chats as OpenClaw threads.
+- Inline reply threads: tools can create and reply in real Inline reply-thread chats.
 - Inline media upload/send for images, videos, and documents from `mediaUrl` payloads.
 - Emoji reactions via message tool actions (`react`, `reactions`).
 - Reaction events on bot-authored messages are surfaced back to the agent as inbound context.
 
-By default, Inline reply threads stay off to preserve the old compatibility behavior. When disabled:
+Reply-thread behavior:
 
-- `replyToId` remains an Inline message reply only.
-- `thread-reply` keeps the legacy compatibility path.
-- `thread-create` keeps the legacy chat-creation alias behavior.
-
-When enabled:
-
-- inbound reply-thread messages use the parent chat as the base conversation target and the child reply-thread chat id as `MessageThreadId`
-- outbound `thread-reply` sends into the child reply-thread chat
-- `thread-create` creates a real Inline reply thread instead of a plain chat alias
+- Small/new parent-chat conversations stay in the parent chat by default.
+- `replyThreadMode: "thread"` opts a parent chat into automatic reply-thread delivery once `replyThreadAutoCreateMinMessages` is reached.
+- `replyThreadMode: "main"` keeps automatic replies in the parent chat, while explicit `thread-create` and `thread-reply` tools remain available.
+- `thread-create` creates a real Inline reply thread. `thread-reply` sends into the child reply-thread chat id returned by `thread-create`.
+- Inbound reply-thread messages use the parent chat as the base conversation target and the child reply-thread chat id as `MessageThreadId`.
+- Bot-participated reply threads can continue without an explicit bot mention by default, matching Slack-style thread behavior.
 
 ## Install
 
-Requires OpenClaw `2026.5.18` or newer.
+Requires OpenClaw `2026.5.28` or newer.
 
 From npm (once published):
 
@@ -136,10 +133,12 @@ channels:
     groupPolicy: "allowlist" # allowlist|open|disabled
     groupAllowFrom:
       - "inline:123" # or "user:123" or just "123"
-    capabilities:
-      replyThreads: false # optional, default false; enable Inline reply-thread support
     requireMention: true # optional: default is false
     replyToBotWithoutMention: true # if true, replies to bot messages can bypass mention requirement
+    replyThreadMode: "auto" # auto|thread|main; thread auto-routes long parent-chat replies into one reply thread
+    replyThreadAutoCreateMinMessages: 50 # optional, default 50; avoids creating reply threads for small/new chats
+    replyThreadRequireExplicitMention: false # optional, default false; bot-participated reply threads continue without @mention
+    replyThreadParentHistoryLimit: 10 # optional, default 10; set 0 to disable parent-chat context before the anchor
 
     # Inbound context history (used to build richer thread context for the agent):
     historyLimit: 50      # group chats
@@ -159,6 +158,8 @@ channels:
     groups:
       "88":
         requireMention: false
+        replyThreadRequireExplicitMention: true
+        replyThreadParentHistoryLimit: 2
         allowFrom:
           - "42"
         tools:
@@ -173,21 +174,21 @@ Per-account override:
 ```yaml
 channels:
   inline:
-    capabilities:
-      replyThreads: false
     accounts:
       work:
         token: "<INLINE_BOT_TOKEN>"
         defaultTo: "user:123"
-        capabilities:
-          replyThreads: true
+        replyThreadMode: "main"
 ```
 
 Reply behavior summary:
 
 - `replyToId` is always an Inline message id.
 - Inline reply threads are separate and use OpenClaw `threadId`.
-- Keep `replyThreads` off if you only want classic message replies.
+- Use `replyThreadMode: "main"` if you only want automatic parent-chat replies to stay in the parent chat.
+- Use `replyThreadMode: "thread"` plus `replyThreadAutoCreateMinMessages` when long parent-chat conversations should move into one stable reply thread.
+- Bot-participated reply threads continue without `@bot` by default, including from persisted recent participation state. Set `replyThreadRequireExplicitMention: true` if a chat should require `@bot` on every reply-thread message.
+- `replyThreadParentHistoryLimit` defaults to `10`, so reply-thread turns include nearby parent-chat context before the anchor. Set it to `0` only when a chat should stay strictly thread-local.
 
 If you set `dmPolicy: "open"`, set `allowFrom: ["*"]`.
 
@@ -203,7 +204,7 @@ For `message send`/plugin outbound sends:
 
 - Use `openclaw message send --channel inline --target chat:<id> --message "..."`.
 - If `channels.inline.defaultTo` is set, OpenClaw uses it when no explicit target is supplied. Named accounts can override it with `channels.inline.accounts.<account>.defaultTo`.
-- Some OpenClaw 2026.5.18 CLI help text lists only built-in channel ids, but installed plugin channel ids such as `inline` are accepted.
+- Some OpenClaw CLI help text lists only built-in channel ids, but installed plugin channel ids such as `inline` are accepted.
 - `chat:<id>` targets a chat id.
 - `user:<id>` targets a user id (DM peer).
 - `inline:user:<id>` and `inline:chat:<id>` are accepted and normalized.
@@ -231,11 +232,13 @@ Direct DM sends can also target `user:<id>`.
 - Pins: `pin`, `unpin`, `list-pins`
 - Space permissions: `permissions`
 
-Inline reply-thread semantics are behind `channels.inline.capabilities.replyThreads`:
+Inline reply-thread semantics:
 
-- disabled: `thread-reply` behaves like the old compatibility reply path
-- enabled: `thread-reply` expects `threadId` to be the child reply-thread chat id, while `to` stays the parent chat id
-- enabled: `thread-create` creates a real reply thread from a parent chat and optional `replyToId` anchor
+- `thread-reply` expects `threadId` to be the child reply-thread chat id, while `to` stays the parent chat id.
+- `thread-create` creates a real reply thread from a parent chat and optional `replyToId` anchor.
+- Automatic thread creation falls back to parent-chat delivery if the reply thread cannot be created.
+- Existing route state is reused so long conversations stay in one reply thread instead of creating one thread per message.
+- If the current reply-thread message has no direct media, OpenClaw can inherit the anchor message media so image/file-only thread starters remain visible to the agent.
 
 You can gate action groups from config:
 
@@ -263,7 +266,15 @@ Named accounts can override the same `reactionNotifications` mode and `reactionA
 
 ## Extra Agent Tools
 
-The plugin also registers a dedicated `inline_members` tool for space-member discovery outside the `message` action surface.
+The plugin also registers dedicated tools outside the `message` action surface.
+
+`inline_parent_context` fetches more parent-chat history for the current Inline reply-thread session when the automatic context window is not enough.
+
+- Defaults to the current reply thread when invoked from one
+- Optional inputs: `threadId`, `parentChatId`, `parentMessageId`, `beforeMessageId`, `limit`, `includeAnchor`, `accountId`
+- Returned messages are ordered oldest to newest and include media/entity summaries
+
+`inline_members` handles space-member discovery:
 
 - Required input: `spaceId`
 - Optional filters: `query`, `userId`, `limit`, `accountId`

package/dist/account-inspect-api.js

@@ -14550,10 +14550,15 @@ var InlineActionsSchema = exports_external.object({
 var InlineCapabilitiesSchema = exports_external.object({
   replyThreads: exports_external.boolean().optional()
 }).strict();
+var InlineReplyThreadModeSchema = exports_external.enum(["auto", "thread", "main"]);
 var InlineTargetSchema = exports_external.union([exports_external.string(), exports_external.number()]);
 var InlineAllowEntrySchema = exports_external.union([exports_external.string(), exports_external.number()]);
 var InlineGroupSchema = exports_external.object({
   requireMention: exports_external.boolean().optional(),
+  replyThreadMode: InlineReplyThreadModeSchema.optional(),
+  replyThreadAutoCreateMinMessages: exports_external.number().int().min(0).optional(),
+  replyThreadRequireExplicitMention: exports_external.boolean().optional(),
+  replyThreadParentHistoryLimit: exports_external.number().int().min(0).optional(),
   allowFrom: exports_external.array(InlineAllowEntrySchema).optional(),
   systemPrompt: exports_external.string().optional(),
   tools: ToolPolicySchema.optional(),
@@ -14593,6 +14598,7 @@ var InlineStreamingSchema = exports_external.union([
       label: exports_external.union([exports_external.string(), exports_external.literal(false)]).optional(),
       labels: exports_external.array(exports_external.string()).optional(),
       maxLines: exports_external.number().int().positive().optional(),
+      maxLineChars: exports_external.number().int().positive().optional(),
       render: exports_external.enum(["text", "rich"]).optional(),
       toolProgress: exports_external.boolean().optional(),
       commandText: InlineStreamingCommandTextSchema.optional()
@@ -14620,6 +14626,7 @@ var InlineRuntimeStreamingSchema = exports_external.union([
       label: exports_external.union([exports_external.string(), exports_external.literal(false)]).optional(),
       labels: exports_external.array(exports_external.string()).optional(),
       maxLines: exports_external.number().int().positive().optional(),
+      maxLineChars: exports_external.number().int().positive().optional(),
       render: exports_external.enum(["text", "rich"]).optional(),
       toolProgress: exports_external.boolean().optional(),
       commandText: InlineStreamingCommandTextSchema.optional()
@@ -14645,6 +14652,10 @@ var InlineAccountSchemaBase = exports_external.object({
   groupPolicy: GroupPolicySchema.optional().default("allowlist"),
   groups: exports_external.record(exports_external.string(), InlineGroupSchema.optional()).optional(),
   requireMention: exports_external.boolean().optional(),
+  replyThreadMode: InlineReplyThreadModeSchema.optional(),
+  replyThreadAutoCreateMinMessages: exports_external.number().int().min(0).optional(),
+  replyThreadRequireExplicitMention: exports_external.boolean().optional(),
+  replyThreadParentHistoryLimit: exports_external.number().int().min(0).optional(),
   replyToBotWithoutMention: exports_external.boolean().optional(),
   historyLimit: exports_external.number().int().min(0).optional(),
   dmHistoryLimit: exports_external.number().int().min(0).optional(),
@@ -14916,9 +14927,7 @@ function inspectInlineAccount(params) {
   }
   const tokenFile = account.tokenFile?.trim() ?? "";
   if (tokenFile) {
-    const token = tryReadSecretFileSync(tokenFile, "Inline bot token", {
-      rejectSymlink: true
-    }) ?? "";
+    const token = tryReadInlineTokenFile(tokenFile);
     return {
       ...account,
       token: token || null,
@@ -14978,13 +14987,31 @@ async function resolveInlineToken(account) {
     }
     throw new Error("Inline token missing (set channels.inline.token, channels.inline.tokenFile, INLINE_TOKEN, or INLINE_BOT_TOKEN)");
   }
-  const token = tryReadSecretFileSync(tokenFile, "Inline bot token", {
-    rejectSymlink: true
-  });
+  const token = readInlineTokenFile(tokenFile);
   if (!token)
     throw new Error(`Inline tokenFile is empty or unreadable: ${tokenFile}`);
   return token;
 }
+function tryReadInlineTokenFile(tokenFile) {
+  try {
+    return tryReadSecretFileSync(tokenFile, "Inline bot token", {
+      rejectSymlink: true
+    }) ?? "";
+  } catch {
+    return "";
+  }
+}
+function readInlineTokenFile(tokenFile) {
+  try {
+    return tryReadSecretFileSync(tokenFile, "Inline bot token", {
+      rejectSymlink: true
+    }) ?? "";
+  } catch (error51) {
+    throw new Error(`Inline tokenFile is empty or unreadable: ${tokenFile}`, {
+      cause: error51
+    });
+  }
+}
 
 // src/account-inspect-api.ts
 function inspectInlineReadOnlyAccount(cfg, accountId) {
@@ -14994,5 +15021,5 @@ export {
   inspectInlineReadOnlyAccount
 };
 
-//# debugId=FF5F089AF31525E364756E2164756E21
+//# debugId=037AA7E34FED47C364756E2164756E21
 //# sourceMappingURL=account-inspect-api.js.map