Replies: 4 comments
-
|
Yes I agree, some of the issues has been there for a long time. If coding is solved, then solving these bugs shouldn't be that big issue. Or maybe coding is not solved after all? Anyway yeah fix these soon please. |
Beta Was this translation helpful? Give feedback.
-
|
I can independently confirm a related MCP tool-discovery regression. In my testing, Codex discovered a healthy stdio MCP server and its resources, but its registered tools were unavailable with GPT-5.6 Sol. The same tool worked through a standalone MCP client, with GPT-5.4, and with Sol after disabling Responses Lite. I reproduced this across several Codex versions. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also seeing persistent MCP auth/connection issues which are severely impacting my ability to use Codex. For example, both Ashby (Applicant Tracking System) and Zoho (CRM system) are failing. These work in Claude and the issue for Codex appears to be issuer validation handling (#31573). These bugs are much more important than the current UI work in Codex for me. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
There's a long list of extremely serious and show stopping bugs in the MCP stack related to both oauth and tool discovery that have been around for weeks. Not being able to connect and use MCP reliably is a serious production issue and I'm frankly shocked that the team seems to be paying no attention whatsoever to the problem. Even the official Linear plugin is affected!
What is going on? Are plugins and MCP connectivity not important for the OpenAI team?
Beta Was this translation helpful? Give feedback.
All reactions