@inline-openclaw/inline 0.0.45 → 0.0.46
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/approval-handler.runtime.js +1244 -262
- package/dist/approval-handler.runtime.js.map +8 -8
- package/dist/channel-plugin-api.js +1519 -219
- package/dist/channel-plugin-api.js.map +9 -9
- package/dist/inline/actions.d.ts.map +1 -1
- package/dist/inline/approval-handler.runtime.d.ts +1 -0
- package/dist/inline/approval-handler.runtime.d.ts.map +1 -1
- package/dist/inline/bot-avatar-tool.d.ts +12 -0
- package/dist/inline/bot-avatar-tool.d.ts.map +1 -0
- package/dist/inline/channel.d.ts.map +1 -1
- package/dist/inline/message-content.d.ts +5 -1
- package/dist/inline/message-content.d.ts.map +1 -1
- package/dist/inline/message-formatting.d.ts +18 -0
- package/dist/inline/message-formatting.d.ts.map +1 -1
- package/dist/inline/message-tools.d.ts.map +1 -1
- package/dist/inline/monitor.d.ts.map +1 -1
- package/dist/inline/parent-context-tool.d.ts.map +1 -1
- package/dist/runtime-register-api.d.ts.map +1 -1
- package/dist/runtime-register-api.js +1488 -71
- package/dist/runtime-register-api.js.map +10 -9
- package/openclaw.plugin.json +2 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,6 +20,7 @@ Supports:
|
|
|
20
20
|
Reply-thread behavior:
|
|
21
21
|
|
|
22
22
|
- Small/new parent-chat conversations stay in the parent chat by default.
|
|
23
|
+
- `replyThreadMode: "auto"` also creates a child reply thread when the triggering parent-chat message explicitly asks OpenClaw to reply in a thread.
|
|
23
24
|
- `replyThreadMode: "thread"` opts a parent chat into automatic reply-thread delivery once `replyThreadAutoCreateMinMessages` is reached; each triggering parent-chat message gets its own child reply thread.
|
|
24
25
|
- `replyThreadMode: "main"` keeps automatic replies in the parent chat, while explicit `thread-create` and `thread-reply` tools remain available.
|
|
25
26
|
- `thread-create` creates a real Inline reply thread. `thread-reply` sends into the child reply-thread chat id returned by `thread-create`.
|
|
@@ -237,6 +238,7 @@ Inline reply-thread semantics:
|
|
|
237
238
|
|
|
238
239
|
- `thread-reply` expects `threadId` to be the child reply-thread chat id, while `to` stays the parent chat id.
|
|
239
240
|
- `thread-create` creates a real reply thread from a parent chat and optional `replyToId` anchor.
|
|
241
|
+
- 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.
|
|
240
242
|
- Automatic thread creation falls back to parent-chat delivery if the reply thread cannot be created.
|
|
241
243
|
- 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.
|
|
242
244
|
- 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.
|