Use Composal with Windows and WSL

Environment ownership

Run the Composal 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 Composal there.

curl -fsSL https://dl.composal.ai/install.sh | sh

The installer needs no sudo and configures your shell’s PATH automatically. Open a new terminal if prompted, then continue:

com login
com whoami
com 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

Composal 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.

com daemon capabilities --format json

Agents and live tools

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

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

If a Windows desktop agent needs a WSL-backed Composal 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.