[Bug] Interactive approval prompt times out and proc ess is Killed in non-interactive env

[YBloom]

Describe the bug

In a non-interactive session, Copilot CLI displays the interactive approval prompt and the process is immediately terminated with “Killed” before any input can be provided—there is no waiting period or chance to select an option. This blocks usage in CI/non‑TTY environments and produces no graceful error or logs. Observed at 2025-11-04T10:43:11.742Z on Linux (x86_64).

Affected version

0.0354

Steps to reproduce the behavior

• Invoke Copilot CLI to run a command that triggers the interactive approval UI; for example:

  set -e
  pwd && ls -la && \
  find . -maxdepth 4 -type f \( -iname "onebot11*.json" -o -iname "*onebot*.json" -o -iname "napcat.json" -o -iname "*napcat*.json" \) 2>/dev/null |     sed 's#^./##' && \
  grep -RIn --exclude-dir=.git -m 1 -e "heartInterval" -e "reconnectInterval" -e "OB11WebSocketClientAdapter" -e "fileLog" . 2>/dev/null | head -n 50
  

• Observe Copilot CLI shows an approval prompt (options like “1. Yes”, “2. Yes, and approve sed…”, “3. No”).

• At the same time, the CLI is killed.

Expected behavior

A non-interactive mode/flag (e.g., --yes or env var) or CI/TTY detection that auto-chooses a safe default; on timeout, exit cleanly with a clear error message instead of abrupt “Killed”.

Additional context

No response

[brandonros]

is that to say, if you are trying to use copilot-cli headless from AzureDevOps pipeline right now... you should not expect it to work as is?