What shipped

MCPIndexed website pages keep their titles and stored size when a crawl finishes without fetching a new body. A normal resume no longer clears this metadata while leaving the indexed content intact. 1519 — account language persistence. An ordinary signed-in user activating Russian by keyboard triggered /api/locale HTTP 502. The same legitimate caller's profile update returned PostgREST HTTP 403, sqlstate 42501 (permission denied for table profiles). The browser cookie and full reload already retained Russian; the account preference stayed null. The project baseline grants authenticated profile reads but omitted the narrow locale update grant that this endpoint requires. Current tenant public contact directory. A customer asking for this business's social/contact channels receives current public destinations from the conversation's signed tenant. The shared reader rereads eligibility after public provider lookups, masks disconnected contacts using connector-kit v0.4.2, and refuses the entire read on a three-second deadline. Resumed tools retain their resolver-time tenant/account identity and verify the binding again before returning. Telegram Business additionally requires AI/reply eligibility. The external public MCP exposes the same directory fold for AI Assistant only. Its empty input rejects tenant/host/config overrides before reads. It uses configured public destinations and reports missing values as unknown; the agent's existing authorized provider resolver can enrich missing public profiles. External provider lookup parity is not claimed. One executor owns get_contact_channels in platform chat; the tenant directory takes precedence over the public bridge. Validation: focused agent directory/platform seat suites 22/22; shared deadline/revocation suite 13/13; public ingress/directory focused suite 14/14. Required17/17/types/package builds passed at6ea56afb7. First broad affected audit354 pass/6 fail/6 skip; stale placement and public description/count failures corrected, other failures retained. Final amended-source checks, protected landing, release and live acceptance pending. No provider-delivery claim. Visitors asking for social accounts or available contact channels get the current business contacts for their conversation's workspace through get_contact_channels. The shared connector kit reports public usernames, links and numbers plus availability; the runtime rereads current channel rows per invocation and obtains missing Telegram, WhatsApp and Instagram public metadata from the provider. Facebook Page and Messenger are listed separately. Responses are instructed to stay brief and avoid implementation details.

ConsoleKeeping an assistant now saves every page already read by its website preview before setup can publish it. The saved pages survive preview expiry and remain available in Console even when the workspace's plan limits how much can enter its searchable knowledge index. Console distinguishes saved pages from indexed pages, explains a paused import, and lets authorized members read the original page text, headings and retained details through the existing knowledge page view. The same saved-page view is available through the existing management MCP tool. An interrupted import resumes from its saved cursor through the normal knowledge writer and plan limits. Worker completion and cursor updates require the current lease, so an older worker cannot overwrite a newly claimed job. Conversation sidebar accessibility labels follow the interface language. Hosted business chats keep their business context when selecting and reopening a conversation. Contact and product links in answers resolve to the published business website. Independently checked machine translations can be approved with truthful machine-review provenance. Existing human review keeps its current behavior, while automatic review now pins both the reviewed English source and translated value so changed rows are held for another review.

ChatRequest human support directly in chat, with optional contact details.

PlatformValid onboarding forms keep their current behavior.

PlatformKnowledge selection still enables source citations, and existing assignment limits and save behavior are preserved.

VoiceiOS and Android integration pages now link directly to the official example apps, with the published SDK version and a clear build-and-run action. Native microphone recovery guidance. Native chat now directs people who deny microphone access to enable microphone access for the app in their device settings, then try again. Browser chat keeps its browser settings instructions.

