Windows Codex app sends thread/start with missing inputSchema after plugins/apps are disabled

Open 💬 1 comment Opened Jun 23, 2026 by WebMeesters2

What version of Codex CLI is running?

codex-cli 0.142.0

What subscription do you have?

Plus plan

Which model were you using?

GPT-5.4

What platform is your computer?

Microsoft Windows NT 10.0.22621.0 x64 → WSL: Ubuntu-22.04

What terminal emulator and version are you using (if applicable)?

Working from integrated terminal in VSCode (in WSL-Ubuntu-22.04)

Codex doctor report

What issue are you seeing?

Environment:

  • Codex Windows app
  • WSL2 project: \\wsl.localhost\Ubuntu-22.04\home\ruben\projects\ha-voicemeeter-mute
  • App logs: C:\Users\Ruben\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\06\23\...

What happened:

  • After disabling apps/plugins/browser/computer_use in C:\Users\Ruben\.codex\config.toml and C:\ProgramData\OpenAI\Codex\requirements.toml, the app still enables apps/plugins/thread_tools/tool_suggest/tool_call_mcp_elicitation.
  • Starting a new thread fails with:

Invalid request: missing field inputSchema

Steps to reproduce:

  1. Launch Codex Windows app.
  2. Open the WSL2 repo above.
  3. Start a new local thread / submit a prompt.
  4. Observe the failure.

Expected:

  • Codex should either respect the disabled feature config or start a thread successfully.
  • It should not send a malformed thread/start request.

Actual:

  • thread/start fails immediately with:

Invalid request: missing field inputSchema

  • Logs also show enabledFeatures including apps/plugins/thread_tools even though they were disabled in config.

Relevant log lines:

  • 2026-06-23T11:24:05.049Z thread/start response_routed
  • 2026-06-23T11:24:05.051Z error Invalid request: missing field inputSchema
  • 2026-06-23T11:24:21.641Z thread/start response_routed
  • 2026-06-23T11:24:21.645Z error Invalid request: missing field inputSchema

Config state:

  • C:\Users\Ruben\.codex\config.toml has:

apps=false
plugins=false
browser_use=false
browser_use_external=false
computer_use=false
in_app_browser=false
tool_suggest=false
tool_call_mcp_elicitation=false

  • C:\ProgramData\OpenAI\Codex\requirements.toml also sets those features false.

Extra notes:

  • The app log shows it still enabling:

enable_mcp_apps, apps, plugins, tool_suggest, auth_elicitation, tool_call_mcp_elicitation, thread_tools, memories

  • The error appears to be in Codex desktop/runtime config handling, not the repo contents.

Sources: /tmp/openai-docs-cache/codex-manual.md:6758 and /tmp/openai-docs-cache/codex-manual.md:6805.

What steps can reproduce the bug?

Uploaded thread: 019ef43d-1cf0-7922-b997-039f6ed36298

What is the expected behavior?

Codex-GUI responding to any prompt without Error messages

Additional information

I've spent 3 hours and all my 5-hour credits in an attempt to debug the issue using Codex-cli.
It seemed not to learn from its mistakes and kept me restarting Codex-GUI with only one different result when a path-issue was resolved. The rest of the time, the results remained the same.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