Running any command against a multi-mount SSH profile used to open with this:
WARNING | SSH profile 'gmo' declares 6 mounts; no mount selected so path
translation is disabled. Pass mount_name explicitly to enable translation.
The advice was impossible to follow. mount_name is only ever passed by the Web (?mount=) and MCP (mount=) surfaces — there is no --mount flag — so every CLI invocation against a multi-mount profile landed there, and a multi-mount profile could never get path translation from the CLI at all. It also fired on commands that never translate a path: squeue, sinfo, gpus and tail build an SSH handle like everything else, so a plain listing opened with a warning about a submission feature it does not use.
srunx now picks the mount from your current directory. Mount local roots are unique per profile and matching is longest-prefix, so the cwd resolves to at most one mount — the same rule that already applied to a positional script path. The remaining "nothing selected" case drops to a debug log.
The fallback is CLI-only. A one-shot CLI process's cwd expresses your intent; a Web app's or MCP server's cwd is an accident of how it was launched, and honouring it there would let identical requests render different remote paths depending on the launch directory. Those surfaces keep explicit mount selection.
Worth knowing before you upgrade: sbatch --profile <multi-mount> run from inside a mount now translates work_dir and log_dir to their remote equivalents, where before it silently did not.
Full Changelog: v4.2.0...v4.2.1