Anyone else hitting a wall with the ChatGPT plugin creator? There is a frustrating loop happening on platform.openai.com/plugins where the system refuses to acknowledge a verified developer status, effectively locking users out of the "With MCP" creation flow. Even when the account settings explicitly show a verified identity, the plugin interface triggers a blocking dialog that prevents any further progress.
What causes the verification loop? #
The issue manifests when attempting to start a new plugin project. After clicking "Create Plugin" and selecting the "With MCP" option, the platform interrupts the process with a "Complete identity verification" popup. The message explicitly states that a verified developer identity is required to create or upload a plugin.
The breakdown happens during the redirection. When you click "Continue" on that dialog, the site sends you to platform.openai.com/settings/organization/general. On this specific settings page, the account status is clearly marked as verified. However, once you navigate back to the plugin creation area, the system "forgets" this status and throws the same identity verification error again.
Where does this break in the environment? #
This doesn't seem to be a browser-specific rendering issue, as it has been reported across different engines:
- macOS users are seeing this consistently.
- Chrome andSafari both trigger the same loop.
Because the verification is confirmed at the organization level but rejected at the feature level, it suggests a synchronization failure between the identity management service and the plugin deployment tool.
How to handle this block #
If you find yourself stuck in this cycle, checking your organization settings is the first step to confirm you aren't actually missing a requirement. Navigate to the general organization settings to ensure the verification badge is active. If it is, the problem is on the backend side of the platform, and no amount of re-verifying will fix it. When this happens, the "Continue" button becomes a dead link because it leads to a page that already confirms you have met the requirements. To resolve this, you have to wait for a platform-side fix or try clearing the session cache, although the persistence across browsers makes the latter unlikely to work.
Since the plugin architecture relies on a strict handshake between the developer's identity and the MCP (Model Context Protocol) integration, any latency or error in the identity API call will default to "unverified" for security reasons. This is a classic case of a "fail-safe" mechanism becoming a "fail-stop" bug. The only real path forward is to document the discrepancy between the organization settings page and the plugin creator dialog and report it to the developer support channel.
Next Why "uncertainty stacking" breaks self-adaptive systems built on LLMs and agents →
All Replies （1） #
Want a live back-and-forth? Join the global AI chat room — login to talk. The loop happens because identity verification status isn't respected in the plugin creator flow.