clawgram 2.19.1 → 2.19.4

package/dist/channel.js

@@ -3,7 +3,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.createChannelPlugin = void 0;
+exports.createChannelPlugin = exports.CORE_ACTION_SYNONYMS = void 0;
 const core_1 = require("openclaw/plugin-sdk/core");
 const node_os_1 = __importDefault(require("node:os"));
 const node_path_1 = __importDefault(require("node:path"));
@@ -177,8 +177,48 @@ function readAccountManageChats(account) {
     const entries = Array.isArray(raw) ? raw : [raw];
     return entries.map((entry) => String(entry).trim()).filter(Boolean);
 }
+/**
+ * Core's own name for a clawgram action, and the only thing that makes the
+ * action reachable from the agent's `message` tool.
+ *
+ * Core keys its target policy by `CHANNEL_MESSAGE_ACTION_NAMES`, and an action
+ * outside that vocabulary is simultaneously "requires a target" and "does not
+ * accept a target" — there is no call that satisfies both. Declaring `chatId`
+ * through `messageActionTargetAliases` looks like the fix and is not: core
+ * resolves the channel with `getBootstrapChannelPlugin`, which only knows
+ * bundled channels, so a plugin channel's declaration is never read. Measured
+ * on 2026-08-30 — `thread-list` reached `handleAction` and `topics` did not,
+ * from the same caller, on the same chat.
+ *
+ * Every name on the right maps to core target mode `"none"` except
+ * `channel-info`, which is `"to"` and therefore arrives with the chat in
+ * `params.to` — a spelling all of these parsers already accept.
+ */
+exports.CORE_ACTION_SYNONYMS = {
+    "thread-list": "topics",
+    "channel-list": "dialogs",
+    "channel-info": "chatInfo",
+    "member-info": "participants",
+    "download-file": "fetch-media",
+    // Chat management. `kick` was already accepted; the rest were advertised
+    // under names core does not know and were therefore never callable from the
+    // tool at all — 2.19.4 gives them core's nearest name. `transferOwnership`
+    // and `inviteLink` have no counterpart in that vocabulary and stay
+    // gateway-only, as does `joins`.
+    "channel-create": "createGroup",
+    addParticipant: "addMembers",
+    kick: "removeMember",
+    "role-add": "promoteAdmin",
+    "role-remove": "demoteAdmin",
+};
 /** Canonical management action for every accepted spelling. */
 const MANAGE_ACTION_ALIASES = {
+    // Core's spellings first — these are the only ones the agent's tool can
+    // reach; see CORE_ACTION_SYNONYMS.
+    "channel-create": "createGroup",
+    addParticipant: "addMembers",
+    "role-add": "promoteAdmin",
+    "role-remove": "demoteAdmin",
     createGroup: "createGroup",
     createChat: "createGroup",
     "create-group": "createGroup",
@@ -405,11 +445,12 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 "Explicit targets may be @username, numeric Telegram user id, phone/contact resolvable by Telegram, group chat ids, or clawgram:<target>.",
                 "For Telegram forum topics, send to the group chat id and pass the topic id separately as `threadId`.",
                 "Use the `react` action to acknowledge a message with an emoji instead of sending a reply; pass an empty `emoji` (or `remove: true`) to take the reaction back.",
-                "Use the `chatInfo` action to learn what a chat is — title, type, member count, description, pinned message — instead of guessing from its id.",
-                "Use the `topics` action to list a forum's topics by name (optional `query` narrows by title); that is where a `threadId` comes from when someone names a topic instead of quoting a message in it.",
+                "Use the `channel-info` action to learn what a chat is — title, type, member count, description, pinned message — instead of guessing from its id. Name the chat with `chatId` and do not pass `target`: core refuses it for this action, and the descriptive spelling `chatInfo` is not callable from this tool at all.",
+                "Use the `thread-list` action to list a forum's topics by name (optional `query` narrows by title); that is where a `threadId` comes from when someone names a topic instead of quoting a message in it. Name the chat with `chatId` and do not pass `target` — core refuses it for this action. `topics` is the same call under a name core does not know, and is only reachable through the gateway RPC.",
                 "Pass that `threadId` to `read` as well: without it a forum read returns every topic interleaved rather than the one that was asked about.",
-                "Use the `download-file` action (or its alias `fetch-media`) to fetch the attachment on a message `read` reported. Name the chat with `chatId` and the message with `messageId`; do not pass `target` — core refuses it for this action: `mode: \"read\"` returns a description of an image or a transcript of a voice note, `\"file\"` returns a path to reuse, `\"both\"` (default) returns both. `read` only says an attachment exists; this is what brings it.",
-                "Use the `dialogs` action to find out which group chats this account is actually in — including ones nobody has configured yet. It reports id, title and type only, never direct chats, and only when the account enables `discoverChats`.",
+                "Use the `download-file` action to fetch the attachment on a message `read` reported. Name the chat with `chatId` and the message with `messageId`; do not pass `target` — core refuses it for this action: `mode: \"read\"` returns a description of an image or a transcript of a voice note, `\"file\"` returns a path to reuse, `\"both\"` (default) returns both. `read` only says an attachment exists; this is what brings it.",
+                "Use the `channel-list` action to find out which group chats this account is actually in — including ones nobody has configured yet. It reports id, title and type only, never direct chats, and only when the account enables `discoverChats`.",
+                "Use `member-info` with a `chatId` to list who is in a chat, and `kick` with a `chatId` and `userId` to remove someone from a managed chat. The rest of the chat-management family and `joins` have no name core knows, so they are reachable only through the gateway RPC, not from this tool.",
                 "Use `createGroup` (title, optional about, optional users) to create a new Telegram supergroup; `addMembers`/`removeMember` change who is in a managed chat, `promoteAdmin`/`demoteAdmin` grant or revoke admin rights, `transferOwnership` hands the chat over, `inviteLink` issues an invite link for people Telegram refused to add directly.",
             ],
             messageToolCapabilities: () => [
@@ -417,10 +458,10 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 "clawgram can send text messages to direct chats and groups from the connected personal account.",
                 "clawgram supports Telegram forum topics via the `threadId` parameter on group sends.",
                 "clawgram can add and clear emoji reactions on messages. A plain Telegram account holds one reaction per message, so a new emoji replaces the previous one.",
-                "clawgram can describe a chat via `chatInfo`: title, type (direct/group/supergroup/channel), member count, description, whether it is a forum, and the pinned message id.",
-                "clawgram can list the topics of a forum supergroup via `topics`: id, title, last message, and whether a topic is closed, hidden or pinned.",
-                "clawgram can fetch the attachment on any message inside its read scope via `fetch-media`: images come back described, voice notes transcribed, and either can be returned as a file path for reuse.",
-                "clawgram can list the group chats the account belongs to via `dialogs`, when the account sets discoverChats. Metadata only, no direct chats — it answers \"where am I\", not \"what was said\".",
+                "clawgram can describe a chat via `channel-info`: title, type (direct/group/supergroup/channel), member count, description, whether it is a forum, and the pinned message id.",
+                "clawgram can list the topics of a forum supergroup via `thread-list`: id, title, last message, and whether a topic is closed, hidden or pinned.",
+                "clawgram can fetch the attachment on any message inside its read scope via `download-file`: images come back described, voice notes transcribed, and either can be returned as a file path for reuse.",
+                "clawgram can list the group chats the account belongs to via `channel-list`, when the account sets discoverChats. Metadata only, no direct chats — it answers \"where am I\", not \"what was said\".",
                 "clawgram can manage chats where the account's manageChats config allows it: create supergroups, add and remove members, promote and demote admins, transfer ownership, and export invite links.",
             ],
         },
