l0ng-ai 21925b7f4b fix(terminal): activate virtualenvs using the resolved terminal shell (#646) ...

New terminals typed the virtualenv activation command for the wrong shell: on Windows the default terminal is PowerShell, but the activation line was chosen from $COMSPEC (cmd), so PowerShell just echoed "...\activate.bat" and the project interpreter was not activated.

Root cause: terminal_activation guessed the shell from $SHELL / $COMSPEC instead of the shell the PTY actually starts. Same class on macOS/Linux when the inherited $SHELL differs from the login shell the terminal uses, and for a blank configured shell.

Fix: the host resolves the shell once with the terminal's own resolve_shell and uses it both to start the PTY and to pick the activation command; terminal_activation takes the resolved shell and no longer reads the environment. Tests cover PowerShell/cmd paths, blank settings and a host-level run with an unrelated $SHELL. Verified in the app on macOS (default zsh and configured bash); not run on Windows.

Fixes #631

2026-11-01 12:40:03 +08:00

..

src

fix(terminal): activate virtualenvs using the resolved terminal shell (#646)

2026-11-01 12:40:03 +08:00

Cargo.toml

Initial open-source release

2026-10-22 18:55:10 +08:00