pbakaus/impeccable · error
Unknown command: "{other}" To see a list of supported comma
Error message
Unknown command: "{other}"
To see a list of supported commands, run:
impeccable --help
What it means
The CLI's catch-all match arm in run() rejects any first argument that is not a recognized command or a detect target. It prints 'Unknown command: "{other}"' plus a pointer to `impeccable --help` and exits with code 1.
Source
Thrown at crates/cli/src/main.rs:101
.collect()
};
impeccable_comp_verbs::run_build_phase(rest, io, &organic)
}
"hook" => impeccable_hook::run_hook(rest, io, engines().html),
"hook-before-edit" => impeccable_hook::run_hook_before_edit(rest, io, engines().html),
"hooks" | "hook-admin" => impeccable_hook::run_hook_admin(rest, io),
v if v.starts_with("live") => impeccable_live::run(v, rest, io),
// `npx impeccable src/` shorthand: a path-shaped, flag, URL, or existing
// first arg is a detect target (cli.js looksLikeDetectTarget).
v if impeccable_detect::looks_like_detect_target(v, &io.cwd.to_string_lossy()) => {
impeccable_detect::run_detect(args, io, &engines())
}
"init" => {
io.err(impeccable_detect::INIT_MESSAGE);
1
}
other => {
io.err(&format!(
"Unknown command: \"{other}\"\n\nTo see a list of supported commands, run:\n impeccable --help\n"
));
1
}
}
}
/// The npm `impeccable` package version `cli.js --version` prints (its
/// `package.json`), tracked separately from the crate version.
pub const CLI_VERSION: &str = "4.0.0";
/// The engines wired into `impeccable detect`: the static HTML engine
/// (crates/html). The browser engine (crates/browser) plugs in here once it
/// lands; until then URL scans report the puppeteer message.
fn engines() -> impeccable_detect::Engines<'static> {
static HTML: impeccable_html::StaticHtmlEngine = impeccable_html::StaticHtmlEngine {
// The shipped binary carries the built-in rules only.
static_rule_pack: None,View on GitHub (pinned to 2bc2879276)
Solutions
- Run `impeccable --help` to list supported terminal commands
- Check the spelling of the subcommand
- Confirm the command is a CLI verb and not an agent-chat skill verb; skill verbs like `init` run inside your AI coding agent
- Update to the latest CLI version if the subcommand is newer than your install
Example fix
// before $ impeccable buld-phase status // after $ impeccable build-phase status
Defensive patterns
Strategy: validation
Validate before calling
impeccable --help | grep -q "^ $cmd\b" || echo "unknown command: $cmd"
Try / catch
out=$(impeccable "$cmd" 2>&1) || { case "$out" in "Unknown command"*) impeccable --help;; esac; } Prevention
- Run impeccable --help before trying an unfamiliar subcommand
- Verify the verb is a CLI command, not an agent-only skill verb
- Keep the CLI updated so newer subcommands exist
When it happens
Trigger: Calling `impeccable <anything>` where the first arg is neither a known command, a path/flag/URL-shaped detect target (per impeccable_detect::looks_like_detect_target), nor an existing file.
Common situations: Typos in subcommand names (e.g. `impeccable scna`); invoking verbs that only exist as agent-chat skill verbs (`init`, `build-phase` variants) from the terminal; outdated CLI version missing a newer subcommand.
Related errors
- build-phase: unknown command {other}
- Unknown skills command: {other}
- "init" is not a CLI command. Type /impeccable init in your A
- usage: build-phase.mjs start --comp <png> [--breakpoint WxH]
- build-phase: start needs --comp <approved comp png> (comp al
AI-assisted analysis of pbakaus/impeccable@2bc2879276 (2026-09-08).
Data as JSON: /api/errors/2c72e2d0f93bf681.
Report an issue: GitHub.