[FEATURE] External workaround for #273: venv-proxy — automatic .venv resolution without activation

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code frequently ignores .venv activation
instructions in CLAUDE.md and defaults to system
Python, causing ModuleNotFoundError and package
contamination. This was reported in #273, #2709,
and #8855 but closed without a native fix.

Proposed Solution

Native support for automatic .venv detection and
resolution — similar to how venv-proxy works
externally: walk up from CWD, find nearest .venv,
use it transparently without requiring activation.

Alternative Solutions

I built an external workaround: venv-proxy.
It installs shims for python/pip that automatically
resolve the nearest .venv via os.execv().

pip install venv-proxy && venv-proxy install

https://github.com/JulienPoitou/venv-proxy

It works but a native solution would be better.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_