Linux Projects (WSL)
Linux (WSL) project execution
Section titled “Linux (WSL) project execution”Setup Checklist → Set up a Linux project; Project Settings → Run this project in Linux.
MCP tool: none.
Run Ubuntu-native projects through Orbit while the dashboard stays on Windows — files, commands, agents, servers, builds, and releases route to Linux. A six-step guide checks WSL2 and Ubuntu, the Orbit helper and its updates, the project location, Linux-local agent install and auth, then hands off to Project Settings for routing, and remains available afterward as a ready check.
Project location rule: the project must already exist inside Ubuntu (e.g. /home/user/projects/my-app). Orbit never moves, copies, converts, or syncs a Windows project into Linux. C:\..., /mnt/c/..., \\wsl$, and \\wsl.localhost are all rejected as Linux project locations.
Install command shown (copy-only, never run by Orbit): wsl --install -d Ubuntu-24.04.
Detection: read-only, via wsl.exe --list --verbose on Windows. Never starts, stops, installs, updates, imports, or unregisters a distribution. Linux agent metadata carries only the public CLI identifier, a label, and one of not_installed, sign_in_required, ready, unavailable — no binary paths, credential paths, tokens, or secrets.
Not covered by this surface: Memtrace Govern remains experimental and unavailable under WSL; this does not affect ordinary Linux project work.
Existing-surface integration:
- Setup Checklist — persistent Set up a Linux project entry.
- Setup Settings — persistent checklist row after foundation/power completion.
- Project Settings — persistent How Linux projects work link beside Run this project in Linux.
- Typed routing failures link directly to the relevant guide step rather than showing a generic error.
- Routing itself (validation, active-work locking, confirmation, recovery, fencing, reconciliation, rollback) is owned by Orbit’s existing project-routing controller — the guide only opens it.
Deep dive: context/audits/wsl-node-linux-setup-guide-report.md.