statusLine.command is not executed or rendered when footer.showCustom=true
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
### Describe the bug
With `footer.showCustom=true` and `statusLine.command` set to a valid executable, Copilot CLI 1.0.43 on macOS reads `settings.json` for built-in footer items, but never executes the custom status line command and never renders custom output.
There is no visible error in the TUI.
### Affected version
GitHub Copilot CLI 1.0.43
### Steps to reproduce
1. Put this in `~/.copilot/settings.json`:
```json
{
"statusLine": {
"type": "command",
"command": "/bin/date",
"padding": 1
},
"footer": {
"showCustom": true,
"showBranch": true,
"showAgent": true
}
}
```
2. Start a fresh `copilot` session in a new terminal.
3. Verify that built-in footer settings are applied (for example, `showBranch` affects the footer, which shows `settings.json` is being read).
4. Run `/statusline` and verify that `custom` is enabled.
5. Observe that the custom output never appears in the status line.
### Additional verification
I also replaced `/bin/date` with a trivial local shell script that:
- writes a timestamp to a file
- reads stdin
- prints a short string to stdout
That script also never ran: no file was created and no custom output was rendered.
### Expected behavior
When `footer.showCustom=true`, the configured `statusLine.command` should execute, receive the current session status JSON on stdin, and render its stdout in the custom status line area.
### Actual behavior
Built-in footer/status line settings are applied, but the custom `statusLine.command` appears not to execute at all and nothing is rendered for the custom status line item.
### Environment
- OS: macOS
- Copilot CLI: 1.0.43
Guía de contribución
Línea de trabajo
Empieza reproduciendo el problema con el settings.json mostrado y el comando /bin/date; después inspecciona la ruta /statusline y el manejo del pie de página para showCustom. Verifica si el comando configurado se invoca con el JSON del estado de la sesión en stdin. Se considera terminado cuando el comando se ejecuta y su stdout aparece en la línea de estado personalizada cuando footer.showCustom=true.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- shell
- Área
- cli
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 52/100