[Windows] VS Code extension enabled in a Remote-SSH session to Ubuntu is having issues using MCP servers #8260

What version of Codex is running?

0.60.1

What subscription do you have?

Company provided Enterprise plan

Which model were you using?

GPT-5.1-Codex

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I'm on Windows and I remotely connect to a Ubuntu 22.04 machine using the Remote-SSH extension. The Codex extension is also installed and available on the remote session. It is able to read and edit the code.

Recently I've added a few MCP servers to the config.toml file. I used the plugin settings icon to open it to make sure I'm editing the correct file. I've added the servers, saved it, restarted VS Code(even restarted the remote Ubuntu box). However, Codex is not using the MCP servers at all and when I asked what MCP servers it currently can use it said that there are no server configured.

I've asked it to list the contents of the config.toml file which is currently using with the absolute file path to it. It showed the correct file. I even opened an external SSH session to check it and the file is there, having the correct contents. When I used it to print the contents of the file I also see the correct result.

After that, it started seeing, listing and using the MCP servers correctly. However, the problem is I have to "convince" it to re-read the file for each new session which is really inconvenient.

What steps can reproduce the bug?

• Install VS Code on Windows with Codex and Remote-SSH extension and any other language tools you want to use for remote development.
• Connect to a remote Linux(I'm using Ubuntu 22.04).
• Add MCP servers using the extension GUI menus to make sure you are editing the correct file.
• Restart IDE, sessions, etc.
• Codex is unable to find the MCP servers until I convince it to reread the file manually.

What is the expected behavior?

The MCP Servers should be usable out of the box when configured correctly.

Additional information

No response