app/windows.md Codex Docs, 2026-04-08 18:32 UTC → 2026-04-24 18:20 UTC

2 2 

3The [Codex app for Windows](https://get.microsoft.com/installer/download/9PLM9XGG6VKS?cid=website_cta_psi) gives you one interface for3The [Codex app for Windows](https://get.microsoft.com/installer/download/9PLM9XGG6VKS?cid=website_cta_psi) gives you one interface for

4working across projects, running parallel agent threads, and reviewing results.4working across projects, running parallel agent threads, and reviewing results.

5The Windows app supports core workflows such as worktrees, automations, Git

6functionality, the in-app browser, artifact previews, plugins, and skills.

5It runs natively on Windows using PowerShell and the7It runs natively on Windows using PowerShell and the

6[Windows sandbox](https://developers.openai.com/codex/windows#windows-sandbox), or you can configure it to8[Windows sandbox](https://developers.openai.com/codex/windows#windows-sandbox), or you can configure it to

7run in [Windows Subsystem for Linux (WSL)](#windows-subsystem-for-linux-wsl).9run in [Windows Subsystem for Linux 2 (WSL2)](#windows-subsystem-for-linux-wsl).

8 10 

9![Codex app for Windows showing a project sidebar, active thread, and review pane](/images/codex/windows/codex-windows-light.webp)11![Codex app for Windows showing a project sidebar, active thread, and review pane](/images/codex/windows/codex-windows-light.webp)

10 12 

30 32 

31## Native sandbox33## Native sandbox

32 34 

33The Codex app on Windows supports a native [Windows sandbox](https://developers.openai.com/codex/windows#windows-sandbox) when the agent runs in PowerShell, and uses Linux sandboxing when you run the agent in [Windows Subsystem for Linux (WSL)](#windows-subsystem-for-linux-wsl). To apply sandbox protections in either mode, set sandbox permissions to **Default permissions** in the Composer before sending messages to Codex.35The Codex app on Windows supports a native [Windows sandbox](https://developers.openai.com/codex/windows#windows-sandbox) when the agent runs in PowerShell, and uses Linux sandboxing when you run the agent in [Windows Subsystem for Linux 2 (WSL2)](#windows-subsystem-for-linux-wsl). To apply sandbox protections in either mode, set sandbox permissions to **Default permissions** in the Composer before sending messages to Codex.

34 36 

35Running Codex in full access mode means Codex is not limited to your project37Running Codex in full access mode means Codex is not limited to your project

36 directory and might perform unintentional destructive actions that can lead to38 directory and might perform unintentional destructive actions that can lead to

71 73 

72By default, the Codex app uses the Windows-native agent. That means the agent74By default, the Codex app uses the Windows-native agent. That means the agent

73runs commands in PowerShell. The app can still work with projects that live in75runs commands in PowerShell. The app can still work with projects that live in

74Windows Subsystem for Linux (WSL) by using the `wsl` CLI when needed.76Windows Subsystem for Linux 2 (WSL2) by using the `wsl` CLI when needed.

75 77 

76If you want to add a project from the WSL filesystem, click **Add new project**78If you want to add a project from the WSL filesystem, click **Add new project**

77or press <kbd>Ctrl</kbd>+<kbd>O</kbd>, then type `\\wsl$\` into the File79or press <kbd>Ctrl</kbd>+<kbd>O</kbd>, then type `\\wsl$\` into the File

83`/mnt/<drive>/...`. This setup is more reliable than opening projects85`/mnt/<drive>/...`. This setup is more reliable than opening projects

84directly from the WSL filesystem.86directly from the WSL filesystem.

85 87 

86If you want the agent itself to run in WSL, open **[Settings](codex://settings)**,88If you want the agent itself to run in WSL2, open **[Settings](codex://settings)**,

87switch the agent from Windows native to WSL, and **restart the app**. The89switch the agent from Windows native to WSL, and **restart the app**. The

88change doesn't take effect until you restart. Your projects should remain in90change doesn't take effect until you restart. Your projects should remain in

89place after restart.91place after restart.

90 92 

93WSL1 was supported through Codex `0.114`. Starting in Codex `0.115`, the Linux

94sandbox moved to `bubblewrap`, so WSL1 is no longer supported.

95 

91![Codex app settings showing the agent selector with Windows native and WSL options](/images/codex/windows/wsl-select-light.webp)96![Codex app settings showing the agent selector with Windows native and WSL options](/images/codex/windows/wsl-select-light.webp)

92 97 

93You configure the integrated terminal independently from the agent. See98You configure the integrated terminal independently from the agent. See

181`%USERPROFILE%\.codex`.186`%USERPROFILE%\.codex`.

182 187 

183If you also run the Codex CLI inside WSL, the CLI uses the Linux home188If you also run the Codex CLI inside WSL, the CLI uses the Linux home

184directory by default, so it does not automatically share configuration, cached189directory by default, so it doesn't automatically share configuration, cached

185auth, or session history with the Windows app.190auth, or session history with the Windows app.

186 191 

187To share them, use one of these approaches:192To share them, use one of these approaches:

203 208 

204### Git isn't detected for projects opened from `\\wsl$`209### Git isn't detected for projects opened from `\\wsl$`

205 210 

206For now, if you want to use the Windows-native agent with a project that is211For now, if you want to use the Windows-native agent with a project also

207also accessible from WSL, the most reliable workaround is to store the project212accessible from WSL, the most reliable workaround is to store the project

208on the native Windows drive and access it in WSL through `/mnt/<drive>/...`.213on the native Windows drive and access it in WSL through `/mnt/<drive>/...`.

209 214 

210### Cmder is not listed in the open dialog215### `Cmder` isn't listed in the open dialog

211 216 

212If Cmder is installed but doesn’t show in Codex’s open dialog, add it to the217If `Cmder` is installed but doesn't show in Codex's open dialog, add it to the

213Windows Start Menu: right-click Cmder and choose **Add to Start**, then restart218Windows Start Menu: right-click `Cmder` and choose **Add to Start**, then

214Codex or reboot.219restart Codex or reboot.