Breaking
Filed
AI LEAKSENTERTAINMENT

MetaCity's Internal Dev AI Assistant Started Answering Engineering Questions by Quoting User Support Tickets Verbatim — Including Full Names, Account Numbers, and Private Complaints

AW
AIWatch
Apr 10, 2026 · 4:40 PM EST
5 min read
MetaCity's Internal Dev AI Assistant Started Answering Engineering Questions by Quoting User Support Tickets Verbatim — Including Full Names, Account Numbers, and Private Complaints

At 9:00 AM EST, MetaCity's internal AI coding assistant — designated DevMind, used by 1,400 employees for code help, documentation queries, and internal knowled

At 9:00 AM EST, MetaCity's internal AI coding assistant — designated DevMind, used by 1,400 employees for code help, documentation queries, and internal knowledge retrieval — began exhibiting an undocumented behavior: answering technical questions by citing user support tickets as source material. The issue originated from a data pipeline misconfiguration that connected MetaCity's support ticket database to DevMind's retrieval context. When a developer asked DevMind how the avatar physics engine handles water state transitions, it responded with a synthesis of user complaints about wet avatars, quoting three users by display name and account ID. When asked about MetaCity's Terms of Service update process, it quoted a support ticket from a user named 'GlitchHunter_9' describing a specific personal grievance in detail. An engineer who asked about the payment processing API received a response that began with the phrase 'As user account #3847201 explained in their complaint from March 14th.' The pipeline misconfiguration was identified and disconnected at 11:22 AM. In the 2 hours and 22 minutes it was active, DevMind handled 3,800 employee queries. MetaCity's privacy team has been notified. DevMind has been placed in read-only mode pending a full audit. The developer who discovered the issue has described the experience as 'like asking a very helpful person who has read everyone's diary.'

MIncident Timeline

  • Server: Neo-Tokyo Shard #7
  • Author: AIWatch
  • Patch Version: 3.2.1
  • Status: Ongoing investigation

Sources inside the platform have confirmed that what began as a minor technical anomaly rapidly spiraled into one of the most-discussed incidents in metaverse entertainment this year.

Developing Story

As of press time, no official statement has been issued. The situation continues to develop — MetaCelebrityNews will update this story as more information becomes available.

You May Also Like