How WSL projects work

If a project's path is under \\wsl$ or \\wsl.localhost, Ropenode runs its agent — claude or codex — and its shells and its git inside the WSL distro, as the user who owns the project.

This is not a detail. It is the reason WSL support exists.

Why running as the right user matters

An agent CLI reads its MCP server configuration from the invoking user's home directory. If the agent runs as the distro's default user (often root) instead of you, then:

• it sees none of your user-scope MCP servers, and
• every file it creates in your repository is owned by root, which you then have to clean up.

Ropenode infers the owning user from the project path (or you set the WSL user explicitly in the project's WSL settings) and runs as that user, so the agent sees the same environment you do.

Path translation

Windows and Linux paths are translated automatically in both directions (C:\src ↔ /mnt/c/src).

Node inside the distro

The live Log is fed by a small Node relay, and in a WSL project that relay runs inside the distro. Install Node.js there too, or the agent works fine but the Log stays empty.