Binaries cargo install'd are placed in ~/.cargo/bin (which is in my shell's PATH), but rustup run <toolchain> foo does not search PATH, instead assuming the named executable to be within the named toolchain's bin directory and requiring the full path to successfully run the command. This is a change from the behavior of multirust, which did search PATH for the named command.