Skip to content

Codex Apps MCP intermittently fails to initialise — Gmail tools unavailable #57137

Open

Description

@Chancerph

Bug description

The Windows Codex desktop application intermittently fails to initialise the codex_apps MCP client.

When this occurs, connected Gmail tools may appear in the tool inventory but fail when invoked, preventing Gmail-dependent workflows from running.

The issue occurs in local Codex sessions using This computer.

Expected behaviour

The Apps MCP client should initialise successfully, and connected Gmail tools should be available for execution.

Actual behaviour

Codex reports:

MCP startup failed: handshaking with MCP server failed
HTTP request failed: error decoding response body,
when send discover request

When calling Gmail:

MCP tool codex_apps/gmail.search_emails is not available to the model

The Gmail call is rejected immediately without reaching the Gmail API.

Reproduction

  1. Open the Codex desktop app on Windows 11.
  2. Select local execution (This computer).
  3. Start or reopen a conversation.
  4. Attempt to execute a connected Gmail search.
  5. In affected sessions, the Apps MCP client fails during discovery and the Gmail tool is unavailable.

The problem is intermittent; other sessions can execute Gmail searches successfully.

Diagnostic evidence

Failed session ID:

01a167f3-8c91-7463-92b3-8fa477652129

23 October 2026, British Summer Time (UTC+1):

  • 09:49:36 — codex_apps status starting
  • 09:49:39 — codex_apps status failed
  • 10:06:00 — Gmail tool rejected immediately as unavailable

No codex_apps status=ready entry was identified for this session before the failure.

The diagnostic logs indicate an HTTP response-decoding failure during MCP discovery.

Security software investigation

Norton 360 Premium is installed.

Controlled tests on 20 October showed Gmail MCP failures with Norton HTTPS scanning enabled, success with scanning disabled, and failure after re-enabling it.

Norton support subsequently adjusted ChatGPT application permissions.

Gmail searches then succeeded in fresh Codex sessions with HTTPS scanning enabled, including after restarting Codex, but another session subsequently failed during MCP initialisation.

This suggests possible HTTPS inspection interference but does not conclusively establish the root cause.

Impact

The failure blocks an automated email-processing workflow. The automation remains paused to avoid incomplete or inconsistent processing.

Request

Please investigate the Apps MCP Streamable HTTP handshake/discovery response-decoding failure and advise whether this is a Codex client, MCP

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    mcpIssues related to the use of model context protocol (MCP) servers
    connectivityIssues involving networking or endpoint connectivity problems (disconnections)
    on Oct 26, 2026
  2. TsangKwunHei commented on Nov 20, 2026

    @TsangKwunHei

    Chancerph, one comparison that might help narrow this down is to start a fresh local session immediately after a failed one, with HTTPS scanning still enabled. For each session, check whether codex_apps reaches ready and whether a search for a known test message succeeds. If the fresh session works while the original still fails, that gives maintainers two session IDs under the same security settings and helps isolate the startup failure from Gmail access.

    I work on Zortex, which has a separate local MCP path for Gmail. If this is still blocking you, I can help check whether a single read-only search against a test mailbox works in the same setup. I've verified local tool discovery on macOS so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingconnectivityIssues involving networking or endpoint connectivity problems (disconnections)mcpIssues related to the use of model context protocol (MCP) serverswindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions