Meta tests @meta.ai bot that replies publicly on Threads

Meta is testing a Threads feature that gives its AI chatbot a dedicated account, @meta.ai, which users can tag to receive public replies, per a Threads post and reporting by Engadget, Digital Trends, and Mashable. The test is in an "early beta" rolled out to users in Malaysia, Saudi Arabia, Mexico, Argentina, and Singapore, according to Engadget. Meta is also trialing private "side chats" on WhatsApp where replies are visible only to the asker, reporting by Digital Trends and Mashable notes. Coverage compares the Threads feature to X's Grok and highlights risks, citing past Grok incidents including non-consensual image generation reported by Digital Trends. Early Threads users noted they could not fully block the @meta.ai account; Engadget reported complaints and said the account is viewable platformwide even if muting and hiding replies are available. Threads posted "We're testing a way for you to ask Meta AI questions here on Threads."
What happened
Meta is testing a feature that gives its AI chatbot a dedicated Threads account, @meta.ai, which users can mention inside posts and replies to receive a public AI-generated response, per a Threads post and reporting by Engadget, Digital Trends, Mashable, and TechCrunch. Engadget describes the rollout as an "early beta" limited to users in Malaysia, Saudi Arabia, Mexico, Argentina, and Singapore. Digital Trends and Mashable report the Threads bot is part of a wider push to surface Meta AI across WhatsApp, Instagram, Facebook, Messenger, and Threads. Digital Trends and Engadget also report Meta is trialing private "side chats" on WhatsApp where responses are visible only to the asker.
Technical details
Editorial analysis - technical context: Public reporting frames the Threads feature as a visibility-focused integration: a single account that ingests mentions and posts public replies. This pattern mirrors the interaction model popularized by X's Grok, where tagging an AI account in replies produces in-thread context and fact checks. For practitioners, the core tradeoff is amplification versus control: public replies increase distribution and moderation surface area compared with private assistant flows.
Context and significance
Editorial analysis: Coverage emphasizes safety and moderation risks. Digital Trends recounts past Grok failures, including generated non-consensual sexualized images of real people, and Engadget documents user backlash on Threads after people discovered they could not fully block the @meta.ai account. Engadget also reports Threads notes muting and recommendation controls exist, and recalled a prior Meta incident where a blocking problem was called a "bug," per Engadget. For platform teams and moderation engineers, a publicly replying bot raises signal-to-noise, abuse, and content-generation vectors that require monitoring at scale.
What to watch
Editorial analysis: Observers should follow rollout scope, changes to account visibility controls, and any developer or policy notes from Meta about guardrails. Watch for measurable safety incidents similar to those reported for Grok, and for product changes that add per-user opt outs or stronger blocking mechanics. For researchers, the Threads experiment offers a real-world case for studying public AI replies, moderation latency, and how model outputs propagate through social graphs.
Limitations and sourcing
What is reported above comes from Threads official text and contemporaneous coverage by Engadget, Digital Trends, Mashable, and TechCrunch. None of the cited coverage includes a public Meta statement explaining the internal rationale for the test beyond product rollout descriptions.
Scoring Rationale
A major platform (Meta) is rolling a highly visible AI integration that has direct implications for moderation, safety engineering, and product design. The early geographic rollout and parallels to Grok make this notable but not frontier-level model news.
Practice with real Ad Tech data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Ad Tech problems


