Changelog
What shipped
The AI Assistant releases that came with something to tell you, newest first — one line each, the date it went live, and a link to what changed. A release that only moved internals is not listed.
314 published notesRSS feedDeveloper guide
- build 1194
VoiceConnector screenshot frames. Console screenshots on connector pages display their original panel border without a second image border. The two Telegram conversation crops sit in matching portrait phone frames, keeping their real content complete and undistorted on desktop and mobile. Site screenshot frames retain their existing appearance. Fixed overlapping text in the live website preview bar on phones. The preview backlink is available in More on smaller screens; domains shorten safely and crowded controls wrap.
- build 1191
App StoreMCP connections preserve their credentials when refresh requests overlap or the authentication store is temporarily unavailable. Refresh retries read the winning rotation, recovery overlaps wait for its result, and database outages ask clients to retry without starting another sign-in.
- build 1190
PlatformGenerated-file timeout proof now exercises both ordinary and hosted-runner timeout scales with the real killed generator. Runtime bounds and fail-closed policy are preserved.
- build 1189
PlatformAI release proof albums now reach the AI Assistant bot and group, using the same product routing as release notifications. An unavailable AI destination refuses delivery instead of posting proof to the other product's group.
- build 1188
InboxTelegram command menu rollout. Owner requested all supported slash commands plus account creation and login through Telegram. The owner's explicit deployment authorization from this chat remains in force. This release changes no schema or infrastructure. Ship the fresh codex/telegram-commands-auth lane through the normal protected captain workflow. The supported customer commands are /start, /help, /login, /signup, /account, /logout; aliases route to the same handlers. Signup/login use existing verified GoTrue email/OAuth and explicit tenant-bound Telegram linking. Credentials are entered in the hosted form inside Telegram's browser, never as plaintext bot messages. Logout disconnects Telegram and revokes pending links; browser sessions remain independent. After the new handlers are verified live, use the current release on the agent host with its normal existing environment. The first and last commands are read-only. The first saves all60 prior public command lists in a mode600 file without credentials; preserve it for rollback. The apply registers only this exact customer bot, after getMe matches the configured bot username using the runtime's own credential resolution. A similarly named Vault alias is not the runtime credential. Never register these menus on the separate staff bot or another product's bot. A refused identity check is unverified; stop provider changes and retain the typed verdict. Expected final menu verdict. Verify public version and /connect/telegram return handling, deliver the normal ship notification and live proof album. Real signup/email-code and callback acceptance require a dedicated non-operator test identity; screenshots, source tests and menu readback alone do not prove a real conversation. Telegram customer commands. The customer bot handles /start, /help, /login, /signup, /account and /logout before the model; unknown slash requests show only the supported catalog. Existing sign-in/create-account phrases and slash aliases preserve login/signup intent. Command descriptions and deterministic replies cover all 14 Tier-1 locales; provider menu registration reads the same shared catalog. Account checks and disconnects require a private chat and the tenant/user-scoped customer identity. Group requests get only a private-chat detour. Wrong bot targets and bot senders cannot reach Business link redemption. Existing Business customer routing, scope/allowlist checks and inbound duplicate claim remain in place. Logout revokes outstanding link requests and unlinks only this customer's Telegram identity in a read committed transaction. Separate statements ensure a concurrently winning redemption cannot escape unlink through an old statement snapshot. The reply explains that web sessions remain signed in. A real isolated PostgreSQL18 race run passed through the handler; the temporary container was removed. Unit regressions cover failed-write rollback/release and no false success. Local proof: customer commands, sign-in/auth intent, support inbound, duplicate admission, hook lease and control-character suites; agent/channels-kit strict types. Release captain separately verifies menu registration on each actual channel credential and private/group provider scopes; no live user messages or production mutations from the implementation lane.
- build 1187
PlatformTelegram connection checks time out safely and refuse provider redirects. Telegram connection status now reflects registration failures with their reason and a retry action. Telegram connection recovery, suggested replies and private account linking are more reliable.
- build 1186
PlatformTelegram connection checks time out safely and refuse provider redirects. Telegram connection status now reflects registration failures with their reason and a retry action. Telegram connection recovery, suggested replies and private account linking are more reliable.
- build 1185
PlatformUpdates are more reliable when release workers are busy.
- build 1182
InboxVoice availability is now described by plan, and Telegram pages reflect the released human handoff with its workspace settings. Opening a page proposed by the mobile assistant closes the covering chat panel and shows the destination; the conversation stays available.
- build 1181
ChatOpening a page from a mobile assistant answer closes the covering chat panel so the destination is visible; the conversation remains available. Reopening a homepage conversation preserves the assistant and its history even when an earlier answer contains a completed website preview.
- build 1180
MCPFind our public GitHub community from the footer. The chat sidebar brand now has equal top and left spacing. Homepage assistant history and website previews are kept separate, including saved-chat reopening. Explore released connectors with separate Telegram Bot and Business setup, and keep website demo chats separate from your main assistant.
- build 1175
VoicePhone alerts come from AI Assistant itself. AI Assistant now sends phone alerts with its own push sender. Install the Console on your phone's home screen and allow notifications there to get them. AI Assistant no longer goes through the DevTools app's relay. Anyone on the team can now run AI Assistant on their own laptop with one command. AI Assistant development now has a dedicated private source identity and an organized workspace, with a separate public home for product information and community support. Desktop releases use AI Assistant's own tooling. Desktop signing and release checks now use the AI Assistant source project and its own Vault. A DevTools checkout is no longer needed to prepare a desktop release. Release lock checks run within AI Assistant. AI Assistant now verifies its release lock using its own security contracts, without reading the DevTools repository. Release preflight now reports an exhausted-usage refusal cleanly, without crashing before the lock is initialized.
- build 1174
ShopifySigning in to the Console works again, and the background job that broke it is switched off for good. Reloading /try no longer loses the scan of your website, and when we are busy the page says so and tells you when to try again. The Shopify connector page no longer shows a store password.
- build 1173
MCPAI Assistant now signs its own tokens with a new key, after the old one was exposed. AI Assistant now signs the tokens it issues for MCP connections, the support widget and "Login as" with a new key of its own. Server components use new per-component access keys. Nobody is signed out, and every surface works as before.
- build 1172
PlatformSaying yes to "build an assistant for your site" in Telegram (and every other text channel) now starts the build the first time.
- build 1171
InboxWhen an operator joins a phone caller, both sides' words are now saved to the conversation, each with its translation.
- build 1168
i18nThe footer's "Solutions" links show in the page's language again on non-English pages (they read English since ai 1161).
- build 1165
ChatThe chat page's first load is lighter and steadier: it no longer sends a loading animation it immediately replaces.
- build 1164
MCPEvery busymate.ai marketing page downloads less: repeated logos are drawn once and referenced, and the connectors directory no longer carries each connector page's copy.
- build 1162
InboxThe Inbox's badge counts load faster after new activity arrives.