InboxKeeping a website assistant now preserves its preview suggestion pills and imports already-read pages into the workspace's knowledge index. Repeating setup preserves an existing indexing generation. An unstarted import whose temporary preview has expired safely uses the normal website crawl; interrupted imports retain their generation and origin checks. Hosted tenant subdomains keep separate website identities from the platform domain and from each other. The saved preview question sets are retained by language, so the questions seen before signup remain the same afterward. Explicitly authored operator questions survive automatic runtime publishing. Tenant replies now receive the visitor’s current interface language in a validated per-turn suffix, with explicit guidance to translate prose and headings while preserving names and URLs. The cached tenant prefix remains unchanged. The preview language choice updates the entire interface and its descriptive business facts, and follows the visitor through sign-in and setup. Try chat exposes the existing conversation-history sidebar and keeps its history across registration. An explicit chat language also survives the first-message URL change, conversation selection and reload, preserving the same conversation and URL fragment. Typed human-support requests now appear in the operator conversation, and existing requests with no message timeline show their saved context. When a restored human handoff is resolved, messages already displayed in the mounted chat remain visible while AI replies resume. That memory is scoped to the current chat and authenticated binding; switching chats clears it immediately and delayed responses cannot restore the old transcript. This frontend safeguard does not expand server history access after a full reload. The homepage tour now gives its real product screens room to read. Each of the five tabs explains what its actual capture shows. Console screens span the section; the chat capture sits near its native size. On phones, wide screens can be panned, and every capture can be opened full size with keyboard and scrolling support. Chat suggestion pills now follow the active chat language. Tenant-specific questions translate their visible labels and submitted prompts together, preserve brand names and icons, and update when the visitor switches languages. Published per-language questions still take precedence; localized default questions cover translation loading or failure. Downloadable microphone SDK source now has explicit feature ownership, so native changes produce a complete test and proof plan. Support chat recovery now keeps rejected session cursors out of the runtime, so recovering an expired chat creates a fresh run while preserving the conversation and pending question. Recognize the retired DevTools AI mirror. The mirror checker now recognizes DevTools C8 retirement only when the selected committed ref descends from the known C8 removal commit and contains none of the retired product trees or mirror declarations. Both check and write modes then report an explicit retired no-op, preserving AI-owned files and the historical mirror pin. Unknown history, unreadable refs, and reintroduced retired paths refuse; legacy mirror exclusion, drift, missing-file, mode, and resolve checks remain active. Surviving shared-source contracts keep their owning gates. Shape follow-up: moved the upstream-state helper into the existing product-mirror feature folder and extracted ref resolution plus retirement dispatch from the checker facade. The facade is now 1,079 physical lines, below its previous budget; scripts/lib gains no direct child. Retirement 7/7 and selected legacy regression 18/18 reruns passed. Lane shape found zero new/grown/gating offenders but correctly returned unverified for tracked files absent from this sparse checkout; full-tree qualification remains with the release captain.

VoiceNative chat microphone permission. On dictation-mic or voice-mode activation, an installed optional native adapter receives a correlated microphone request, asks iOS/Android for OS permission, and answers before capture begins. Native denial requires an explicit retry; its error view omits browser address-bar instructions and the browser-only automatic recovery promise. Cancel, second tap, unmount, and superseded starts cannot open a microphone after a late grant. Complete installation contract. Validation: 45 focused web assertions; 30 frozen SDK/contract/add-on publication assertions; SDK build. Native OS prompts require actual iOS/Android device verification; release/live verification pending. Open full window is disabled inside native iOS and Android support WebViews, including apps that load their tenant URL without integration parameters. Browser chats and the desktop app keep their existing full-window behavior. Native app developers now have a complete iOS/Android microphone integration guide. Docs: https://busymate.ai/docs/guides/mobile-in-app-support and https://busymate.ai/docs/guides/app-bridge-; complete versioned integration. Native integration now starts with the official, versioned iOS Swift package and Android Gradle library, each with a buildable example app and configuration reference. Marketing and generated tenant integration snippets use the actual SDK APIs rather than manual v1 bridges. New platform guides cover identity, OS microphone callbacks, lifecycle and device verification; existing versioned compatibility assets remain available. Official guides: https://busymate.ai/docs/guides/ios-sdk and https://busymate.ai/docs/guides/android-sdk. Publication depends on verified public iOS SDK 1.0.1 and Android SDK 1.0.0 tags and the hosted microphone event implementation. Qualification follows the actual read approval contract. Account reads now run directly in an authenticated chat; writes retain confirmation. The three backend consumers were published from build1206 and their generated live provenance is recorded. Downloadable microphone SDK source now has explicit feature ownership, so native changes produce a complete test and proof plan.

PlatformAuthorized account information reads execute directly in the final shared tool set, while changes continue to require approval.

PlatformThis is a source candidate only. The current queued check and active captain sha remain unchanged. Qualification requires a fresh candidate through normal protected flow and a real lane-bar check reporting the dedicated Mac runner; no queued result, source contract, or runner inventory alone qualifies the change for landing. Local exact-base evidence.

ConsoleConsole account reads explicitly opt out of tool-call confirmation prompts. Asking for account information should execute authorized reads without a Yes/No approval card.

InboxInstagram and Messenger no longer silently discard captionless supported attachment messages. The signed webhook parser accepts the allowlisted image/audio/video/file receipt types independent of missing, expired or non-cdn attachment URLs and retains type only. The gate preserves the caption and prepares honest unsupported-content text before consuming the provider deduplication claim. No attachment URL, binary body or fabricated transcription reaches model input. Human handoff records attachment-type context and keeps AI paused. This is receipt/acknowledgement support only. It does not download or interpret images, transcribe voice, process video/files, support calls, send outbound media, change public permission/availability, synchronize provider deletion or erase native retained history. Actual media interpretation remains blocked in issue 1576. Future unsent seam (issue 1575).

