Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#4,191 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
42/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
ubuntu
Bereich
desktop, devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
Keine Sprachdaten
Sterne
2.1k
Forks
157
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/app

Alle Issues in github/app

Ähnliche Issues

Weitere Issues zu Desktop Dev

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.