[srozen]

When you cd into a project, Codec now activates its uv .venv (after asking once) and shows which tool versions the pane is using: from mise, the other common version managers, or conda. Each command in the Commands sidebar records what it ran with, and Explain passes it to the model.

Screenshots

Going into a project with a .venv: Codec asks at the top of the pane, and the status bar counts what's in effect.

A project with a .venv and seven mise tools, one pinned but not installed: one chip, which opens the list.

Settings › Shell › Project environments: the answers, a project per row, missing ones flagged.

Python environments

• Going into a folder with a .venv, or below one, asks: Always, This Time, Never, or × (not now). Asking first matters because a downloaded folder can ship its own .venv/bin/python.
• Once allowed, the zsh integration activates it on the way in (from a chpwd hook, so cd app && python already uses it) and deactivates it on the way out. It sets VIRTUAL_ENV and PATH as activate would, without touching the prompt. deactivate works and keeps it off until you leave. An environment activated by hand or by mise is left alone. If mise's hook moves the PATH, the environment is put first again at each prompt.
• This Time activates it in that pane only, through a new private key sequence, and remembers nothing.
• Answers live in venv-decisions beside the shell scripts. The shell reads the file and Codec writes it. Settings lists them: switch Activate/Never, forget one, flag projects whose folder or .venv is gone, Remove Missing. Changes reach panes already in the project at their prompt.

Tool versions

• The shell reports a new OSC 6973 toolchain event only when something may have changed: the folder, mise's __MISE_DIFF, or a mise, uv, pyenv, nvm, conda (…) command ran. Toolchain and VersionManagers live in CodecCore.
• mise, while it's active: mise ls --current --json (about 13 ms).
• Otherwise, the files and variables of pyenv, rbenv, nodenv, asdf, nvm, fnm, chruby, read without running them. nvm, fnm and chruby only switch when told, so the version in use is compared with what the project asks for.
• Conda: the active environment, except base.
• A version that isn't installed, or isn't the one asked for, gets a warning. The list offers the manager's install or switch command (mise install, nvm use…), run in the pane.
• The status bar shows a single chip (8 environments). The first version had a chip per tool, which crowded out the folder and the command when a project used many tools.

Testing

• swift build -j 2 --build-tests, swift test -j 2 --skip-build: 542 tests pass. New: ToolchainTests, VersionManagersTests, VenvActivationTests (a real zsh: asking, activating with the cd, This Time, deactivate, environments activated elsewhere, refusing later, reporting only on change), ToolchainUITests (a real pane end to end, Settings, the status bar chip, the Commands heading).
• ARCHS="arm64 x86_64" scripts/build-app.sh release: builds a universal app.
• make screenshots: retaken. The tour uses a stand-in mise, so its images don't depend on the machine.
• Not tried with the real tools other than mise and uv. pyenv, rbenv, nodenv, asdf, nvm, fnm, chruby and conda are covered by fake installs that follow each tool's documented layout. nvm's NVM_BIN path, fnm's per-shell link and FNM_DIR are worth a check on a machine that has them.

🤖 Generated with Claude Code

[ALambot]

🍆