PlatformAi — owned Meta contact links and accurate data-location disclosures. Reach AI Assistant through WhatsApp, Messenger, Facebook and Instagram from the contact page. WhatsApp explains the secure account-link step for account help; Messenger and Instagram describe their current limited availability. The privacy policy and data processing addendum now reflect the confirmed London hosting and Ireland support-storage locations, with clear limits on international processing claims.

InboxNative aliased intervention composer reply. Native support admission and atomic operator initiation. Verified physical inbound uses existing provider bridge credentials to renew exact tenant/route support identity. Event nonce replay cannot extend expiry; revoked visitors never renew. Timeout/5xx/429 leaves the provider event unclaimed for retry before dispatch. Native operator initiation derives delivery from durable visitor/route and creates/stamps the request atomically using existing request/policy authority. Collaboration/operator grace/manual holds are unchanged. Console cannot renew an expired visitor without a fresh authorized customer inbound; existing open-IV rollover continuity is commit3597b3607. Validation: 75 focused tests, zero failures/skips; actual isolated PostgreSQL schema/RPC fixtures cover three-provider ttl, replay, revocation, tenant/channel/actor isolation, concurrency, atomic promotion rollback, seven-day bounded retention and anon/auth rejection. HTTP timeout/secret-rotation→same-event retry regressions prove one dispatch and command dedup across all three providers. Four touched agent TS files. Full Edge follow-up: committed per-function Deno locks and explicit nodeModulesDir:none. Both complete indices pass frozen checks with their own deno.json config from repo root and outside the repo. The native promotion helper requires only table access, fixing the actual Supabase thenable/promise type mismatch without casts. The actual PostgreSQL promotion fixture passes again. Root generated lock remains ignored; no dependency-resolution refusal is counted as TS green.

InboxNative support continuity after SDK run rollover. Console exact/list/history lookup now resolves an open native intervention by the tenant-owned support session and provider, preserving its operator actions and delivery route across reopened WhatsApp/Messenger/Instagram SDK runs. The latest owned run supplies transcript access; deterministic selection handles multiple requests/tied runs. Normal route overlays exclude test requests. No generic takeover whitelist, cancellation authority, cloud association or collaboration/grace policy changed. Validation: 139 focused web tests; semantic/syntactic diagnostics on all 11 touched TS files.

ChatRequest human support directly in chat, with optional contact details and confirmation after your request is saved. Sign in from WhatsApp, Instagram or Messenger, and give your support team time to reply before the AI resumes. Choose suggested responses directly in supported Messenger and Instagram conversations.

PlatformRegistered dedicated Facebook Messenger and Instagram webhook routes for the connected AI Assistant profiles, ready for Meta verification and delivery checks. New macOS checkouts keep Finder view metadata out of source changes. WhatsApp account confirmation now validates its dedicated session with the authentication service instead of querying a table that the native database does not own. The same boundary applies to account session lookup, refresh, mfa and one-use actions.

InboxWebsite previews now recover automatically when a deeper read provides enough usable content. A thin first read no longer keeps the assistant hidden after the site has supplied readable pages. Removed the offline support team notice and generic leave-a-message line from visitor chat. Named operator presence and typing feedback remain available. Move automated Linux checks to our Kubernetes infrastructure, keeping protected release checks and eliminating GitHub-hosted execution fallback. Stop auto-train from dropping unrelated PRs after a required lane-bar fails without attributable test rows. Move portable ship-bar, cache and browser test execution to bounded own Kubernetes pools.

ArtifactsProduction dependency versions now include the compatible fixes identified by the ecosystem audit. The update covers Next.js image handling, Sharp, WebSocket dependencies and transitive parsers/network clients; the application behavior remains subject to owning tests and release verification. Dispatched PR qualification now selects the actual common ancestor of its task head and origin/main. GitHub pull-request merge refs retain their base-tip first parent. Missing refs, unsupported events, non-merge PR heads and ambiguous ancestry fail closed; the official sweep loader and required affected checks still decide the verdict. . Validated with real Git task/PR/criss-cross histories and cli refusal controls (17 tests including existing workflow/baseline controls). No baseline artifacts manufactured, test failures waived or live qualification claimed.

PlatformThe marketing homepage is easier to scan.