Allow configuring the assistant command runner shell

Abierto
  • ¿Algo no está bien?
#2,917 1 comentario 0 reacciones 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, java
Área
developer-experience

Línea de trabajo

The issue does not name implementation files, tests, or an entry point. First determine whether shell selection is controlled by the SDK or the VS Code host, then trace how the command-execution tool chooses its runner and handles session settings. Done means a documented setting can select a shell and environment, commands run directly in it, unavailable shells produce an explicit error, and the existing default is preserved.

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

Descripción

Feature request

Allow SDK hosts or users to configure the shell used by the assistant's command-execution tool, rather than always exposing a PowerShell command runner on Windows.

Motivation

In a VS Code session using Copilot SDK on Windows, the integrated terminal can be configured to use Bash, but the assistant's command runner remains PowerShell. Bash commands require an explicit bash invocation, and a WSL Bash environment may not have the same tools or PATH as the configured VS Code terminal.

Desired behavior

  • Provide a documented host or session setting for choosing the command runner shell, including Git Bash or another user-configured Bash on Windows.
  • Allow commands to run directly in the selected shell without a PowerShell wrapper.
  • Clearly expose which shell and environment are active, and report an explicit error if the requested shell is unavailable.
  • Preserve the existing default behavior when no shell is configured.

If this is controlled by the VS Code host rather than the SDK, please direct this request to the appropriate project.

Lenguaje dominante
Java
Estrellas
10.7k
Forks
1.5k
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/copilot-sdk

Todos los issues de github/copilot-sdk

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.