Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Let coordinated sessions target a specific environment (WSL) when creating sessions in other projects

Aperta
  • Qualcosa non va?
#4,191 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ubuntu
Ambito
desktop, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

triage
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
  1. 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.
  2. 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.
  3. 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.json are 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
Lingua principale
Nessun dato sulla lingua
Stelle
2.1k
Fork
157
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/app

Tutte le issue di github/app

Issue simili

Altre issue su Desktop Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.