app/windows.md +40 −0
21For enterprises, administrators can deploy the app with Microsoft Store app21For enterprises, administrators can deploy the app with Microsoft Store app
22distribution through enterprise management tools.22distribution through enterprise management tools.
23 23
24If you prefer a command-line install path, or need an alternative to opening
25the Microsoft Store UI, run:
26
27```powershell
28winget install Codex -s msstore
29```
30
24## Customize for your dev setup31## Customize for your dev setup
25 32
26### Preferred editor33### Preferred editor
156Local setup scripts run in the agent environment: WSL if the agent uses WSL,163Local setup scripts run in the agent environment: WSL if the agent uses WSL,
157and PowerShell otherwise.164and PowerShell otherwise.
158 165
166### Share config, auth, and sessions with WSL
167
168The Windows app uses the same Codex home directory as native Codex on Windows:
169`%USERPROFILE%\.codex`.
170
171If you also run the Codex CLI inside WSL, the CLI uses the Linux home
172directory by default, so it does not automatically share configuration, cached
173auth, or session history with the Windows app.
174
175To share them, use one of these approaches:
176
177- Sync WSL `~/.codex` with `%USERPROFILE%\.codex` on your file system.
178- Point WSL at the Windows Codex home directory by setting `CODEX_HOME`:
179
180```bash
181export CODEX_HOME=/mnt/c/Users/<windows-user>/.codex
182```
183
184If you want that setting in every shell, add it to your WSL shell profile, such
185as `~/.bashrc` or `~/.zshrc`.
186
159### Git features are unavailable187### Git features are unavailable
160 188
161If you don't have Git installed natively on Windows, the app can't use some189If you don't have Git installed natively on Windows, the app can't use some
162features. Install it with `winget install Git.Git` from PowerShell or `cmd.exe`.190features. Install it with `winget install Git.Git` from PowerShell or `cmd.exe`.
191
192### Git isn't detected for projects opened from `\\wsl$`
193
194For now, if you want to use the Windows-native agent with a project that is
195also accessible from WSL, the most reliable workaround is to store the project
196on the native Windows drive and access it in WSL through `/mnt/<drive>/...`.
197
198### Cmder is not listed in the open dialog
199
200If Cmder is installed but doesn’t show in Codex’s open dialog, add it to the
201Windows Start Menu: right-click Cmder and choose **Add to Start**, then restart
202Codex or reboot.