mbx setup
- Usage:
mbx setup [FLAGS]
Make plain Cargo commands run through mbx.
mbx installs a stable Cargo shim and prints its path. When you pick a mise scope, with a flag or at the prompt, mbx also adds a [wrappers.cargo] entry to that scope's mise configuration, if it has none, and runs mise reshim; this needs mise 2026.8.16 or newer. Without a mise scope, put the shim's directory first on PATH yourself; mbx never edits shell startup files.
mbx also writes check.overrideCommand to rust-analyzer's user rust-analyzer.toml so editor checks run through the shim, unless that file already has check settings of its own.
Flags
--yes— Accept the recommended activation scope without prompting.MISE_CONFIG_FILEnames the scope when it is set. Otherwise, in an activated mise shell, mbx picks the mise config whose tools includemr-boxington, then the nearest project mise config, then the global config; outside one, mbx installs the Cargo shim and edits no mise config. Cannot be combined with--globalor--local.--global— Add mise's Cargo wrapper to the global mise configuration.--local— Add mise's Cargo wrapper to the current project's mise configuration.--status— Check that the Cargo shim and rust-analyzer check command are current.mbx checks what
mbx setupwrites and exits non-zero when any of it is missing or out of date. When a mise scope applies (--global,--local,MISE_CONFIG_FILE, or an activated mise shell), mbx also checks that the scope's config has the[wrappers.cargo]entry thatmbx setupadds. Existing rust-analyzer check settings thatmbx setupdid not write count as a pass.The status does not show which
cargoyour shell runs, and it does not detect mise's nativemr_boxingtonoption.mbx doctorchecks whethercargoonPATHresolves to the shim or mise's Cargo wrapper.--uninstall— Undombx setupfor the selected scope, keeping the Cargo shim.The scope comes from
--global,--local,MISE_CONFIG_FILE, or an activated mise shell, as for--status. mbx removes the[wrappers.cargo]entry thatmbx setupadded to that scope's mise config. For the global scope, or when no mise scope applies, mbx also removes the rust-analyzer check command thatmbx setupwrote. For a project scope, mbx leaves that command for other scopes; remove it withmbx setup --global --uninstall.-h --help— Print help