[ChatGPT Desktop] Suggested plugin connect/install card does not render in chat

What issue are you seeing?

When ChatGPT detects an available integration/plugin that is not yet installed and attempts to surface the inline connect/install UI, the actual card/button does not appear in the conversation.

This is reproducible with GitHub.

The assistant can successfully detect that the GitHub plugin exists and is available for the account, and it attempts to suggest the plugin so the user can connect it. However, no inline installation card, connect button, authorization prompt, or other UI element is rendered in the chat.

The user therefore has to navigate manually to plugin/integration settings and install the plugin there.

What steps can reproduce the bug?

1. Use the ChatGPT desktop app on Windows.
2. Ask ChatGPT to use or connect an available plugin that is not currently installed, e.g. GitHub.
3. ChatGPT detects the plugin and attempts to surface the plugin suggestion/connect UI.
4. No card, button, or authorization flow appears in the conversation.
5. Refresh/reopen the conversation.
6. The connection UI still does not appear.
7. Manually install/connect the plugin through settings.
8. The plugin works after manual installation.

What is the expected behavior?

When ChatGPT suggests an available integration/plugin, the corresponding inline connect/install UI should render in the conversation so the user can authorize the connection directly from the chat.

If the UI cannot render, ChatGPT should receive a failure signal instead of assuming that the user was shown a connection card.

Additional information

• Platform: ChatGPT desktop app on Windows
• Subscription: ChatGPT Plus
• Date observed: September 7, 2026
• The problem has occurred repeatedly, not just once.
• Refreshing/reopening the conversation did not make the card appear.
• Manual installation through settings worked, confirming that the integration itself was available to the account.

Impact: the assistant reports that it has surfaced a connection flow, while the user sees nothing. This creates confusion and forces unnecessary manual navigation through settings.

The report names no repository files, tests, or entry points; first verify that the ChatGPT Desktop Windows behavior belongs in this codex repository and locate the responsible connection-UI entry point. Done should be an inline install or authorization card when a plugin is suggested, with a failure signal when that UI cannot render.