[Feature Request] Pre-configure WSL environments for Desktop sessions (wslConfigs / deep link / trust via settings)

Feature request

Allow pre-configuring WSL environments (distro + folder, ideally trust) for Desktop Code sessions — the WSL analogue of the existing sshConfigs managed setting — and/or a deep link that opens a Desktop session in a given WSL distro + folder.

Problem

Our team's repo (Linux-native toolchain) requires Windows users to work inside WSL 2. We ship a bootstrap prompt that drives the whole machine setup agentically — WSL check, prerequisites, gh auth, clone into the distro filesystem, toolchain bootstrap, git identity — and it all automates cleanly except the very last step: getting the next Desktop session to open in the WSL environment at the repo folder.

Today that hand-off is click-through only:

1. Fully exit the app (File → Exit — closing the window isn't enough, and an instance already running when the distro was installed doesn't show a WSL section at all until restarted),
2. new session → environment picker → distro under WSL,
3. folder picker → /home/<user>/path/to/repo,
4. workspace trust dialog.

None of it can be pre-configured, deep-linked, or granted via settings, so the last mile of an otherwise fully agent-driven onboarding is a screenshot-by-screenshot manual walkthrough that we maintain in our docs.

What exists today (for contrast)

• SSH: admins can pre-configure connections via sshConfigs in managed settings, so team members get them in the environment picker with zero setup (documented at code.claude.com/docs/en/desktop#pre-configure-ssh-connections-for-your-team).
• WSL: no equivalent. No wslConfigs, no default-environment setting, no trust pre-grant.
• Deep links: claude-cli:// only launches terminal sessions; no Desktop-session variant, no WSL targeting.

Proposal (any of these would help, in rough order of value)

1. wslConfigs managed/user setting mirroring sshConfigs: distro + default folder(s), shown pre-wired in the environment picker.
2. Deep link for Desktop sessions, e.g. claude://code/new?env=wsl:Ubuntu&cwd=/home/me/lab/repo, so bootstrap tooling can end with "click this link" instead of a four-step manual walkthrough.
3. Workspace trust via settings (e.g. a trusted-folders list scoped per distro), so orgs that already vet the repo can skip the dialog.
4. Smaller polish: detect newly installed WSL distros without a full app exit (window close doesn't kill the app, which makes the current behaviour extra confusing — the picker silently lacks a WSL section until File → Exit).

Environment

• Claude Code Desktop on Windows 11 Pro (10.0.26200), WSL 2, Ubuntu 26.04
• Use case: agent-driven onboarding of new Windows machines for a monorepo whose toolchain (mise/uv) is Linux-only