Google Drive connector connected but no mcp__codex_apps__google_drive tools are exposed in Codex Desktop

What version of Codex are you using?

Unknown from this session.

What subscription do you have?

Unknown.

What platform is your computer?

macOS / darwin-arm64, Codex Desktop.

What issue are you seeing?

The Google Drive connector appears to be installed and connected, and can be selected/mentioned in a Codex Desktop thread, but no Google Drive MCP tools are exposed to the model/tool runtime.

This is not a Google Drive API permission failure: the failure happens earlier, during tool discovery/routing, before any Drive API call can be attempted.

Repro steps

1. In Codex Desktop, connect Google Drive / Google Workspace from the ChatGPT app connections UI.
2. Start a Codex Desktop thread in a local workspace.
3. Ask: [@google-drive] list 3 last modified files I can access.
4. The Google Drive plugin is recognized at the UI/prompt level.
5. Tool discovery is attempted for Drive operations, including queries such as:

• Google Drive list files modifiedTime orderBy
• google drive search files list recent modified modifiedTime orderBy
• mcp__codex_apps__google_drive list files

1. Reconnect all Google connections from the ChatGPT app and retry.

Expected behavior

Codex should expose callable tools under a Google Drive namespace, such as mcp__codex_apps__google_drive..., allowing file discovery/listing/search against Drive.

Observed behavior

Tool discovery returns tools for other installed connectors, including GitHub, Slack, Figma, Notion, GBrain, etc., but no mcp__codex_apps__google_drive namespace/tools are present.

The Google Drive plugin skill files are present locally under the plugin cache and mention the expected connector namespace, but the runtime callable tool surface never includes it.

Troubleshooting already tried

• Disconnected and reconnected Google Workspace/Drive via the ChatGPT app connections UI.
• Retried tool discovery after reconnecting.
• Verified other connector namespaces are exposed in the same session.
• Checked for local CLI fallbacks; local gcloud auth print-access-token could not refresh non-interactively, but this is separate from the Codex connector issue.

Why this seems like a Codex/OpenAI bug

The connected app appears to exist, but Codex Desktop does not expose the Drive MCP namespace at all. Re-authentication cannot fix a missing tool namespace because no Drive API request is ever made.

Related but not exact reports

• #24373 reports Google Drive/Sheets tools exposed but missing write scopes / quota failures.
• #19701 reports broader plugin visibility/listing problems.

This issue is specifically: Google Drive is connected/selected, but mcp__codex_apps__google_drive tools are missing from the callable tool surface.