@talqing/mcp 0.13.0 → 0.13.2

package/SKILL.md

@@ -1472,8 +1472,8 @@ rejected one is fixed by creating a corrected copy under a new name.
 - **`add_whatsapp_batch_recipients` on a sending or completed batch messages
   the new rows at once**, with nobody pressing anything. Get an explicit yes.
 
-Replies are answered by the agent on the sender's
-`whatsapp.message.inbound` trigger, which sees the row's columns as
+Replies are answered by the batch's own agent, if `create_whatsapp_batch` named
+one, else the agent on the sender's `whatsapp.message.inbound` trigger. It sees the row's columns as
 `{{userdata.<column>}}` and the whole template, buttons included, as its own
 first message — so write that agent's prompt against the CSV's column names.
 
@@ -1507,6 +1507,12 @@ reply starts from. Send an `idempotency_key` when retrying is possible. A
 provider refusal still stores the item, `delivery_status: failed` (nothing resends it). While
 they have an open chat, post anything but a note into that chat's conversation:
 another one is refused with `chat_open_elsewhere`.
+**Choosing the agent:** a post or batch takes the agent fields an outbound call
+does (`agent_id`, `agent`, `agent_override`, `vars`…; a batch takes no `secrets`).
+Send them to make that agent answer this person — an open chat running something
+else ends, and a template or `agent_text` saves it for their reply; leave them
+out to continue whatever runs. Needs the number's messages trigger on
+(`messages_off`).
 
 ## Secrets, keys and webhooks
 
@@ -1608,10 +1614,11 @@ connects and then fails.
 
 A chat is one text session, as a call is a voice one. `create_chat_message`
 takes a `client_message_id` (a UUID you generate) and returns the reply itself:
-`status`, `items` and `chat_status`. A chat **ends only explicitly** — the
-agent's `end_call`, or `end_chat` — and only then is it analysed and its
-`session.completed` sent, so end the chats you start. On Telegram and WhatsApp a
-person's messages join one chat until it ends; the next starts a new one.
+`status`, `items` and `chat_status`. A chat ends with the agent's `end_call`,
+`end_chat`, or 24 hours after the person last wrote (`inactivity_timeout`) — only
+then is it analysed and its `session.completed` sent, so end the chats you start.
+On Telegram and WhatsApp a person's messages join one chat until it ends; the
+next starts a new one.
 
 A message can carry `images`: up to four `{data_url, filename}` entries beside
 `message`, each a base64 `data:image/...` URL of a JPEG, PNG or WebP under 10 MB.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@talqing/mcp",
-  "version": "0.13.0",
+  "version": "0.13.2",
   "description": "MCP server for building Talqing AI voice, video and text agents from Claude Code, Codex, or any MCP client.",
   "license": "MIT",
   "homepage": "https://talqing.com",

package/tools.json

@@ -3008,7 +3008,7 @@
       "role": "read"
     },
     {
-      "description": "One chat with its health snapshot, cost lines, vars and event trace.",
+      "description": "One chat with its health snapshot, cost lines, vars, what it ran and event trace.",
       "method": "GET",
       "name": "get_chat_detail",
       "parameters": {