LGUG2Z/komorebi · error
could not find masir, please make sure it is installed befor
Error message
could not find masir, please make sure it is installed before using the --masir flag
What it means
Thrown by komorebic's startup prerequisite checks when the user passed --masir but the `which` lookup cannot locate a masir executable on PATH. It is a guard against silently launching a companion process that does not exist; masir (the bar/companion binary) must be installed separately from komorebi.
Source
Thrown at komorebic/src/main.rs:2380
);
}
let mut ahk: String = String::from("autohotkey.exe");
if let Ok(komorebi_ahk_exe) = std::env::var("KOMOREBI_AHK_EXE")
&& which(&komorebi_ahk_exe).is_ok()
{
ahk = komorebi_ahk_exe;
}
if args.whkd && which("whkd").is_err() {
bail!(
"could not find whkd, please make sure it is installed before using the --whkd flag"
);
}
if args.masir && which("masir").is_err() {
bail!(
"could not find masir, please make sure it is installed before using the --masir flag"
);
}
if args.ahk && which(&ahk).is_err() {
bail!(
"could not find autohotkey, please make sure it is installed before using the --ahk flag"
);
}
let mut buf: PathBuf;
// The komorebi.ps1 shim will only exist in the Path if installed by Scoop
let exec =
if let Ok(output) = Command::new("where.exe").arg("komorebi.ps1").output() {
let stdout = String::from_utf8(output.stdout)?;
match stdout.trim() {
"" => None,View on GitHub (pinned to e0709f02bf)
Solutions
- Install masir (e.g. `winget install LGUG2Z.masir` or via scoop) and ensure it is on PATH
- Remove the --masir flag if masir is not needed
- If masir is installed, verify PATH includes its directory or reinstall it
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at komorebic/src/main.rs:2380 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of LGUG2Z/komorebi@e0709f02bf (2026-09-06).
Data as JSON: /api/errors/60163f1d98115e03.
Report an issue: GitHub.