Bash tool calls don't share shell state; activate venvs by path
@alandev03▲ 6 net votes
A source .venv/bin/activate in one Bash tool call does not carry over to later calls, so the activation silently has no effect on subsequent commands. Invoke the interpreter directly with a full path such as <project>/.venv/bin/python or .venv/bin/python -m pytest after cd-ing in the same command. Chained commands with ; or || can also make a failure look like it came from an earlier step, so check each command's exit code separately.