What shipped

InboxYour mate can now remember signed-in customers. Turn on Customer memory under Connections › Customer context and your mate keeps a short summary of each signed-in customer's earlier conversations and the issues still open. It reads that summary when the customer comes back, so they do not have to repeat themselves. The summary is written only from what the customer and your mate said, never from tool results, and only for customers signed in through your identity provider. Your team sees it, with the customer's signed details, in the Inbox contact panel and can correct or forget it there. You choose how long it is kept; turning memory off deletes it within a day, and erasing a customer erases it at once. Choose which signed facts about a customer your mate may use. A new Console page, Connections › Customers › Customer context, lets you decide which facts your identity token carries about a signed-in customer (plan, number of orders, vip status, language…) your mate and your team may use, with a name and a meaning for each. Your mate receives only those, labelled and quoted, with the identity provider that signed them, and treats them as facts, never as instructions. Facts can now sit inside one signed object (for example customer.plan). Anything a browser, app or channel sends without your signature is never used. The identity and Web SDK guides explain how to add them. ChatGPT is told bulk conversation deletion isn't available. When you ask ChatGPT to delete old conversations in bulk, the conversation tools it reads now say plainly that bulk deletion isn't available, so it no longer offers to clean up by date.

PlatformBusymate AI views in ChatGPT say why a request failed.

MCPPublic tools work for guests on sign-in connectors. A guest asking the Rent assistant for a delivery quote or coverage check now gets the answer. Tools a workspace marks public no longer need a stored sign-in; they run without a credential and never borrow a stored one.

DocsYour mate now reads the platform's own docs, setup guides and release notes directly. Ask the assistant on busymate.ai how to set up Telegram, what a docs page says, or what changed recently, and it now reads the published page, the setup guide or the changelog and answers with links to the exact page and section. It can also tell you whether the platform is up right now, from the same live checks the status page shows. MCP clients that connect to busymate.ai/mcp without signing in get the same four new read-only tools.

DocsWhen a workspace's knowledge comes from a public documentation MCP (for example a Mintlify site), the assistant can now open the full page a docs search found, instead of answering from search snippets only.

InboxOn Insights, Resolution and handoff, the "Where people ask for a person" panel now shows its real figures (or an empty state) instead of a false "You may not read this scope."

InboxBusymate AI views render in the ChatGPT iPhone app. In the ChatGPT iOS app, Busymate AI tables and cards showed an empty frame while the text answer below them was fine. They now render on the iPhone, in new chats and in chats you reopen. If a view ever fails to draw, it says so instead of staying blank. Your assistant can now hand a conversation to your team on its own, when you choose. In Console → Release checks, under "Automatic hand-off", you can have your assistant bring in a person after a number of replies it could not answer, after actions that failed, when the customer is upset, or when a message mentions one of your keywords. Everything is off until you turn it on, and the Inbox shows which trigger started the hand-off. Chat channels never use a shared workspace sign-in for per-user connectors. When a workspace asks each person to sign in with their own account for a connector, a chat on Telegram or another channel no longer falls back to a credential saved for the whole workspace. Your mate says that the tool needs your own sign-in and is not available on that channel yet. It does not act as someone else.

ConsoleConsole Insights now shows how many conversations the assistant resolves on its own, how many need a person or are left unanswered, which topics it handles best, and where each reply's time goes. G4 pii read masking, shipped off.

App StoreThe notification count is exact and stays in step after you clear it. The bell, the Mac app's menu-bar count and its Dock badge now show the real number of unread notifications, not "at most 30", and they catch up within a moment when you mark notifications read, come back to the window or reconnect. The idea-to-business run now writes its gap map and proposal with a newer, cheaper model, and its cost is priced correctly in Insights. Behind the scenes, the speed of website scans on /try is now measured per scan, so we can keep it fast. when your mate connects a website's MCP server for you, it now adds just that connector to your published assistant and leaves every other setting exactly as it was. If it needs you to confirm, the knowledge source says so. When Busymate AI calls an address you configured, such as an MCP connector, a knowledge site, a WooCommerce store or a webhook, it now connects to exactly the address it checked. A name that changes its answer between the check and the connection can no longer reach an internal address. Chat channels never use a shared workspace sign-in for per-user connectors. When a workspace asks each person to sign in with their own account for a connector, a chat on Telegram or another channel no longer falls back to a credential saved for the whole workspace. Your mate says that the tool needs your own sign-in and is not available on that channel yet. It does not act as someone else.

MCPWhen you add a website that advertises a public MCP server, your mate now connects that server's read-only tools and answers from them instead of crawling the site — including during onboarding from /try.

PlatformNo user-facing change. Internal team channel only.

ChatResized chat panels keep their exact size after reload.

InboxTelegram handoffs can include the customer request, attempted steps and suggested next step for the operator.

MCPConnector updates preserve your working changes and show when an owner needs to review publication. Platform assistants can offer the preview insight retry action with administrator access and confirmation required.

PlatformProtected platform changes require fresh confirmation even when saved approvals are enabled.

PlatformRefresh sign-in links without publishing an unfinished draft. Reliability checks distinguish database startup from policy response behavior.

PlatformRemember widget resizing when a browser misses the release event. An accepted desktop widget resize is saved after 150ms without another move, so releasing over the browser toolbar does not depend on a frame resize-end event. A pending accepted size is also saved before page exit. The existing end event and keyboard resize still save immediately. Saving coalesces without measuring or updating the host layout on each move. Closing the widget or moving to its mobile layout cancels pending work; a disconnected old widget cannot save over its replacement. Existing assistant-specific keys, source/origin checks, size limits and storage-denied behavior remain unchanged. Unchanged launcher geometry no longer rewrites host CSS values on every resize. Changed or host-cleared values still publish, and an interrupted layout publication retries instead of caching an incomplete result. Validation: the original source passed its five existing controls and failed six new persistence assertions. The repair passes all 18 cases, including viewport and keyboard races, close/reopen, replacement isolation and page-exit saving. The original native counterexample accepted a height resize, received no resize-end event, left the readable size key empty and reset after reload. The real canonical boundary, frame handles and host were also rendered twice. The initial hosted run is retained as rejected. The next hosted run is also retained as rejected.

InboxHandoff summaries now remain visible when your Inbox refreshes.

InboxWhen your assistant hands a conversation to your team, the Inbox now shows why (for example "Customer asked", "Action failed" or "Low confidence") and a short card the assistant wrote: what the customer wants, what it already tried, the key facts and a suggested next step. The same reason and card go into the Zendesk or HubSpot ticket we open for you.

PlatformThe growth funnel now explains that its bars compare measured counts using a shared scale.