windows.md Codex Docs, 2026-04-21 18:29 UTC → 2026-05-14 07:00 UTC

7worktrees, automations, Git functionality, the in-app browser, artifact previews,7worktrees, automations, Git functionality, the in-app browser, artifact previews,

8plugins, and skills.8plugins, and skills.

9 9 

10[![](/images/codex/codex-banner-icon.webp)10<div class="mb-8">

11 11 <CodexCallout

12Use the Codex app on Windows12 href="/codex/app/windows"

13 13 title="Use the Codex app on Windows"

14Work across projects, run parallel agent threads, and review results in one place with the native Windows app.](https://developers.openai.com/codex/app/windows)14 description="Work across projects, run parallel agent threads, and review results in one place with the native Windows app."

15 iconSrc="/images/codex/codex-banner-icon.webp"

16 />

17</div>

15 18 

16Depending on the surface and your setup, Codex can run on Windows in three19Depending on the surface and your setup, Codex can run on Windows in three

17practical ways:20practical ways:

134 137 

135 This prints your distribution name.138 This prints your distribution name.

136 139 

137If you don’t see “WSL: …” in the status bar, press `Ctrl+Shift+P`, pick140If you don't see "WSL: ..." in the status bar, press `Ctrl+Shift+P`, pick

138 `WSL: Reopen Folder in WSL`, and keep your repository under `/home/...` (not141 `WSL: Reopen Folder in WSL`, and keep your repository under `/home/...` (not

139 `C:\`) for best performance.142 `C:\`) for best performance.

140 143 

141If the Windows app or project picker does not show your WSL repository, type144If the Windows app or project picker does not show your WSL repository, type

142`\wsl$` into the file picker or Explorer, then navigate to your145 <code>\\wsl$</code> into the file picker or Explorer, then navigate to your

143 distro's home directory.146 distro's home directory.

144 147 

145### Use Codex CLI with WSL148### Use Codex CLI with WSL

171 174 

172### Working on code inside WSL175### Working on code inside WSL

173 176 

174- Working in Windows-mounted paths like `/mnt/c/…` can be slower than working in Windows-native paths. Keep your repositories under your Linux home directory (like `~/code/my-app`) for faster I/O and fewer symlink and permission issues:177- Working in Windows-mounted paths like <code>/mnt/c/...</code> can be slower than working in Windows-native paths. Keep your repositories under your Linux home directory (like <code>~/code/my-app</code>) for faster I/O and fewer symlink and permission issues:

175 

176 ```bash178 ```bash

177 mkdir -p ~/code && cd ~/code179 mkdir -p ~/code && cd ~/code

178 git clone https://github.com/your/repo.git180 git clone https://github.com/your/repo.git

179 cd repo181 cd repo

180 ```182 ```

181- If you need Windows access to files, they’re under `\wsl$\Ubuntu\home<user>` in Explorer.183- If you need Windows access to files, they're under <code>\\wsl$\Ubuntu\home\&lt;user&gt;</code> in Explorer.

182 184 

183## Troubleshooting and FAQ185## Troubleshooting and FAQ

184 186 

319 321 

320Large repositories feel slow in WSL322Large repositories feel slow in WSL

321 323 

322- Make sure you’re not working under `/mnt/c`. Move the repository to WSL (for example, `~/code/…`).324- Make sure you're not working under <code>/mnt/c</code>. Move the repository to WSL (for example, <code>~/code/...</code>).

323- Increase memory and CPU for WSL if needed; update WSL to the latest version:325- Increase memory and CPU for WSL if needed; update WSL to the latest version:

324 

325 ```powershell326 ```powershell

326 wsl --update327 wsl --update

327 wsl --shutdown328 wsl --shutdown