Let coordinated sessions target a specific environment (WSL) when creating sessions in other projects
還沒有人認領這個 Issue。
評估
研究方向
Start with the session-creation tool and /orchestrate entry points, then trace how the environment picker and Repository availability → Environments resolve hosts. Define how an explicit environment, the parent session's host, and the project's primary location are selected, and add coverage showing the requested environment is honored or the documented fallback is used.
由索引模型根據 Issue 內容生成。
描述
Feature summary
Allow a session to choose the target environment/host (e.g. WSL: Ubuntu) when it creates a child session in another project, and default to the parent session's host.
What problem are you trying to solve?
On projects that support Windows and WSL, sometimes WSL is dramatically faster for builds and tests (endpoint security scanning slows native Windows processes significantly), so I want all agent work to run in WSL.
This works for sessions I start manually — I pick WSL: Ubuntu in the environment picker. But once a WSL session orchestrates work across repos, it breaks down:
- The session-creation tool only exposes
execution_location: local | cloud. There is no way to target a remote host such as WSL. - Each project has a single primary path (a Windows
C:\...path in my case), even when the project is also available on WSL via Repository availability → Environments. - As a result, a WSL session that spawns a session in a different project gets a Windows session. Only branch children in the same project stay on the parent's host (fixed in v1.1.23).
- Per-repository Instructions (e.g. "Prefer the WSL env") can't help, because they're injected after the host is already chosen.
Proposed solution
- Add an environment/host parameter to session creation (agent tools and
/orchestrate), e.g.environment: "wsl:Ubuntu", accepted when the target project is available on that environment. - Default child sessions to the parent session's host when the target project is available there, falling back to the project's primary location otherwise.
- Optionally, add a per-project Default environment for new sessions setting (e.g. always WSL), used by both the UI and agent-created sessions.
Workflow impact
Affects anyone on Windows who uses WSL hosts together with multi-session or multi-repo coordination. Today orchestrated work silently falls back to Windows, which gives up the performance benefit of WSL and produces inconsistent toolchains across the sessions in one task. Current workaround: a multi-repo folder project on WSL, which loses per-session worktree isolation.
Installation context
GitHub Copilot app v1.1.21 on Windows 11 with a WSL2 Ubuntu 24.04 host. Projects are cloned on both "This machine" and "WSL: Ubuntu".
Additional context
Related gaps in parity between Windows and WSL:
- MCP servers configured in the Windows
~/.copilot/mcp-config.jsonare not available to WSL sessions; I currently symlink the file into WSL manually. - #4058 — BYOK custom model provider is not forwarded to remote (WSL) sessions
- #3879 — New terminal inside a WSL session opens a Windows shell
- Discussion #4188 — Allow automations to run on specific environments
- 主要語言
- 沒有語言資料
- 星號
- 2.1k
- 分支
- 157
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/app 的其他 Issue
-
triage
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 70/100
相似的 Issue
-
area:dictation bug P2
難度 2/5 1-3 小時 新手友好度 88/100
uttrflow/uttrflow-swift#1584 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
comp/desktop P3 type/bug
難度 2/5 1-3 小時 新手友好度 86/100
NousResearch/hermes-agent#123437 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
steipete/CodexBar#4009 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