Codex Desktop Git action fails on remote project when passing empty -c core.fsmonitor=

What version of the Codex App are you using (From “About Codex” dialog)?

26.601.2237.0

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When I use Codex Desktop's built-in Git/staging action on a remote SSH project, Codex fails before the Git operation completes.

The command shown by Codex Desktop is:

git -C /home/<user>/projects/tis -c core.hooksPath=/dev/null -c core.fsmonitor= add -u

It fails with this error:

failed to spawn process: No such file or directory (os error 2)

This does not appear to be a repository problem or a general Git installation problem. Git is available on the remote machine, and the repository itself is valid.

The suspicious part is the empty temporary config value passed by Codex Desktop:

-c core.fsmonitor=

Using a non-empty value works as a workaround:

git -C /home/<user>/projects/tis -c core.hooksPath=/dev/null -c core.fsmonitor=false add -u

Changing the repository or global Git config does not fix it, because Codex Desktop passes -c core.fsmonitor= directly in the command, which overrides configured Git settings.

So the issue appears to be in Codex Desktop's remote Git action / app-server spawn path when it passes an empty core.fsmonitor= value.

What steps can reproduce the bug?

Feedback ID: 019e91d8-6163-750Feedback ID: 019e91d8-6163-7500-ab0f-757158213539

1. Open Codex Desktop on Windows.
2. Connect Codex Desktop to a remote Linux project over SSH.
3. Open a Git repository on the remote host.
4. Modify one or more already-tracked files.
5. Use the Codex Desktop Git/staging action that stages tracked file changes.
6. Codex Desktop attempts to run a command like:

git -C /home/<user>/projects/tis -c core.hooksPath=/dev/null -c core.fsmonitor= add -u

1. The action fails with:

failed to spawn process: No such file or directory (os error 2)

Workaround that succeeds:

git -C /home/<user>/projects/tis -c core.hooksPath=/dev/null -c core.fsmonitor=false add -u

Token limit usage / context window usage: not applicable.0-ab0f-757158213539

What is the expected behavior?

Codex Desktop should stage tracked changes successfully when using its built-in Git action on a remote SSH project.

If Codex needs to disable fsmonitor for the Git action, it should pass a stable non-empty value such as:

-c core.fsmonitor=false

or avoid passing the empty value:

-c core.fsmonitor=

The Git action should not fail with a process spawn error.

Additional information

The Codex Desktop app is running locally on Windows, while the project is on a remote Linux machine connected through Codex Desktop's remote SSH workflow.

This seems specific to Codex Desktop's Git action/app-server execution path for remote projects. It does not look like a TIS repository configuration issue.

The command can be worked around by replacing the empty core.fsmonitor= value with core.fsmonitor=false.