Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#4,191 0 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ubuntu
Área
desktop, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.1k
Forks
157
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/app

Todos los issues de github/app

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.