@@ -1387,29 +1428,40 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                     // Leaving it out does not degrade to a text send: the agent simply
                     // never sees a way to send the file, announces it in words, and the
                     // file stays on disk. That is exactly what happened on 2026-08-07.
+                    // Only names core already knows. An action outside
+                    // `CHANNEL_MESSAGE_ACTION_NAMES` cannot be called from the agent's
+                    // `message` tool at all — it is simultaneously "requires a target"
+                    // and "does not accept a target" — so advertising one is handing the
+                    // agent a trap. It cost a broken reply in a live chat on 2026-08-31:
+                    // the agent picked the descriptive `chatInfo`, got both halves of
+                    // the contradiction, and the turn ended in `✉️ Message failed`.
+                    //
+                    // The descriptive spellings (`topics`, `dialogs`, `chatInfo`,
+                    // `participants`, `joins`, `fetch-media`, the manage family) still
+                    // work in `handleAction`, so gateway RPC and existing skills keep
+                    // calling them — RPC does not consult this list. They are simply not
+                    // offered to the agent, which has no way to use them.
+                    //
+                    // `upload-file` is what core dispatches when an agent has an
+                    // attachment to deliver — a generated image is the common case.
+                    // Leaving it out does not degrade to a text send: the agent simply
+                    // never sees a way to send the file, announces it in words, and the
+                    // file stays on disk. That is exactly what happened on 2026-08-07.
+                    //
+                    // `kick` is core's name for `removeMember`; the rest of the manage
+                    // family has no core equivalent and stays gateway-only until it gets
+                    // one. `joins` likewise.
                     actions: [
-                        "send", "read", "participants", "joins", "react", "chatInfo", "topics", "dialogs", "upload-file",
+                        "send", "read", "react", "upload-file",
                         // Reading an attachment that is already in a chat. `read` reports
                         // that a photo exists; this is what turns it into something the
                         // agent can look at or pass on.
-                        //
-                        // Two names on purpose. `download-file` is core's own vocabulary
-                        // (`CHANNEL_MESSAGE_ACTION_NAMES`), and core's target policy is
-                        // keyed by that vocabulary: an action it does not know is both
-                        // "requires a target" (`MESSAGE_ACTION_TARGET_MODE[action] !==
-                        // "none"` is true for `undefined`) and "does not accept a target"
-                        // (the same lookup defaults to `"none"` when a target is passed).
-                        // That contradiction is unresolvable from the caller's side —
-                        // measured on 2026-08-24, when the agent tried every combination
-                        // and got one of the two errors each time. `download-file` is
-                        // mapped to `"none"`, so it has no such contradiction;
-                        // `fetch-media` stays as the descriptive name and is made usable
-                        // by the alias declaration below.
-                        "fetch-media", "download-file",
+                        "download-file",
+                        // Core's names for the chat-shaped reads — see CORE_ACTION_SYNONYMS.
+                        "thread-list", "channel-list", "channel-info", "member-info",
                         // Chat management (2.12.0) — gated by the account's manageChats
                         // scope; without it every one of these is refused.
-                        "createGroup", "addMembers", "removeMember",
-                        "promoteAdmin", "demoteAdmin", "transferOwnership", "inviteLink",
+                        "channel-create", "addParticipant", "kick", "role-add", "role-remove",
                     ],
                     capabilities: [],
                     mediaSourceParams: {
@@ -1423,6 +1475,17 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
             // reaches `handleAction`. The chat is named by `chatId` rather than
             // `target` because core reserves `target` for actions in its own
             // vocabulary and throws on it for everything else.
+            //
+            // This declaration alone does not rescue an action, and 2.19.1 read too
+            // much into it. Core resolves the channel through
+            // `getBootstrapChannelPlugin`, which only ever returns a *bundled*
+            // channel; for a plugin channel the lookup misses and the declaration is
+            // never consulted. Measured on the live server on 2026-08-30: `topics`
+            // was refused for `target`, `chatId`, `groupId` and the prefixed form
+            // alike even with `chatId` declared here. What actually carried
+            // `fetch-media` through was its second name, `download-file` — see
+            // CORE_ACTION_SYNONYMS. This stays because it costs nothing and is
+            // correct the day core consults plugin channels too.
             messageActionTargetAliases: {
                 "fetch-media": { aliases: ["chatId"] },
                 "download-file": { aliases: ["chatId"] },
@@ -1639,7 +1702,7 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 // Membership is a read, so the same `readChats` scope that gates history
                 // gates it too: this cannot become a way to enumerate chats the account
                 // was never allowed to read.
-                if (action === "participants" || action === "members") {
+                if (action === "participants" || action === "members" || action === "member-info") {
                     const participantsParams = (0, history_1.parseListParticipantsParams)(params);
                     const participantsAccountId = resolveRuntimeAccountId(cfg, accountId);
                     if (!participantsAccountId) {
@@ -1679,7 +1742,7 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 // id could only be lifted off an inbound message — so a topic nobody had
                 // written in yet was unreachable, and one named in words was unfindable.
                 // Titles say what a chat is working on, so the read scope gates them.
-                if (action === "topics" || action === "forumTopics") {
+                if (action === "topics" || action === "forumTopics" || action === "thread-list") {
                     const topicsParams = (0, topics_1.parseTopicsParams)(params);
                     const topicsAccountId = resolveRuntimeAccountId(cfg, accountId);
                     if (!topicsAccountId) {
@@ -1716,7 +1779,7 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 // Which chats this account is in. Not gated by `readChats` — the whole
                 // point is to find chats that are not in it yet — so it has a gate of
                 // its own, is metadata only, and never reports direct chats.
-                if (action === "dialogs" || action === "chats") {
+                if (action === "dialogs" || action === "chats" || action === "channel-list") {
                     const dialogsParams = (0, dialogs_1.parseDialogsParams)(params);
                     const dialogsAccountId = resolveRuntimeAccountId(cfg, accountId);
                     if (!dialogsAccountId) {
@@ -1776,7 +1839,7 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 // Describing a chat is a read, so the same `readChats` scope that gates
                 // history gates it too — this must not become a way to learn the title
                 // and size of a chat the account was never allowed to read.
-                if (action === "chatInfo" || action === "getChatInfo"
+                if (action === "chatInfo" || action === "getChatInfo" || action === "channel-info"
                     || action === "chatMetadata" || action === "getChatMetadata") {
                     const chatInfoParams = (0, chat_info_1.parseChatInfoParams)(params, toolContext);
                     const chatInfoAccountId = resolveRuntimeAccountId(cfg, accountId);

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "clawgram",
   "name": "Clawgram",
   "description": "Clawgram — personal Telegram (MTProto userbot) channel for OpenClaw. Your AI assistant reads and responds as you.",
-  "version": "2.19.1",
+  "version": "2.19.4",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawgram",
-  "version": "2.19.1",
+  "version": "2.19.4",
   "description": "Clawgram — personal Telegram (MTProto userbot) channel for OpenClaw. Your AI assistant reads and responds as you.",
   "main": "./dist/index.js",
   "scripts": {