What shipped

Inbox2789 — an existing Telegram Business conversation is named in the Inbox list at once.

ChatConversation transcripts name the assigned teammate. A conversation transcript and its exports now show the assigned teammate's name in the header. Before, they showed an internal user ID.

InboxWidgets in the chat shrink when their content gets shorter. After a customer sent the "talk to a person" form, the chat showed "Your request has been sent." above a large empty space. Their request and the "Waiting for a human operator" line sat below it, and they had to scroll down to see them. The form now shrinks to its new size, so the request and status show right under it. This applies to every Busymate AI widget in every chat that shows them.

InboxA signed-in customer still sees their request for a person after reopening the chat. When a signed-in customer asked for a person and then reloaded the page, the chat they reopened stopped showing the request and the "Waiting for a human operator" line. It now shows them again. Other chats still show no request that belongs to a different chat.

ShopifyConversation history in the Shopify admin now shows what the customer saw. When you read a conversation in Busymate AI inside Shopify, or through the MCP conversation reader, the assistant's replies no longer include its own notes, such as "The user asks for a person, so I'll call request_human", or the "I'll check the catalog…" line written before a lookup. You see the same reply your customer saw.

PlatformThe build Mac refuses to start a ship or heavy run when its disk is nearly full, and clears finished lane checkouts on a schedule. Internal: a full disk killed a ship mid-run with an unreadable error. Now ship and test runs stop up front with a clear message, finished lane checkouts are removed daily, and the team is alerted when free space drops under 15%.

Inbox2699 follow-up — a Telegram Business customer's name and @username reach the Inbox. Live e2e (ai 1493) showed Business session d7b3726d with claims only {telegram_id, channel_source}. Busymate AI widgets in ChatGPT and claude.ai now inset their header, table and footer evenly, and row counts use proper singular and plural forms in all languages.

ChatEdge deploys can no longer overlap, and a deploy that fails to come up rolls itself back. Two Edge deploys at once used to recreate the functions container together. Onthat left every Edge function returning 502 for about 3 minutes. Deploys now queue behind a lock on the server, and a release that does not turn healthy is replaced by the previous one automatically.

PlatformAfter a reload, steps rebuilt from a finished scan show no elapsed time instead of a made-up "0s".

PlatformOn a slow host the scan now gives each page a longer wait (scaled from how slowly the first page answered, up to 25 seconds) and reads fewer pages at once, so slow sites are read in full instead of just their home page.

PlatformBusymate AI's site scan waits up to 30 seconds for your first page (it used to give up after 7), so slow shared hosts are read instead of reported as down.

