@ycodium-ai/plugin-im 0.2.3244 → 0.2.3252

package/README.md

@@ -138,12 +138,12 @@ messages → API receive”. Each column is validated, and a row with problems d
 connect. Streaming replies are off by default (the app's passive stream reply has not
 been verified on a real WeCom client). With it on, WeCom refreshes the reply as the agent
 writes; if the client never refreshes the stream, the final reply is sent as text.
+Team goals finish the initial placeholder when accepted; the lead's replies arrive as
+new messages.
 
-Known limits with Streaming replies on: the "Got it, working on it" placeholder is
-not closed when a turn cannot start because the project has no default model, or
-when handling the message throws; and a message queued for a team goal has its
-placeholder closed right away, so it gets no 5-second fallback confirmation. The
-reply itself still arrives as text in all three cases.
+If a message cannot be saved before dispatch, the bot replies that there is no need to
+send it again and that it will be handled automatically the next time the machine starts
+(a WeCom App streaming placeholder is finished first).
 
 The default is one message per finished turn. A single turn can produce dozens
 of assistant messages, mostly commentary between tool calls.
@@ -260,14 +260,18 @@ is sent to the chat. `chat_type` (1 single, 2 group) comes from the last inbound
 conversation and is left out when none has arrived since the plugin started, as plain text does.
 A picture goes as `image` only when it is PNG, JPEG or GIF within 10 MB (`imageMimeTypes`).
 
-Chat commands: `/stop`, `/continue`, `/status`, `/new`, `/sessions`, `/resume`, `/model`,
+Chat commands: `/stop`, `/continue`, `/status`, `/version`, `/new`, `/sessions`, `/resume`, `/history [count]`, `/model`,
 `/plan`, `/repo`, `/group`, `/team`, `/thread`, `/help`, `/panel`. In a chat with no project
-`/sessions`, `/resume` and the team commands answer with the project picker. `/sessions` and `/resume` only list and
+`/sessions`, `/resume` and the team commands answer with the project picker. `/version` still answers. `/sessions` and `/resume` only list and
 switch threads this plugin opened, since the host lets a plugin send only into
 its own threads. `/continue` calls `threads.turnQueue.resume` for the chat's thread
 when its queue is paused (a `/stop` or a failure pauses it), which is how WeCom
 resumes a paused queue from the chat; it is not `/resume`, which already switches threads.
 
+`/history [count]` previews the current session's recent user and assistant messages in private chats only (default 3, maximum 5), oldest first. It does not start a turn or change the session. Images and files appear as placeholders; long text is split for the platform, with a notice when the preview text is incomplete. Type the command in the chat; panels and native command menus do not list it. With the reply language set to Chinese, `会话历史 [数量]` works too.
+
+`/version` answers with one line, the plugin name and its version. It takes no arguments; if anything follows it, the reply is a usage reminder. It works in private chats and groups, does not read the session, and does not start a turn. Type it; panels and native command menus do not list it. There is no Chinese alias.
+
 On Lark, Telegram, and the WeCom smart bot, `/panel` sends a command panel, and `/help` stays text and ends with a pointer to it. WeCom App does not implement the panel surface, so `/panel` answers with the text list and `/help` does not mention `/panel`. Lark cards and Telegram inline keyboards show all command buttons. The WeCom smart bot uses a template card from `src/wecomPanel.ts`; its main menu is limited to six buttons. Commands that do not fit are listed in `/help` and can be typed into the chat. Commands that take an argument (a thread, a project, a model) open a second view on the same message with a Back button. These lists let you reach every option by paging: Lark and Telegram show eight items per page, and WeCom shows three, leaving room for Back, Previous, and Next. A tap on the WeCom card updates that same card; when the update cannot be applied, `src/panelController.ts` posts a new card and the old one stops accepting taps. A busy placeholder is not drawn on that card: it stays as it is until the next interactive view. Telegram buttons carry only a short `pn:<version>:<index>` token (`callback_data` is capped at 64 bytes); the action stays in memory and a tap on an older keyboard version counts as expired. Each card keeps its own view stack in memory (`src/panelController.ts`), so after a restart an old card only answers that it has expired. A tap runs the same handler as the typed command and waits in the same per-chat queue as typed messages. Another platform opts in by implementing the optional `panel` surface on its adapter (`src/adapter.ts`).
 
 `/team` uses the chat's selected project. It reads the roster from the `team` plugin and

package/assets/ui.js

@@ -61,7 +61,7 @@ var Vn=window.__ycodiumPluginHost.react;var{Activity:Zn,Children:et,Component:nt
   color: inherit;
   font: inherit;
   text-align: start;
-  cursor: pointer;
+  cursor: var(--control-cursor, pointer);
 }
 .im-settings .im-status {
   display: inline-flex;