Codex app keeps selecting Google Drive instead of Notion in the same session

Open 💬 0 comments Opened Apr 7, 2026 by nickem00

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

26.325.31654

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When I ask Codex to update a Notion page, it repeatedly calls the Google Drive connector instead of the Notion connector.

This happened after I had already used Codex in the same session to work on a Google Slides presentation. Later in the same thread, I asked Codex to update a Notion page.

Codex acknowledged the request correctly in natural language and explicitly said it would use only Notion tools, but the actual logged tool call still went to Google Drive, for example:

Called Google Drive Get Presentation Text tool from Codex Apps MCP

This happened repeatedly.

I then disabled the Google Drive plugin, but Codex still tried to route the action through Google Drive instead of switching to Notion.

So this looks like a connector/tool-routing bug, not a Notion authentication problem.

What steps can reproduce the bug?

Session ID: 019d6429-f465-7ef2-9114-34b6a3b776c7
Has happened once before. Just use Google Drive and Notion in Codex, and after a while it gets stuck.

The chat had compacted the context once, if that matters.

In my case this happened multiple times in a row, even after I pointed out that it was selecting the wrong connector.

What is the expected behavior?

If I ask Codex to update a Notion page, especially after explicitly saying to use only Notion tools, Codex should call the Notion connector and not continue reusing Google Drive from earlier context in the same thread.

Additional information

_No response_

View original on GitHub ↗