Problem description

I previously asked in #2281 about Ruby's gem command: it can install useful programs but these cannot be accessed by default for a pixi global user. This also affects other tools like npm, e.g. today I wanted to use pixi global to install nodejs then use npm to install anthropic's new claude-code (npm install -g @anthropic-ai/claude-code; claude` from here)- this failed as the npm tools are not available in my path -- but works if I use other package managers. When #2281 was closed it was undoubtably for sound technical reasons, however pixi's current limitation still conflicts with the pixi motto: "Package management made easy".

So the feature request is for a future pixi that can better expose executables reliably from npm and gem in the first instance into the path pixi uses for global tools. I know I can manually symlink things (adding the gem path to the user path at least doesn't work due to how it works, so gem executables are better symlinked directly into ~/.pixi/bin). In my mind some command like:

> gem install pandocomatic
> npm npm install -g @anthropic-ai/claude-code
> pixi global expose add claude -e nodejs
> pixi global expose add pandocomatic -e ruby

I, the user know which tool I installed, and pixi know what the hidden path that gem or npm uses is in its env, so then pixi can symlink (or builds a launcher). This is not automatic (although pixi could automate this at a later date), it just makes our life a bit easier. Thoughts?