Gmail plugin shows installed checkmark while required app connection returns to Connect and exposes no tools

Open 💬 2 comments Opened May 2, 2026 by javenfang
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

I could not confirm the Desktop app version from the current UI during the repro. The local CLI/runtime available on the same machine reports:

codex-cli 0.124.0

What subscription do you have?

Unknown / not relevant to the observed connector state bug.

What platform is your computer?

macOS 26.3 (25D125), arm64.

What issue are you seeing?

Codex Desktop can show the Gmail plugin as installed with a checkmark, while the Gmail required app is not actually connected and no Gmail tools are exposed to the active session.

This creates a false-positive state: the plugin list suggests Gmail is installed/ready, but the setup modal still shows Finish setting up Gmail and the required Gmail app has a Connect button.

Steps to reproduce

  1. Open the Gmail plugin setup flow in Codex Desktop.
  2. Click Connect for the required Gmail app.
  3. Observe the button enters an ongoing/in-progress state.
  4. Complete or wait through the flow. No visible error is shown.
  5. The button returns to the clickable Connect state.
  6. In the plugin list, Gmail still has a checkmark indicating it is installed.
  7. In a Codex thread, inspect or try to use Gmail capabilities.

Expected behavior

Codex should distinguish these states clearly:

  • plugin installed
  • required app/account connected
  • authorization failed or incomplete
  • tools actually available in the current thread

If the required Gmail app connection fails or returns to Connect, Codex should show an explicit failure/incomplete state and should not imply the Gmail integration is ready.

Actual behavior

  • The Gmail plugin appears installed with a checkmark.
  • The setup modal still shows Finish setting up Gmail.
  • The required Gmail app row shows Connect again after an in-progress state.
  • No error is shown during or after the connection attempt.
  • The active Codex session exposes no Gmail tools.

Tool discovery in the active session for Gmail capabilities returned only unrelated GitHub/OpenAI Docs tools and no Gmail send/search/read/draft tools.

Screenshot evidence

The screenshot shows:

  • Finish setting up Gmail
  • Gmail plugin card with openai-curated
  • Required apps -> Gmail
  • Description: Find and reference emails from your inbox
  • The required app button is still Connect

At the same time, the user reports the plugin list shows Gmail with a checkmark, which makes the overall state look successful even though the required app is not connected.

Why this matters

This is less severe than an OAuth page that cannot be clicked, but it is still a product state bug. Users need a reliable distinction between "plugin installed" and "connector/account authorized and tools mounted".

A readiness check should verify that the required app connection completed and that Gmail tools are actually exposed before presenting the integration as usable.

Related issue

This is related in category to #20707, where Readwise also appeared available/installed even though OAuth did not complete and no Readwise tools were exposed. The Gmail case is a separate reproduction because the UI clearly returns to Connect without surfacing an error while still showing an installed checkmark elsewhere.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #20707

Powered by Codex Action

javenfang · 3 months ago

Update from the same repro machine: removing the Gmail plugin/connection and then reconnecting from scratch eventually made Gmail work.

After the remove + reconnect flow, tool discovery in the active Codex session now exposes the Gmail namespace and actions, including:

  • mcp__codex_apps__gmail._get_profile
  • _search_emails
  • _read_email
  • _create_draft
  • _send_email
  • _list_labels
  • _list_drafts
  • batch read / label / archive / delete actions

So the underlying Gmail connector can work on this machine/account.

That narrows the bug: the earlier state was likely a stale or incomplete connection/install state that the UI did not surface clearly. The UX problem remains that the first connect attempt went in-progress, returned to Connect, showed no error, and the plugin list still showed Gmail with an installed checkmark even though no Gmail tools were mounted. A remove + clean reconnect was required to recover.