bug: Amazon Q Developer being installed breaks Visual Studio Code Python Debugging on macOS

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

macOS 15.6.1

Expected behaviour

When starting a Python debugging session within Visual Studio Code, it starts a debug session command in the integrated Terminal, and then connects to it and shell prompt doesn't return until debugging is completed/program has exited.

Actual behaviour

When Amazon Q Developer is installed on macOS and you begin a Python debugging session in VS Code, VS Code will run the same expected shell commands to spawn a debugging session and connect to it, but it will immediately quit and VS Code will continuously wait to connect to a debug session that already quit until it eventually times out.

Steps to reproduce

1.) Do a clean install of Visual Studio Code on a Mac
2.) Do a simple python hello world script and set a debugging point somewhere so the debugger will have to clearly stop and wait
3.) Start debugging, VS Code spawns an integrated terminal, runs shell commands to spawn a debugging session, and attaches to it.
4.) Debugger stops at break point as expected
5.) Do a clean install of Amazon Q Developer for Mac, do all required shell and accessibility enablements
6.) Start debugging, VS Code spawns an integrated terminal, runs shell commands to spawn a debugging session, session immediately exists out.
7.) VS Code keeps waiting to attach to session that is already closed.
8.) VS Code debugger times out.

Environment

[q-details]
version = "1.15.0"
hash = "eb8db5c635fc469f3bd94ead16bb4bfb32d7443b"
date = "2025-09-02T17:57:24.662205Z (1d ago)"
variant = "full"

[system-info]
os = "macOS 15.6.1 (24G90)"
chip = "Apple M4"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "brew"

[env-vars]
PATH = "/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.local/bin"
QTERM_SESSION_ID = "bf52c32574f14f048312d280439567c8"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.15.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"

Riproduci il problema di debug di Python in Visual Studio Code su macOS 15.6.1 con Amazon Q Developer 1.15.0 installato, confrontando l’ambiente del terminale integrato prima e dopo l’installazione. Traccia l’effetto della sessione zsh e delle variabili d’ambiente relative a Q sul comando del debugger; l’attività è completata quando la sessione rimane attiva, si arresta su un punto di interruzione e VS Code si collega correttamente.