When auto activating, the terminal will Ctrl C in the tmux, and my tasks are interrupted

[大川小朋友 (lll123github)]

When auto activating, the terminal will Ctrl C in the tmux, and my tasks are interrupted.
Any way to stop Ctrl C, instead of turning off the auto activation?

[vinkay215]

This appears to be the same terminal auto-activation behavior reported in microsoft/vscode-python-environments, where environment activation can send Ctrl+C to an existing terminal before running the activation command. With tmux, that can interrupt the process currently attached to the terminal.

Since you want to keep automatic environment activation enabled, I would avoid disabling activation completely.

If you are using the newer Microsoft Python Environments extension, try changing the activation method from command to shellStartup:

{
    "python-envs.terminal.autoActivationType": "shellStartup"
}

Then reload VS Code and create a new terminal.

command activation executes the environment activation command in the terminal. shellStartup instead performs activation through the shell startup configuration, so it is a better fit when an existing tmux terminal may contain a long-running process that must not receive Ctrl+C.

The Python Environments extension currently supports shell-startup activation for bash, zsh, fish, PowerShell, and cmd.

If you are not already using the Python Environments extension, install Microsoft's ms-python.vscode-python-envs extension and make sure the Python extension is configured to use it.

There are also existing reports describing essentially the same failure mode, including long-running processes inside tmux being interrupted when VS Code reconnects/reloads and attempts environment activation.

So I don't think tmux itself is the root cause here. The important part is preventing command-based reactivation from being sent into an existing terminal containing a running process.

For long-running tmux jobs, I would also recommend keeping the job in a terminal/session that VS Code does not need to reactivate, at least until this activation behavior is changed upstream.