fix(shell): don't exec tmux during VS Code's shell-env probe #73

Merged
lyrathorpe merged 1 commits from fix/vscode-shell-env-tmux-guard into main 2026-07-14 16:48:16 +01:00
1 Commits
Author SHA1 Message Date
Emma Thorpe 2125dd7aac fix(shell): don't exec tmux during VS Code's shell-env probe
CI / flake (pull_request) Successful in 3m46s
VS Code on macOS resolves the shell environment at startup by running an
interactive login shell with stdout piped and no controlling terminal.
The order-200 auto-tmux block treated that probe as a normal interactive
shell and ran `exec tmux new-session`, which fails without a tty ("open
terminal failed: not a terminal") and exits non-zero. VS Code then reports
"Unable to resolve your shell environment: Unexpected exit code from
spawned shell (code 1)".

Gate the exec on a real terminal (-t 1) and skip it when
VSCODE_RESOLVING_ENVIRONMENT is set. Real terminals still land in tmux;
the integrated terminal was already exempt via TERM_PROGRAM.
2026-07-14 16:43:44 +01:00