What shipped

ConsoleConnecting Claude, ChatGPT and other MCP apps is safer. When an app asks to connect to your Busymate AI account, the approval screen now marks Claude, ChatGPT and VS Code as known apps and names who runs them. For any other app it shows an "Unverified app" warning next to the exact address that would receive access. An app can no longer register under a name like "Claude", "ChatGPT" or "Busymate AI" unless it really belongs to them. Unused app registrations are cleaned up automatically. A failed preview insight now says what went wrong and has a Retry button. In Console › Platform › Insights › Previews, a session whose AI insight could not be generated now explains in plain words whether the conversation could not be read or the AI models could not produce a valid insight. A Retry button re-queues it, and the card then shows "Retry queued" until the new insight arrives (about 5 minutes). The raw technical reason is still there under "Technical detail". The same action is available to MCP clients as retry_preview_insight. Preview and support insights are generated again. The AI insight for each website preview, and the scheduled support-insight audit for each workspace, stopped being written after the move to the new hosting on Oct 17. Sign-in events name how the person actually signed in. A Google, Apple or GitHub sign-in now reads "signed in with Google" (or Apple, GitHub) in the platform events and the Console Activity, instead of "signed in with email" for every account that began with an email address. Password, magic-link and one-time-code sign-ins are named too. GitHub sign-in that matches several accounts explains itself, and you can connect GitHub to your account. When the email addresses on a GitHub (or Google, Apple) account belong to more than one account here, the sign-in page now says so and how to fix it, instead of "We couldn't finish signing you in. Please try again." Settings › Account has a new Connect row to add GitHub, Google or Apple to the account you are signed in to; after that, that provider signs you straight in. Other provider reasons (no verified email, email to confirm, already connected elsewhere) are named too.

ChatShips no longer stall on a brief GitHub hiccup. A deploy now waits and tries again when GitHub returns a temporary error. Before, one such error could stop a release that had already passed every check.

MCPThe connector registry check is fresh again.

DocsYour mate connects your website's own MCP server automatically. When your website publishes an MCP server, Busymate AI now connects it for you, with no setup and no question asked. Your mate then answers visitors from the site's own tools (for example its docs search) instead of crawling its pages. Only tools that really work without signing in are offered to anonymous visitors. The connection appears in Console › MCP servers; delete or disable it there and your site is crawled again.

VoiceBusymate AI widgets catch results that ChatGPT on iPhone sends early, and stop hidden refresh errors. Busymate AI widgets in ChatGPT now keep tool results that arrive before the widget has finished loading, so they show their tables instead of a blank or "Couldn't load" card more often on iPhone. Write results and forms no longer show internal fields such as payload hashes, replay flags or raw IDs.

InboxEdge release record for the handoff-list fixes. Records the two self-hosted Edge releases that carried the ChatGPT handoff-list fixes, so the release ledger matches what is live.

InboxThe changelog entry for the Inbox Telegram name follow-up now says what it changed instead of repeating the first entry.

InboxA Member asking ChatGPT about handoff requests now gets a clear answer instead of an error. When your role in a workspace does not include its handoff requests (you are a Member, not an Admin), ChatGPT now hears "your role does not include this workspace's handoff requests" for that workspace and still lists the others. Before, the whole answer said the handoff service returned an error.

InboxTwo small chat fixes: no more "AI AI", and honest Inbox banners for anonymous visitors. The chat composer on a white-label support page no longer doubles the assistant's name ("Message Busymate AI DevTools AI AI" now reads "Message Busymate AI DevTools AI"). In the Inbox, an anonymous conversation whose location or device is known no longer says "Details unavailable".

MCPWebsites that publish their own MCP server are no longer crawled. When a workspace's website publishes an MCP server and the workspace has that server connected, your mate now uses the site's own tools for its knowledge instead of crawling its pages. The knowledge source shows as up to date with no error, and the old crawled pages stop being used for answers. Disconnecting the MCP server brings the crawl back on the next sync. Sites without an MCP server crawl exactly as before.

InboxChatGPT can list open handoff requests again when it names the workspace by its id. Asking ChatGPT "which of my workspaces have open handoff requests?" no longer ends in "the handoff service returned an error". Tools that act on one workspace now accept the workspace id however the assistant words it.

MCPBusymate AI can now tell when a website publishes its own MCP server. The first step toward "sites with MCP tools are used through their tools, not crawled".

Inbox2789 — a new Telegram Business conversation shows its customer's name in the Inbox list from the first message.

VoiceYour preview answer now shows the page its phone number or e-mail came from. When the /try preview answered with a business's phone number or e-mail, it could show "No source found" even though those facts came from a page it had read. It now names the page that carries the number or address, and a link to the site's own www address is no longer treated as a foreign page.

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%.