@inline-openclaw/inline 0.0.58 → 0.0.60

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 CHANGED
@@ -40,12 +40,12 @@ Requires OpenClaw `2026.6.11` or newer.
40
40
 
41
41
  | Plugin version | OpenClaw host | Inline realtime SDK | Status | Notes |
42
42
  | --- | --- | --- | --- | --- |
43
- | `0.0.58` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.15` | Current | Promotes the stable realtime v3 SDK; hardens terminal authentication, model settings, recovered replies and joins, rich streaming delivery, and monitor failure reporting. |
43
+ | `0.0.60` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.16` | Current | Uses the plugin index's supported force-install path for exact updates on current OpenClaw hosts. |
44
+ | `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. |
45
+ | `0.0.58` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.15` | Previous | Promotes the stable realtime v3 SDK; hardens terminal authentication, model settings, recovered replies and joins, rich streaming delivery, and monitor failure reporting. |
44
46
  | `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. |
45
47
  | `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. |
46
48
  | `0.0.55` | `>=2026.6.11 || >=2026.7.1-0` | `0.0.14` | Stable | Enforces empty-payload nudges, canonical visible-text sanitizing, hard access-before-mention policy, explicit auto-threading, and clearer formatting guidance; explicitly admits npm's `2026.7.1-2` stable host version. |
47
- | `0.0.54` | `>=2026.6.11` | `0.0.13` | Stable | Keeps recovered WebSocket and best-effort cursor warnings out of healthy channel status; validated through OpenClaw `2026.7.1-2`. |
48
- | `0.0.53` | `>=2026.6.11` | `0.0.13` | Stable | Clears recovered Inline WebSocket errors from channel status after reconnect. |
49
49
 
50
50
  From npm:
51
51
 
@@ -56,8 +56,7 @@ openclaw plugins install @inline-openclaw/inline
56
56
  If the plugin is already installed, update in place:
57
57
 
58
58
  ```sh
59
- openclaw config set plugins.installs.inline.spec '"@inline-openclaw/inline@latest"'
60
- openclaw plugins update inline
59
+ openclaw plugins install --force @inline-openclaw/inline@latest
61
60
  openclaw gateway restart
62
61
  openclaw plugins list
63
62
  openclaw channels status
@@ -268,6 +267,7 @@ Inline reply-thread semantics:
268
267
  - `channel-edit` can rename (`title`/`name`/`threadName`), update `emoji`, and change space-thread visibility with `isPublic` or `visibility: "public"|"private"`. Private visibility changes require `participant`/`participants`.
269
268
  - `upload-file` is the native OpenClaw alias for `sendAttachment`; use `filePath`, `path`, `media`, `mediaUrl`, or `url` for the file/media source.
270
269
  - Inline `buttons` rows support `callback_data` for callbacks and `copy_text`/`copyText` for client-side copy buttons. JSON `callback_data` can include `callbackToast` or `toast` for an immediate short acknowledgement when pressed.
270
+ - 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.
271
271
  - `thread-reply` expects `threadId` to be the child reply-thread chat id, while `to` stays the parent chat id.
272
272
  - 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`.
273
273
  - `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.