Repository navigation
Windows support hardening: WSL boundary, doctor checks, sandbox matrix #397
Description
From the Windows research (~50% of pro devs; Conductor is macOS-only, Codex app is Codex-only — an open lane): (1) WSL-boundary rule: run git, watchers, and agents on the same side as the worktree; repos in WSL spawn via wsl -d distro --cd path with poll-watching; worktrees never under /mnt/c. (2) A Windows doctor on project add: core.longpaths, Git Bash presence, Node 22 for Codex, which side of the WSL boundary the repo is on. (3) Per-thread sandbox badge (sandboxed yes/no/why) since it depends on agent x repo-location. (4) node-pty ConPTY rebuild in CI, test on win32-x64, winget publishing.
Activity
currentbits commentedon Aug 17, 2026
Research note (Windows agentic OS): Microsoft's agent-workspace model is per-agent OS ACCOUNTS with scoped folder ACLs — a Windows Solenta could run each thread under an agent account with per-thread folder consent, OS-enforced isolation for free. Also: register Solenta with the Windows On-Device Registry (ODR) so Copilot/VS Code discover it as an MCP host — an OS-level distribution channel unique to Windows.