Understanding the Status of @Mentions for Custom GPTs: A Cross-Platform Overview

In recent months, many users have noticed significant changes in how @mentions function within the ChatGPT platform, particularly concerning their availability across web and mobile applications. This article aims to shed light on these issues, based on user experiences and official responses from OpenAI, and to contextualize their impact on productivity workflows.

The Evolution of @Mentions Functionality

Historically, @mentions have been a vital feature for users managing multiple Custom GPTs within a single conversation. This capability enables seamless referencing and chaining of different GPTs—such as one for organization, another for formatting, and a third for review—without the need to open numerous chat instances. Such functionality became integral to many users’ daily workflows, including those accessing ChatGPT on mobile devices.

Recent Disruptions Post-GPT-5.1 Launch

Following the mid-November 2025 rollout of GPT-5.1, users have reported notable issues:

On Web Platforms:

  • Initially, @mentions only worked with “legacy” models such as GPT-4 variants.
  • Upon switching to GPT-5.1 or Auto mode, the @ symbol no longer triggered the GPT list.
  • Extensive troubleshooting—including testing different browsers, incognito modes, cache clearing, and account changes—failed to resolve the problem.
  • OpenAI indicated ongoing fix rollouts; subsequently, many users observed that @mentions regained functionality on the web, now supporting GPT-5.1 and GPT-5.2.

On Android Devices:

  • The situation remains unchanged; typing @ does not display the Custom GPT list, irrespective of the selected model.
  • This issue persisted even after the initial web fixes, with no apparent resolution as of now.
  • Consequently, Android users are compelled to revert to desktop workflows when employing multi-GPT configurations, disrupting convenience and efficiency.

Official Support Feedback

Users contacted OpenAI support to clarify the issue:

  • Support confirmed the problem is reproducible on their end.
  • They reassured that the feature has not been deprecated.
  • The issue is under investigation, with no definitive ETA for resolution.
  • Notably, official statements noted that the fix “should already be in place,” with progress described as a “gradual rollout.” This explanation aligns with observed behavior: functionality has returned on web but remains absent on Android.

Implications and User Experience

For many, @mentions are more than a cosmetic feature—they are

Leave a Reply

Your email address will not be published. Required fields are marked *