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
- NVIDIA says Nemotron 3 Ultra hit 97.1% on agentic RTL chip-design tasks — NVIDIAAI · 2026-07-27
- Tokyo Agent Forge hackathon shipped production-ready AI agents in one day — DavidBennett__ · 2026-07-27
- Long-running agents will need immutable event logs, this thread argues — sebpaquet · 2026-07-27
- Agentic Data Science in Practice: Agents Write Code but Answer Wrong Questions — hugobowne · 2026-07-27
- A VS Code extension adds Markdown-style highlighting to Alchemy string templates — samgoodwin89 · 2026-07-27
- Claude’s Stripe MCP connector is being called unusable after repeated disconnects — evielync · 2026-07-27