{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreictbqnuzkyphypu33exatt7l3arirvzn7wisyyhabpxzbzgkmokce",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mniprsw63kn2"
  },
  "path": "/t/codex-desktop-app-on-windows-10-wsl-takes-60s-to-answer-simple-prompt-while-vscode-agent-responds-in-seconds/1382691#post_1",
  "publishedAt": "2026-06-04T21:52:43.000Z",
  "site": "https://community.openai.com",
  "textContent": "Codex Desktop App on Windows 10 + WSL takes >60s to answer simple prompt, while VSCode agent responds in seconds\n\nHi, I’m seeing a consistent Codex Desktop App performance issue on Windows 10 with WSL mode enabled.\n\n## Summary\n\nA trivial prompt like `ping` takes more than 60 seconds in Codex Desktop App before returning a short response.\n\nThe same account, same WSL Ubuntu environment, same project, and same context work normally in the Codex VSCode agent, where the response arrives within a few seconds.\n\nThis looks specific to the Codex Desktop App pipeline, not to the model, project, WSL environment, Python environment, or account.\n\n## Environment\n\n  * OS: Windows 10 Pro\n\n  * Windows version: 2009\n\n  * OS build: 19045\n\n  * Codex Desktop App build: 26.601.2237.0\n\n  * WSL distro: Ubuntu, WSL 2\n\n  * Desktop config:\n\n    * `runCodexInWindowsSubsystemForLinux = true`\n\n    * `integratedTerminalShell = \"wsl\"`\n\n  * Model: `gpt-5.5`\n\n  * Reasoning effort: `medium`\n\n\n\n\n## Expected behavior\n\nA simple `ping` prompt should return in a few seconds, similar to the Codex VSCode agent in the same environment.\n\n## Actual behavior\n\nCodex Desktop App stays in `thinking` for more than 60 seconds before returning a minimal answer.\n\n## What I tested\n\n  * VSCode Codex agent works normally in the same project/environment.\n\n  * WSL path and git commands are fast when run directly.\n\n  * Python/venv are valid.\n\n  * `%LOCALAPPDATA%\\Codex` was reset by renaming the folder and letting Codex recreate it.\n\n  * The issue also reproduces on a Windows-side copy of the repo, not only the original WSL project.\n\n  * `workspace_dependencies` was disabled after an earlier Windows 10-related runtime error; that specific error disappeared, but latency remained.\n\n\n\n\n## Relevant log observations\n\nFresh logs show `git-repo-watcher` failures and aborted git commands around WSL-normalized paths.\n\nFor the original WSL project:\n\n\n    ENOENT: no such file or directory, watch '/home/<user>/projects/my-private-repo/.git'\n    ENOENT: no such file or directory, watch '/home/<user>/projects/my-private-repo'\n\n\n\nFor a Windows-side copy of the repo, Codex Desktop still appears to normalize it into a WSL path:\n\n\n    ENOENT: no such file or directory, watch '/mnt/c/Users/<user>/Documents/CodexTest/my-private-repo/.git'\n    cwd=/mnt/c/Users/<user>/Documents/CodexTest/my-private-repo\n    git.command.complete aborted=true\n    command=\"git -c core.hooksPath=/dev/null -c core.fsmonitor= rev-parse --git-dir\"\n    requestKind=branch-diff-stats\n\n\n\nEarlier logs also showed:\n\n\n    Primary runtime install failed before first turn\n    Codex Workspace dependencies are not supported on Windows 10\n\n\n\nAfter disabling `workspace_dependencies`, this specific error disappeared, but the >60s latency remained.\n\n## Why I think this is Desktop-specific\n\n  * VSCode agent responds in seconds in the same repo/environment.\n\n  * Direct WSL/git checks are fast.\n\n  * The issue persists after resetting `%LOCALAPPDATA%\\Codex`.\n\n  * The issue persists on a Windows-side repo copy.\n\n  * The slow behavior seems tied to Codex Desktop App’s Windows/WSL path handling, git watcher, or pre-response pipeline.\n\n\n\n\nIs there a supported way to disable the Desktop git watcher / branch-diff-stats / WSL path normalization for testing? Or is this a known Windows 10 + WSL limitation in the Codex Desktop App?",
  "title": "Codex Desktop App on Windows 10 + WSL takes >60s to answer simple prompt, while VSCode agent responds in seconds"
}