Command "{{v}}" not found. Run "spicetify -h" for a list of

Error message

Command "{{v}}" not found.
Run "spicetify -h" for a list of valid commands.

What it means

main() dispatches on the first CLI word via a switch; the default branch fires for any word that is not a registered spicetify command, producing this fatal error before anything else runs.

Source

Thrown at spicetify.go:363

			}

		case "restore":
			cmd.Restore()
			shouldRestart = true

		case "enable-devtools":
			cmd.EnableDevTools()
			shouldRestart = true

		case "restart":
			cmd.SpotifyRestart()

		case "auto":
			cmd.Auto(version)
			shouldRestart = true

		default:
			utils.Fatal(errors.New(`Command "` + v + `" not found.
Run "spicetify -h" for a list of valid commands.`))
		}
	}

	if !noRestart && !slices.Contains(commands, "restart") && shouldRestart {
		cmd.SpotifyRestart()
	}
}

func help() {
	utils.PrintBold("spicetify v" + version)
	log.Println(utils.Bold("USAGE") + "\n" +
		"spicetify [-q] [-e] [-a] \x1B[4mcommand\033[0m...\n" +
		"spicetify {-c | --config} | {-v | --version} | {-h | --help}\n\n" +
		utils.Bold("DESCRIPTION") + "\n" +
		"Customize Spotify client UI and functionality\n\n" +
		utils.Bold("CHAINABLE COMMANDS") + `
backup              Start backup and preprocessing of app files.

View on GitHub (pinned to 1f13f73616)

Solutions

Check spelling of the command
Run `spicetify -h` for the list of valid commands in your installed version
Update spicetify (`spicetify upgrade`) if the command exists only in newer releases

Example fix

// before
spicetify aply
// after
spicetify apply

Defensive patterns

Strategy: validation

Validate before calling

validCommands := []string{"apply", "update", "restore", "backup", "config", "path", "watch", "auto", "version", "-h"}
if !slices.Contains(validCommands, os.Args[1]) {
    fmt.Fprintln(os.Stderr, "unknown command; run spicetify -h")
    os.Exit(1)
}

Prevention

Verify command spelling against `spicetify -h`
Update spicetify if following newer docs than your installed version
Script defensively: check `$?` after spicetify calls

When it happens

Trigger: Running `spicetify <unknown-word>`, e.g. typos like `spicetify aply`, removed/renamed commands like `spicetify update` on older versions, or accidentally passing a bare word where a flag was expected.

Common situations: Typoed commands; following an outdated tutorial where the command was renamed (e.g. `watch`/`backup` changes across versions); shell aliases interfering; invoking a script name instead of a command.

Related errors

AI-assisted analysis of spicetify/cli@1f13f73616 (2026-08-31). Data as JSON: /api/errors/2ace549ef48519c3. Report an issue: GitHub.