Copilot agent terminal commands in VS Code Insiders + WSL intermittently terminate with exit codes 130 / 1

[thadguidry]

WSL: Archlinux

• Copilot Chat Extension Version: 0.40.2026031401

• VS Code Version:
  Version: 1.112.0-insider (user setup)
  Commit: 4c82223
  Date: 2026-03-13T23:23:49Z
  Electron: 39.8.0
  ElectronBuildId: 13470701
  Chromium: 142.0.7444.265
  Node.js: 22.22.0
  V8: 14.2.231.22-electron.0
  OS: Windows_NT x64 10.0.26200

• OS Version: Windows 11 Pro

• Feature (e.g. agent/edit/ask mode): Agent

• Selected model (e.g. GPT 4.1, Claude 3.7 Sonnet): Auto - GPT-5.3-Codex

What I see

Popup examples:

• The terminal process "/usr/bin/bash" terminated with exit code: 130.
• The terminal process "/usr/bin/bash" terminated with exit code: 1.
• (Also seen as wsl.exe ... terminated with exit code: 130 in some popups)

Expected behavior

Copilot agent terminal jobs should either:

1. complete normally, or
2. fail with actionable command-level output,

without spurious interruption popups during normal agent execution.

Actual behavior

• Long or chained agent terminal commands sometimes get interrupted.
• Popup appears during agent workflows and forces reruns.
• Exit code is often 130 (interrupt), occasionally 1.

Repro (approximate)

1. Open VS Code Insiders in WSL remote (archlinux).
2. Use Copilot Chat agent mode to run multi-step terminal workflows (clone/build/test/benchmark style).
3. Include at least one longer-running command and follow-up commands.
4. After some runs, popup appears with exit 130 or 1, and command chain is partially interrupted.

Frequency

Intermittent but recurring during agent-heavy sessions with many terminal invocations.

Workarounds tried

• Avoiding manual Ctrl+C helps somewhat.
• Using shorter commands instead of long chains helps.
• Background runs + log capture helps.
• Restarting WSL helps temporarily.

Additional notes

This appears tied to terminal/session lifecycle while Copilot agent drives commands in Insiders + WSL rather than deterministic project build failures.

Logs available on request

I can provide:

• Extension Host logs
• Terminal logs
• Window logs
• timestamps around popup events

Logs:

GitHub_CoPilot_Chat_Logs.txt

Extension_Host_Logs.txt

Extension_Host_Remote_Logs.txt

[go2sh]

I see the same issue with copilot and WSL exiting expectantly after the command finishes. But not in insiders but in:

Version: 1.114.0 (system setup)
Commit: e7fb5e96c0730b9deb70b33781f98e2f35975036
Date: 2026-04-01T09:27:11Z
Electron: 39.8.3
ElectronBuildId: 13658728
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631
´´´

[thadguidry]

@go2sh which WSL distro does this happen with? Can you share your WSL version output?

[go2sh]

wsl --version
WSL version: 2.6.3.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.71
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.6936

WSL Distro is Ubuntu 26.04