@ycodium-ai/plugin-im 0.2.3265 → 0.2.3306

package/README.md

@@ -165,18 +165,20 @@ per-message text. How depends on the platform:
 
 An adapter opts in with the optional `turnCards` surface (`src/adapter.ts`).
 Approval messages are posted for every pending request on platforms with
-buttons and replaced with a settled notice when the request is answered, here or
+buttons and settled when the request is answered, here or
 elsewhere (`thread.request-resolved`); WeCom, which answers by number, posts only
 the first and just stops accepting its number. Each bot's **More settings** includes
 an approval timeout in minutes: the default is 60, and 0 turns automatic denial off
 (integers from 0 to 1440). Unanswered approvals are denied automatically at the
-deadline. Lark and Telegram replace the approval card or message with a notice
+deadline. Lark and Telegram show a notice on the approval card or message
 stating the number of minutes; platforms without editable approval cards, and
 failed card updates, send the same notice as chat text. The timeout continues from
 the approval's creation time after a restart, including immediately denying
 overdue requests. Changing the setting recalculates pending deadlines immediately;
 setting it to 0 cancels them. Questions have no timeout.
 
+Once a request has been answered or has timed out, Lark cards and Telegram messages show the result first, followed by the original approval content; timeout notices sent as chat text include a short excerpt of that content.
+
 On a platform whose `turnCards` set
 `rotatesOnInteraction` (Lark: patching a card does not move it), an approval or
 question that someone answered seals the open reply card as "continues below" and the
@@ -195,7 +197,9 @@ optional `choiceCards` surface (`ImChoiceCard`, `src/adapter.ts`): Lark patches
 card, Telegram edits a message and its inline keyboard. A request is posted on
 `thread.user-input-pending` (read with `listPendingUserInputs`), one card per
 question, and answered through `ctx.threads.userInput.respond` once every question
-has an answer; a free-form answer is the next ordinary message in the chat, and
+has an answer; a free-form answer is the next ordinary message in the chat (its
+attachments, and any waiting ones, go along in `attachmentsByQuestionId`; an
+option-only question leaves them waiting for the next message), and
 `thread.request-resolved` freezes the cards of a question answered elsewhere or
 closed unanswered. WeCom writes the options as numbers and the
 reply is parsed in `src/questionCards.ts`. A message that lands behind a running
@@ -272,7 +276,7 @@ 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`, `/compact`, `/status`, `/version`, `/new`, `/sessions`, `/archived`, `/resume`, `/history [count]`, `/model`,
+Chat commands: `/stop`, `/steer <instruction>`, `/batch`, `/send`, `/cancel`, `/continue`, `/compact`, `/status`, `/version`, `/new`, `/sessions`, `/archived`, `/resume`, `/history [count]`, `/model`,
 `/reasoning`, `/permission`, `/plan`, `/repo`, `/group`, `/team`, `/thread`, `/help`, `/panel`. In a chat with no project
 `/sessions`, `/resume` and the team commands answer with the project picker. `/version` and `/archived` still answer. `/sessions` and `/resume` only list and
 switch threads this plugin opened, since the host lets a plugin send only into
@@ -280,6 +284,10 @@ its own threads. `/continue` calls `threads.turnQueue.resume` for the chat's thr
 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.
 
+`/steer <instruction>` adds text to the turn running in this chat, regardless of the bot's queue mode. It preserves multiple lines and rejects images and files. While the host waits for an answer or approval it is refused and not kept; the user handles that first or sends `/stop`, then sends it again. The waiting check reads the host execution view, not the plugin interaction records. With no bound session or running turn, it replies without starting work. If the turn ends just as the host accepts the instruction, it waits as the next message. Files sent on their own before it are not attached; they stay for the next ordinary message. Type it; panels and native command menus do not list it. There is no Chinese alias.
+
+`/batch` collects up to 10 text messages in a private chat without replying or starting a turn. `/send` submits them together as one input; a failed submission keeps them for retry. `/cancel` discards them. Repeating `/batch` reports progress, and a full batch never submits automatically. Attachments are refused without counting them; other slash commands are blocked until `/send` or `/cancel`. Starting a batch is refused in a group, before a project is picked, while the chat targets a team, or while the host reports a running turn or pending answer or approval. If the project has been archived or deleted when `/send` is sent, nothing is submitted and the batch is kept. After unarchiving, `/send` works again; to switch projects (the only way on for a deleted one), `/cancel` (discarding it), then `/repo` and start again with `/batch` (other commands stay blocked while collecting). These commands take no arguments, have no Chinese aliases, and appear in `/help` but not panels or native menus. Batches live only in memory: restarting Ycodium clears a collecting batch, and its messages must be resent. See [Batch input](../../docs/user/im-bots.md#batch-input).
+
 `/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.