InboxChatGPT picks up Busymate AI widget security settings again. When a Busymate AI view's settings change, such as its content security policy, the view gets a new address. ChatGPT and Claude then load the new settings instead of a cached copy, so ChatGPT no longer shows "csp off". Busymate AI handoff and conversation tables show what people need. In ChatGPT and Claude, the handoff-request table now shows the request number, title, summary, status, how long it has been waiting and who it's assigned to. Conversations show channel, whether they are live, and when they started and were last active. Internal run ids and routing keys no longer appear. Busymate AI views in ChatGPT keep their data when you reopen a chat. When you go back to an earlier ChatGPT chat, including in the iOS app, the Busymate AI tables and cards show their data again instead of an empty frame. If a view still gets no data, it now says so ("Couldn't load this result. Busymate AI says plainly that bulk deletion isn't available. When you ask an AI assistant connected to Busymate AI to delete conversations or other data in bulk, it now tells you this isn't available instead of asking which data you mean. A request to talk to a person now appears only in the chat it was made in. Opening a conversation transcript from the Inbox shows the transcript again. The Inbox's "View transcript" link opened a "This page is no longer here" error for every conversation. It now opens the transcript, and the breadcrumb names the workspace. A conversation that is not in this workspace shows "Conversation not found" with a link back to the Inbox, and a link pasted without its iv.

InboxResolving a conversation hands it straight back to your mate, and no Telegram message is ever lost. When you resolve or hand back a conversation in the Inbox, your mate answers the customer's next message again right away. Pressing take-over again on a conversation you already hold pauses your mate again, and the Telegram send tick on your replies now updates live.

Platform2699 — Telegram users shown by name and @handle (and linked to their app).

ShopifyA store whose public chat page is off no longer shows its name on the "not found" page. When a workspace's public page is switched off (a password-protected Shopify store), its address and a direct visit to busymate.ai/support/<slug> now show a neutral "Busymate AI" page title and product name, not the store's name. The storefront widget is unchanged.

InboxBusymate AI's tool results are fully described for ChatGPT and Claude. Every Busymate AI tool that shows a card or table now declares the shape of what it returns. Its views declare their security policy, so ChatGPT no longer marks them "csp off". The server's description no longer mentions other products. Our own overnight checks no longer show up as customer conversations in the platform Inbox. When a person takes over a Telegram chat, your mate goes quiet and the operator sees every customer message. Taking a conversation over in the Inbox now pauses your mate in that chat until you resolve it (or for the workspace's hold window after your last reply). While you hold a Telegram or Telegram Business chat, your mate no longer answers next to you, and each message the customer sends shows up live in the Inbox thread. Your mate no longer shows customers its own notes about which internal step it is taking. A note that your mate writes to itself, such as "The user explicitly asked to talk to a person, so I'll call…", is no longer shown to customers in your site's chat. This applies wherever the note appears in the reply. When a connected store app gains a new option (for example sorting products by price), your mate now picks it up on its own instead of waiting for the store owner to sign in again. Long-running connections from Claude and other MCP clients to Busymate AI now stay open for up to 14 minutes instead of being closed and reopened every 6.5 minutes. Internal: no public change.

InboxDeclining an action reads as your customer's choice, answers no longer open with "I'll check…", and cancelling an order asks "Cancel order" or "Keep order". When a customer declines an action your mate asked them to approve, your mate now treats it as their choice and no longer says the action was denied. Answers start with the answer. A store can switch off its public chat page and keep the assistant only on its own site. A workspace whose public hosted page is switched off (channels.hostedWeb. Claude can use what Busymate AI's tools return. In Claude, a tool that shows a table or card, such as your workspaces or conversations, now also gives Claude the data itself. So "list my workspaces and show the inbox counts for Demo Bakery" runs to the end instead of asking you for an id. Busymate AI widgets in ChatGPT and claude.ai no longer draw a second border inside the host's own frame.

InboxReal-browser ssrf test moves to its own CI row. The real-Chromium test of the /try snapshot browser no longer runs inside the ordinary web unit tests, where it silently skipped on CI and flaked on busy machines. It now has its own browser row that reports a missing Chromium by name and fails when the proof is incomplete. Sign-in card and tool chips use the visitor's language. In a Spanish (or any non-English) chat, the sign-in card, the "Checked. The platform Inbox no longer lists our own uptime checks as "Anonymous visitor" conversations. Opening a chat with /start now gets a plain greeting from your mate, without a note saying the command isn't recognized. After a store teammate replies, the chat shows when they replied instead of "Away", and reloading the store during a handoff no longer logs an error. The Inbox shows whether a Telegram reply was really sent. A reply to a Telegram customer now shows its real state in the Inbox.

InboxThe platform assistant now greets you when you open a chat with /start or an empty message, and answers "how do I add / connect / install you?" questions from the Busymate AI docs instead of saying it has no details. The Console now shows where your try-outs and sign-ups come from. Platform › Insights › Sources is a new page in the Growth group. Claude can connect to Busymate AI again. Adding Busymate AI in Claude, from the directory or as a custom connector at https://busymate.ai/mcp, signs you in again instead of failing with "Couldn't register with … sign-in service". Your Inbox reply to a Telegram customer is now sent even after you take the conversation over. When a customer asked for a person on Telegram and you then took the conversation over in the Inbox, your reply showed as sent but never reached the customer's chat. It now does. Busymate AI's server functions stay warm between requests, so fewer calls pay a cold start, and long Claude connector calls are no longer cut off at about 6.5 minutes. Internal: no public change.

MCPA connector that needs sign-in now says so, instead of claiming its credential was rejected. When your mate is used in a channel such as Telegram and a connector needs sign-in but no credential is stored for that channel, your mate now says plainly that the connector needs sign-in and isn't available on this channel yet. Before, it called the connector with no credentials and then wrongly reported that "the stored credential was rejected".