Installation trips up on python; `uv` would be nice

[canadaduane]

I'd like to install inside a package (not globally). I tried this:

$ npm install

> @cloi-ai/cloi@1.0.1 postinstall
> node bin/cloi-setup.cjs --auto && (pip install -r bin/requirements.txt || pip3 install -r bin/requirements.txt || echo 'Python requirements installation failed - continuing...') && node bin/ollama-setup.cjs

✅ CLOI history settings already present – nothing to do.
sh: pip: command not found
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try brew install
    xyz, where xyz is the package you are trying to
    install.

... [snip]

added 31 packages, changed 3 packages, and audited 35 packages in 2s

14 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

I guess I don't have pip available, but I have uv. So I wanted to use uv, and I prefixed the postinstall script, like this: uv pip install -r bin/requirements.txt. This didn't work, because I forgot to activate a venv:

$ uv venv .venv
$ source .venv/bin/activate

Finally, npm install works on my system this way.