Meta Threads test AI account: Meta AI that cannot be blocked causes strong dissatisfaction among users
Meta tested the AI account function in Threads. Users found that Meta AI could not be blocked, and there were more than 1 million posts on related topics. The incident exposed the controversy over user choice and privacy control in AI social products.
Core conclusion
On May 12, Meta tested a new feature on the Threads platform: users can use the @Meta AI account in conversations to get AI answers. But users soon discovered that this AI account cannot be blocked, the blocking button is hidden, and attempts to block will return an error. The topic quickly became popular on Threads, with more than 1 million posts related to "Users cannot block Meta AI".
Key Points
- Time of incident: 2026-05-12
- Involved platforms: Threads (Meta’s social platform)
- Core controversy: Users cannot block Meta AI accounts, privacy and user choice are questioned -Affected objects: Threads global users, AI social product operators
Background and trigger events
Meta announced on Tuesday (May 12) that it is testing a new feature on Threads: users can get answers to @Meta AI in conversations, such as "Why is everyone talking about matcha" or "How do you pronounce Cannes?" Meta has invested heavily in AI and is trying to catch up with competitors such as OpenAI and Google.
But Threads users quickly discovered that the AI account couldn't be blocked, Engadget first reported. In the three-dot menu on the Meta AI account page, the blocking option has completely disappeared. Users who try to block through other means will receive an error.
Data source:
| Source | Link |
|---|---|
| The Verge | Meta won't let you block its AI account on Threads |
| Engadget | Threads users can't block Meta AI |
SEO: The first paragraph contains the main keywords "Meta AI", "Threads blocking", "AI account"
Key Impact (by Dimension)
| Dimensions | Changes | Meaning to users | Suggested actions |
|---|---|---|---|
| User Privacy | Meta AI cannot be blocked | Users lose control over AI interactions | Use "not interested" or mute functions instead of blocking |
| Platform trust | Forced AI exposure triggers backlash | Threads may lose user trust | Pay attention to whether Meta will adjust its strategy in the future |
| AI deployment model | Social platforms are forced to embed AI | AI changes from tools to platform infrastructure | Evaluate whether your own AI products provide exit options |
| Industry trends | Similar to Grok’s model on the X platform | AI social accounts will become the norm | Plan the interaction boundaries between AI and users in advance |
Adaptation suggestions
For content producers and AI product operators, this incident has the following implications:
- AI interaction transparency: Users should have the right to choose whether to interact with AI. It is enabled by default but cannot exit, causing a trust crisis.
- Block vs Mute: Meta offers the option to "not interested" and mute Meta AI replies, but this does not equate to true muting - the user will still see the AI content
- PR response: Meta spokesperson Christine Pai said that it is currently in the testing phase and the functions may change, but user dissatisfaction has formed a storm of public opinion.
Action List
- Check whether your own AI product provides exit/blocking functions
- Manage user expectations well before AI functions are launched online
- Pay attention to the subsequent adjustment direction of Meta as a benchmark for AI social functions
Example: Meta AI usage scenarios
Users can use @Meta AI to obtain conversation background information. For example, when a new user joins a Threads discussion about "AI Content Automation", they can ask @Meta AI "What is this discussion talking about?" and AI will give summary background information. This is exactly what Grok does on the X platform.
Related extended information
Tool entry
Tool brand names that are naturally triggered in the text: Meta AI, ChatGPT, OpenAI, Grok, Google, Gemini, Claude
Internal link guidance (associated reading)
This incident reflects the challenges of AI products in terms of user trust and privacy control. Combined with our content system:
- Want to learn AI content automation? Watch: How to build an AI content automated distribution system with n8n + ChatGPT: a complete 30-minute tutorial
- A real case of trust building in AI tools: Indie Developer: n8n + OpenClaw Automation Workflow Earning $5,000/mo
- Local AI is a reliable choice for protecting privacy: How to run local AI models on M4 Mac with LM Studio: A complete 30-minute tutorial
Monetization angle
How can you make money from this trend?
WayToClawEarn focuses on verified earn playbooks—not just news. Start from these cases.
n8n + OpenAI affiliate site
Automate content and affiliate monetization
Claude + n8n automation agency
Charge monthly for agent workflow builds