Codex plugin MCPs are disabled by plugin requirements that never mention MCP servers
publi0 · ghdev · 2026-07-19
A Codex bug report says plugin MCP servers are being disabled whenever requirements.plugins exists but none of its entries defines mcpservers.
- The result is that plugin installation and codex mcp login can succeed, but new TUI, codex exec, and Desktop sessions do not receive the plugin MCP tools.
- The reporter argues that an unrelated plugin requirement should not behave like an empty MCP allowlist.
- The proposed fix is to skip MCP filtering unless at least one plugin requirement explicitly declares mcpservers.
- This would preserve explicitly empty allowlists while avoiding accidental disabling of all plugin MCPs.
More from coding & agent
- Spring AI 2.1.0-RC1 adds tool-call confirmation, pausing agent loops before real-data access — therealdanvega · 2026-10-26
- 250 Builders Hack With Codex at Berlin Community Hackathon Ahead of OpenAI DevDay — paw_lean · 2026-10-26
- Building AI bots on raw APIs? Devs say models are 'dumb without the harness' — madeofAjala · 2026-10-26
- HarnessMM cuts agent tokens per task by up to 88% while raising success rates — omarsar0 · 2026-10-26
- Microsoft demos intent-classifying agents built with Copilot App and Foundry, deployable across Teams and Outlook — marlene_zw · 2026-10-26
- Looking for a wearable mic with best battery life that feeds recordings to personal agents via MCP — altryne · 2026-10-26