Android: Voice Mode hides connected app tools; switching to text exposes them in the same chat

ChatGPT app version

1.2026.223 (Android build 2622320)

Subscription

Plus

Platform

Android 16, Pixel 10 Pro

Issue

In an ongoing ChatGPT conversation, connected app tools can be unavailable to the assistant while the conversation is in Voice Mode, then become callable immediately after exiting Voice Mode and continuing the same conversation in text.

Observed example: Notion was connected and available to the account. During Voice Mode, the assistant repeatedly concluded that no Notion write tool / connector was available in the session. After exiting Voice Mode and sending a text message in the same chat, Notion search/fetch/create/update tools were exposed and worked normally.

OpenAI's Voice Mode documentation states that Voice does not yet support some tools and that custom actions are unavailable. Even if this behavior is intentional, the current UX/tool metadata makes the limitation look like a missing or disconnected app, leading the assistant to give an incorrect diagnosis and send the user toward unnecessary manual work.

Steps to reproduce

1. Connect an app that exposes callable tools in ChatGPT (observed with Notion).
2. Start or continue a conversation in Voice Mode.
3. Ask ChatGPT to perform an action requiring that connected app, such as creating/updating Notion content.
4. Observe that the assistant cannot see/call the connected app tools and may state that the connector is unavailable.
5. Exit Voice Mode without starting a new conversation.
6. Send a text message asking for the same action.
7. Observe that the connected app tools become available immediately and work.

Expected behavior

One of the following would avoid the failure mode:

• Connected app tools work in Voice Mode; or
• Voice Mode explicitly exposes to the model/user that external app tools are disabled in the current modality, so the assistant can say 'switch to text to execute this' rather than incorrectly concluding the connector is absent.

Ideally, switching modalities within the same conversation should not silently change the tool surface without a clear capability signal.

Actual behavior

The tool surface changes silently between Voice and text. In Voice, the assistant interprets the missing tool as a session/account connector problem. In text, the tool is immediately available.

Why this matters

This breaks agentic workflows that begin by voice and then require execution in connected apps. It also causes misleading troubleshooting: the user may be told to reconnect an app or manually perform work even though simply switching to text restores the tool.

No repository files, tests, or entry points are named in the report. Reproduce the modality switch with a connected app such as Notion and inspect how Voice and text advertise available tools. Done means either connected tools work in Voice or the limitation is clearly exposed so the assistant directs the user to text.