Use Vex with Windows and WSL

Environment ownership

Run the Vex CLI in your Linux distribution, not in a Windows command prompt. The WSL profile has its own configuration, credentials, PATH, and filesystem behavior. Windows desktop applications stay responsible for their own integrations.

Install inside WSL

Open your WSL terminal and install Vex there.

curl -fsSL https://dl.vex.sc/install.sh | sh
vex login
vex whoami
vex clone <org>/<repo>

Keep repositories in the Linux filesystem when possible. It gives command-line tools and file watchers the most predictable behavior.

FUSE is optional

Vex source control, cloning, review, landing, and deployment do not need FUSE. Use a normal checkout first. A virtual working copy is a host capability, not a prerequisite; check it from WSL before relying on it.

vex daemon capabilities --format json

Agents and live tools

Install agent guidance in the environment where the agent runs. vex setup can install skills and, when requested, MCP tools. Those are separate capabilities.

vex setup --yes --targets codex --with-mcp
vex setup doctor --format json

If a Windows desktop agent needs a WSL-backed Vex command, point that integration at the WSL executable deliberately; do not copy Linux credentials into a Windows profile. Continue with agent setup or CLI configuration.