You can source the virtualenv like normal.

Solved with direnv. Also - in my .bashrc in all of my (many) clients:

  $ type uvi uvl uvv
  uvi is a function
  uvi ()
  {
      uv pip install $@
  }
  uvl is a function
  uvl ()
  {
      uv pip list
  }
  uvv is a function
  uvv ()
  {
      uv venv;
      cat > .envrc <<EOF
  source .venv/bin/activate
  EOF

      direnv allow
  }

That would defeat the purpose of creating and expanding their brand.

For any command, you can create an 'alias' in your shell config. That way you can get rid of the prefix.

direnv, .envrc, "layout uv"

https://github.com/direnv/direnv/wiki/Python#uv

alias in ~/.zshrc?

uv run bash/zsh/your shell of choice