1# WSL1# WSL

2 2 

3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

4 

3When you use WSL2, Codex runs inside the Linux environment instead of using the5When you use WSL2, Codex runs inside the Linux environment instead of using the

4native [Windows sandbox](https://learn.chatgpt.com/docs/windows/windows-sandbox). Choose WSL2 when you need Linux-native6native [Windows sandbox](https://learn.chatgpt.com/docs/windows/windows-sandbox). Choose WSL2 when you need Linux-native

5tooling, your repositories and developer workflow already live in WSL2, or7tooling, your repositories and developer workflow already live in WSL2, or

33- Integrated terminals should display Linux paths (such as `/home/...`) instead of `C:\`.35- Integrated terminals should display Linux paths (such as `/home/...`) instead of `C:\`.

34- You can verify with:36- You can verify with:

35 37 

36 ```bash38```bash

37 echo $WSL_DISTRO_NAME39 echo $WSL_DISTRO_NAME

38 ```40```

39 41 

40 This prints your distribution name.42 This prints your distribution name.

41 43 

44 `C:\`) for best performance.46 `C:\`) for best performance.

45 47 

46If the Windows app or project picker does not show your WSL repository, type48If the Windows app or project picker does not show your WSL repository, type

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

48 distro's home directory.50 distro's home directory.

49 51 

50## Use Codex CLI with WSL52## Use Codex CLI with WSL

69 71 

70## Work on code inside WSL72## Work on code inside WSL

71 73 

72- 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:74- 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:

73 ```bash75```bash

74 mkdir -p ~/code && cd ~/code76 mkdir -p ~/code && cd ~/code

75 git clone https://github.com/your/repo.git77 git clone https://github.com/your/repo.git

76 cd repo78 cd repo

77 ```79```

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

79 81 

80## Troubleshooting and FAQ82## Troubleshooting and FAQ

81 83 

82Large repositories feel slow in WSL84Large repositories feel slow in WSL

83 85 

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

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

86 ```powershell88```powershell

87 wsl --update89 wsl --update

88 wsl --shutdown90 wsl --shutdown

89 ```91```

90 92 

91VS Code in WSL cannot find codex93VS Code in WSL cannot find codex

92 94