app/windows.md +46 −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
31## Native sandbox
32
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.
34
35Running Codex in full access mode means Codex is not limited to your project
36 directory and might perform unintentional destructive actions that can lead to
37 data loss. Keep sandbox boundaries in place and use [rules](https://developers.openai.com/codex/rules) for
38 targeted exceptions, or set your [approval policy to
39 never](https://developers.openai.com/codex/agent-approvals-security#run-without-approval-prompts) to have
40 Codex attempt to solve problems without asking for escalated permissions,
41 based on your [approval and security setup](https://developers.openai.com/codex/agent-approvals-security).
42
24## Customize for your dev setup43## Customize for your dev setup
25 44
26### Preferred editor45### Preferred editor
156Local setup scripts run in the agent environment: WSL if the agent uses WSL,175Local setup scripts run in the agent environment: WSL if the agent uses WSL,
157and PowerShell otherwise.176and PowerShell otherwise.
158 177
178### Share config, auth, and sessions with WSL
179
180The Windows app uses the same Codex home directory as native Codex on Windows:
181`%USERPROFILE%\.codex`.
182
183If you also run the Codex CLI inside WSL, the CLI uses the Linux home
184directory by default, so it does not automatically share configuration, cached
185auth, or session history with the Windows app.
186
187To share them, use one of these approaches:
188
189- Sync WSL `~/.codex` with `%USERPROFILE%\.codex` on your file system.
190- Point WSL at the Windows Codex home directory by setting `CODEX_HOME`:
191
192```bash
193export CODEX_HOME=/mnt/c/Users/<windows-user>/.codex
194```
195
196If you want that setting in every shell, add it to your WSL shell profile, such
197as `~/.bashrc` or `~/.zshrc`.
198
159### Git features are unavailable199### Git features are unavailable
160 200
161If you don't have Git installed natively on Windows, the app can't use some201If 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`.202features. Install it with `winget install Git.Git` from PowerShell or `cmd.exe`.
163 203
204### Git isn't detected for projects opened from `\\wsl$`
205
206For now, if you want to use the Windows-native agent with a project that is
207also accessible from WSL, the most reliable workaround is to store the project
208on the native Windows drive and access it in WSL through `/mnt/<drive>/...`.
209
164### Cmder is not listed in the open dialog210### Cmder is not listed in the open dialog
165 211
166If Cmder is installed but doesn’t show in Codex’s open dialog, add it to the212If Cmder is installed but doesn’t show in Codex’s open dialog, add it to the