diff --git a/.github/workflows/publish-cli.yml b/.github/workflows/publish-cli.yml
index a939addb..ada3a8ee 100644
--- a/.github/workflows/publish-cli.yml
+++ b/.github/workflows/publish-cli.yml
@@ -96,4 +96,4 @@ jobs:
         with:
           submodules: recursive
       - uses: jdx/mise-action@v2
-      - run: gh release edit ${{ github.ref_name }} --draft=false
+      - run: gh release edit ${{ github.ref_name }} --draft=#false
diff --git a/Cargo.lock b/Cargo.lock
index 7bde79f8..c0e4c852 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -268,7 +268,7 @@ dependencies = [
  "heck",
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -304,17 +304,6 @@ dependencies = [
  "windows-sys",
 ]
 
-[[package]]
-name = "contracts"
-version = "0.6.3"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f1d1429e3bd78171c65aa010eabcdf8f863ba3254728dbfb0ad4b1545beac15c"
-dependencies = [
- "proc-macro2",
- "quote",
- "syn 1.0.109",
-]
-
 [[package]]
 name = "core-foundation-sys"
 version = "0.8.7"
@@ -372,7 +361,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "32a2785755761f3ddc1492979ce1e48d2c00d09311c39e4466429188f3dd6501"
 dependencies = [
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -396,7 +385,7 @@ dependencies = [
  "proc-macro2",
  "quote",
  "strsim",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -407,7 +396,7 @@ checksum = "d336a2a514f6ccccaa3e09b02d41d35330c07ddf03a62165fcec10bb561c7806"
 dependencies = [
  "darling_core",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -804,13 +793,14 @@ dependencies = [
 
 [[package]]
 name = "kdl"
-version = "4.7.0"
+version = "6.2.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3a18038fbecda667e7ea2101bdd02af754da5e17ca2887a7649b8f3fa809d8b8"
+checksum = "6d63de1aa3d632a8dd61da7cddfc499e9f88e6265d85bd84002419c3cdd3dc8f"
 dependencies = [
  "miette",
- "nom",
+ "num",
  "thiserror 1.0.69",
+ "winnow",
 ]
 
 [[package]]
@@ -894,7 +884,7 @@ checksum = "23c9b935fbe1d6cbd1dac857b54a688145e2d93f48db36010514d0f612d0ad67"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -940,12 +930,76 @@ version = "0.3.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "61807f77802ff30975e01f4f071c8ba10c022052f98b3294119f3e615d13e5be"
 
+[[package]]
+name = "num"
+version = "0.4.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "35bd024e8b2ff75562e5f34e7f4905839deb4b22955ef5e73d2fea1b9813cb23"
+dependencies = [
+ "num-bigint",
+ "num-complex",
+ "num-integer",
+ "num-iter",
+ "num-rational",
+ "num-traits",
+]
+
+[[package]]
+name = "num-bigint"
+version = "0.4.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a5e44f723f1133c9deac646763579fdb3ac745e418f2a7af9cd0c431da1f20b9"
+dependencies = [
+ "num-integer",
+ "num-traits",
+]
+
+[[package]]
+name = "num-complex"
+version = "0.4.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "73f88a1307638156682bada9d7604135552957b7818057dcef22705b4d509495"
+dependencies = [
+ "num-traits",
+]
+
 [[package]]
 name = "num-conv"
 version = "0.1.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "51d515d32fb182ee37cda2ccdcb92950d6a3c2893aa280e540671c2cd0f3b1d9"
 
+[[package]]
+name = "num-integer"
+version = "0.1.46"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7969661fd2958a5cb096e56c8e1ad0444ac2bbcd0061bd28660485a44879858f"
+dependencies = [
+ "num-traits",
+]
+
+[[package]]
+name = "num-iter"
+version = "0.1.45"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1429034a0490724d0075ebb2bc9e875d6503c3cf69e235a8941aa757d83ef5bf"
+dependencies = [
+ "autocfg",
+ "num-integer",
+ "num-traits",
+]
+
+[[package]]
+name = "num-rational"
+version = "0.4.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f83d14da390562dca69fc84082e73e548e1ad308d24accdedd2720017cb37824"
+dependencies = [
+ "num-bigint",
+ "num-integer",
+ "num-traits",
+]
+
 [[package]]
 name = "num-traits"
 version = "0.2.19"
@@ -1032,7 +1086,7 @@ dependencies = [
  "pest_meta",
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1282,7 +1336,7 @@ checksum = "5a9bf7cf98d04a2b28aead066b7496853d4779c9cc183c440dbac457641e19a0"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1324,7 +1378,7 @@ dependencies = [
  "darling",
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1407,7 +1461,7 @@ dependencies = [
  "proc-macro2",
  "quote",
  "rustversion",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1431,17 +1485,6 @@ version = "3.0.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "b7401a30af6cb5818bb64852270bb722533397edcfc7344954a38f420819ece2"
 
-[[package]]
-name = "syn"
-version = "1.0.109"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
-dependencies = [
- "proc-macro2",
- "quote",
- "unicode-ident",
-]
-
 [[package]]
 name = "syn"
 version = "2.0.96"
@@ -1527,7 +1570,7 @@ checksum = "4fee6c4efc90059e10f81e6d42c60a18f76588c3d74cb83a0b242a2b6c7504c1"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1538,7 +1581,7 @@ checksum = "26afc1baea8a989337eeb52b6e72a039780ce45c3edfcc9c5b9d112feeb173c2"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1659,11 +1702,9 @@ dependencies = [
  "assert_cmd",
  "clap",
  "clap_usage",
- "contracts",
  "ctor",
  "env_logger",
  "exec",
- "heck",
  "indexmap 2.7.0",
  "itertools 0.14.0",
  "kdl",
@@ -1675,7 +1716,6 @@ dependencies = [
  "serde",
  "serde_json",
  "serde_with",
- "strum",
  "tera",
  "thiserror 2.0.11",
  "usage-lib",
@@ -1775,7 +1815,7 @@ dependencies = [
  "log",
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
  "wasm-bindgen-shared",
 ]
 
@@ -1797,7 +1837,7 @@ checksum = "30d7a95b763d3c45903ed6c81f156801839e5ee968bb07e534c44df0fcd330c2"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
  "wasm-bindgen-backend",
  "wasm-bindgen-shared",
 ]
@@ -1884,7 +1924,7 @@ checksum = "9107ddc059d5b6fbfbffdfa7a7fe3e22a226def0b2608f72e9d552763d3e1ad7"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1895,7 +1935,7 @@ checksum = "29bee4b38ea3cde66011baa44dba677c432a78593e202392d1e9070cf2a7fca7"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
 
 [[package]]
@@ -1980,6 +2020,15 @@ version = "0.52.6"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "589f6da84c646204747d1270a2a5661ea66ed1cced2631d546fdfb155959f9ec"
 
+[[package]]
+name = "winnow"
+version = "0.6.22"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "39281189af81c07ec09db316b302a3e67bf9bd7cbf6c820b50e35fee9c2fa980"
+dependencies = [
+ "memchr",
+]
+
 [[package]]
 name = "xx"
 version = "2.0.3"
@@ -2019,5 +2068,5 @@ checksum = "fa4f8080344d4671fb4e831a13ad1e68092748387dfc4f55e356242fae12ce3e"
 dependencies = [
  "proc-macro2",
  "quote",
- "syn 2.0.96",
+ "syn",
 ]
diff --git a/clap_usage/tests/snapshots/simple__simple.snap b/clap_usage/tests/snapshots/simple__simple.snap
index 697a44da..d6ca2087 100644
--- a/clap_usage/tests/snapshots/simple__simple.snap
+++ b/clap_usage/tests/snapshots/simple__simple.snap
@@ -3,10 +3,10 @@ source: clap_usage/tests/simple.rs
 expression: output
 snapshot_kind: text
 ---
-name "example"
-bin "example"
+name example
+bin example
 usage "Usage: example [OPTIONS]"
-flag "--file" help="some input file" {
-    arg "<FILE>"
+flag --file help="some input file" {
+    arg <FILE>
 }
-flag "--usage"
+flag --usage
diff --git a/cli/Cargo.toml b/cli/Cargo.toml
index 85d24503..3a53b5a2 100644
--- a/cli/Cargo.toml
+++ b/cli/Cargo.toml
@@ -27,13 +27,11 @@ path = "src/lib.rs"
 [dependencies]
 clap = { version = "4", features = ["derive", "string", "env"] }
 clap_usage = { workspace = true }
-contracts = "0.6"
 env_logger = "0.11"
 exec = "0.3"
-heck = "0.5"
 indexmap = "2"
 itertools = "0.14"
-kdl = "= 4.7.0" # upgrade when it supports new miette
+kdl = "6"
 log = "0.4"
 miette = { version = "7", features = ["fancy"] }
 once_cell = "1"
@@ -41,7 +39,6 @@ regex = "1"
 serde = { version = "1", features = ["derive"] }
 serde_json = "1.0"
 serde_with = "3.11"
-strum = { version = "0.26", features = ["derive"] }
 tera = "1"
 thiserror = "2"
 usage-lib = { workspace = true, features = ["clap", "docs"] }
diff --git a/cli/assets/fig.ts b/cli/assets/fig.ts
index 4239e9a9..8fc3b8bd 100644
--- a/cli/assets/fig.ts
+++ b/cli/assets/fig.ts
@@ -84,262 +84,7 @@ const completionGeneratorTemplate = (
 };
 
 const completionSpec: Fig.Spec = {
-  name: "usage",
-  subcommands: [
-    {
-      name: "bash",
-      description: "Executes a bash script",
-      options: [
-        {
-          name: "-h",
-          description: "Show help",
-          isRepeatable: false,
-        },
-        {
-          name: "--help",
-          description: "Show help",
-          isRepeatable: false,
-        },
-      ],
-      args: [
-        {
-          name: "script",
-        },
-        {
-          name: "args",
-          description: "Arguments to pass to script",
-          isOptional: true,
-          isVariadic: true,
-        },
-      ],
-    },
-    {
-      name: ["complete-word", "cw"],
-      options: [
-        {
-          name: "--shell",
-          isRepeatable: false,
-          args: {
-            name: "shell",
-            suggestions: ["bash", "fish", "zsh"],
-          },
-        },
-        {
-          name: ["-f", "--file"],
-          description: "Usage spec file or script with usage shebang",
-          isRepeatable: false,
-          args: {
-            name: "file",
-            template: "filepaths",
-          },
-        },
-        {
-          name: ["-s", "--spec"],
-          description: "Raw string spec input",
-          isRepeatable: false,
-          args: {
-            name: "spec",
-          },
-        },
-        {
-          name: "--cword",
-          description: "Current word index",
-          isRepeatable: false,
-          args: {
-            name: "cword",
-          },
-        },
-      ],
-      args: {
-        name: "words",
-        description: "User's input from the command line",
-        isOptional: true,
-        isVariadic: true,
-      },
-    },
-    {
-      name: ["generate", "g"],
-      subcommands: [
-        {
-          name: ["completion", "c"],
-          options: [
-            {
-              name: "--cache-key",
-              description:
-                "A cache key to use for storing the results of calling the CLI with --usage-cmd",
-              isRepeatable: false,
-              args: {
-                name: "cache_key",
-              },
-            },
-            {
-              name: ["-f", "--file"],
-              description:
-                "A .usage.kdl spec file to use for generating completions",
-              isRepeatable: false,
-              args: {
-                name: "file",
-                template: "filepaths",
-              },
-            },
-            {
-              name: "--usage-bin",
-              description:
-                "Override the bin used for calling back to usage-cli",
-              isRepeatable: false,
-              args: {
-                name: "usage_bin",
-              },
-            },
-            {
-              name: "--usage-cmd",
-              description:
-                'A command which generates a usage spec e.g.: `mycli --usage` or `mycli completion usage` Defaults to "$bin --usage"',
-              isRepeatable: false,
-              args: {
-                name: "usage_cmd",
-              },
-            },
-            {
-              name: "--include-bash-completion-lib",
-              description: "Include https://github.com/scop/bash-completion",
-              isRepeatable: false,
-            },
-          ],
-          args: [
-            {
-              name: "shell",
-              suggestions: ["bash", "fish", "zsh"],
-            },
-            {
-              name: "bin",
-              description: "The CLI which we're generates completions for",
-            },
-          ],
-        },
-        {
-          name: "fig",
-          options: [
-            {
-              name: ["-f", "--file"],
-              description: "A usage spec taken in as a file",
-              isRepeatable: false,
-              args: {
-                name: "file",
-                template: "filepaths",
-              },
-            },
-            {
-              name: "--spec",
-              description: "Raw string spec input",
-              isRepeatable: false,
-              args: {
-                name: "spec",
-              },
-            },
-            {
-              name: "--out-file",
-              description: "File on where to save the generated Fig spec",
-              isRepeatable: false,
-              args: {
-                name: "out_file",
-                template: "filepaths",
-              },
-            },
-          ],
-        },
-        {
-          name: "json",
-          description: "Outputs a usage spec in json format",
-          options: [
-            {
-              name: ["-f", "--file"],
-              description: "A usage spec taken in as a file",
-              isRepeatable: false,
-              args: {
-                name: "file",
-                template: "filepaths",
-              },
-            },
-            {
-              name: "--spec",
-              description: "Raw string spec input",
-              isRepeatable: false,
-              args: {
-                name: "spec",
-              },
-            },
-          ],
-        },
-        {
-          name: ["markdown", "md"],
-          options: [
-            {
-              name: ["-f", "--file"],
-              description: "A usage spec taken in as a file",
-              isRepeatable: false,
-              args: {
-                name: "file",
-                template: "filepaths",
-              },
-            },
-            {
-              name: ["-m", "--multi"],
-              description: "Render each subcommand as a separate markdown file",
-              isRepeatable: false,
-            },
-            {
-              name: "--url-prefix",
-              description: "Prefix to add to all URLs",
-              isRepeatable: false,
-              args: {
-                name: "url_prefix",
-              },
-            },
-            {
-              name: "--html-encode",
-              description: "Escape HTML in markdown",
-              isRepeatable: false,
-            },
-            {
-              name: "--replace-pre-with-code-fences",
-              isRepeatable: false,
-            },
-            {
-              name: "--out-dir",
-              description: "Output markdown files to this directory",
-              isRepeatable: false,
-              args: {
-                name: "out_dir",
-                template: "folders",
-              },
-            },
-            {
-              name: "--out-file",
-              isRepeatable: false,
-              args: {
-                name: "out_file",
-                template: "filepaths",
-              },
-            },
-          ],
-        },
-      ],
-    },
-  ],
-  options: [
-    {
-      name: "--usage-spec",
-      description: "Outputs a `usage.kdl` spec for this CLI itself",
-      isRepeatable: false,
-    },
-  ],
-  args: {
-    name: "completions",
-    description:
-      "Outputs completions for the specified shell for completing the `usage` CLI itself",
-    isOptional: true,
-  },
+  name: "",
 };
 
 export default completionSpec;
diff --git a/cli/src/cli/bash.rs b/cli/src/cli/bash.rs
index f68a5f97..3cfb3ff2 100644
--- a/cli/src/cli/bash.rs
+++ b/cli/src/cli/bash.rs
@@ -12,7 +12,7 @@ use usage::Spec;
 ///
 /// Typically, this will be called by a script's shebang
 ///
-/// If using `var=true` on args/flags, they will be joined with spaces using `shell_words::join()`
+/// If using `var=#true` on args/flags, they will be joined with spaces using `shell_words::join()`
 /// to properly escape and quote values with spaces in them.
 #[derive(Debug, Args)]
 #[clap(disable_help_flag = true, verbatim_doc_comment)]
diff --git a/cli/tests/complete_word.rs b/cli/tests/complete_word.rs
index 55ac10e6..48d29116 100644
--- a/cli/tests/complete_word.rs
+++ b/cli/tests/complete_word.rs
@@ -68,7 +68,7 @@ fn complete_word_kitchen_sink() {
 #[test]
 fn complete_word_choices() {
     assert_cmd("mise.usage.kdl", &["--", "env", "--shell", ""])
-        .stdout("bash\nfish\nnu\nxonsh\nzsh\n");
+        .stdout("bash\nelvish\nfish\nnu\nxonsh\nzsh\npwsh\n");
 }
 
 #[test]
diff --git a/cli/usage.usage.kdl b/cli/usage.usage.kdl
index 4f98cb25..45700763 100644
--- a/cli/usage.usage.kdl
+++ b/cli/usage.usage.kdl
@@ -1,107 +1,102 @@
-name "usage-cli"
-bin "usage"
+name usage-cli
+bin usage
 version "1.7.4"
 about "CLI for working with usage-based CLIs"
 usage "Usage: usage-cli [OPTIONS] [COMPLETIONS] <COMMAND>"
-flag "--usage-spec" help="Outputs a `usage.kdl` spec for this CLI itself"
-arg "[COMPLETIONS]" help="Outputs completions for the specified shell for completing the `usage` CLI itself" required=false
-cmd "bash" help="Executes a bash script" {
-    long_help r"Executes a bash script
-
-Typically, this will be called by a script's shebang
-
-If using `var=true` on args/flags, they will be joined with spaces using `shell_words::join()`
-to properly escape and quote values with spaces in them."
-    flag "-h" help="show help"
-    flag "--help" help="show help"
-    arg "<SCRIPT>"
-    arg "[ARGS]..." help="arguments to pass to script" required=false var=true
+flag --usage-spec help="Outputs a `usage.kdl` spec for this CLI itself"
+arg "[COMPLETIONS]" help="Outputs completions for the specified shell for completing the `usage` CLI itself" required=#false
+cmd bash help="Executes a bash script" {
+    long_help "Executes a bash script\n\nTypically, this will be called by a script's shebang\n\nIf using `var=#true` on args/flags, they will be joined with spaces using `shell_words::join()`\nto properly escape and quote values with spaces in them."
+    flag -h help="show help"
+    flag --help help="show help"
+    arg <SCRIPT>
+    arg "[ARGS]..." help="arguments to pass to script" required=#false var=#true
 }
-cmd "complete-word" {
-    alias "cw"
-    flag "--shell" {
-        arg "<SHELL>" {
-            choices "bash" "fish" "zsh"
+cmd complete-word {
+    alias cw
+    flag --shell {
+        arg <SHELL> {
+            choices bash fish zsh
         }
     }
     flag "-f --file" help="usage spec file or script with usage shebang" {
-        arg "<FILE>"
+        arg <FILE>
     }
     flag "-s --spec" help="raw string spec input" {
-        arg "<SPEC>"
+        arg <SPEC>
     }
-    flag "--cword" help="current word index" {
-        arg "<CWORD>"
+    flag --cword help="current word index" {
+        arg <CWORD>
     }
-    arg "[WORDS]..." help="user's input from the command line" required=false var=true
+    arg "[WORDS]..." help="user's input from the command line" required=#false var=#true
 }
-cmd "exec" hide=true {
-    alias "x"
-    arg "<COMMAND>" help="command to execute after parsing usage spec"
-    arg "<BIN>" help="path to script to execute"
-    arg "[ARGS]..." help="arguments to pass to script" required=false var=true
+cmd exec hide=#true {
+    alias x
+    arg <COMMAND> help="command to execute after parsing usage spec"
+    arg <BIN> help="path to script to execute"
+    arg "[ARGS]..." help="arguments to pass to script" required=#false var=#true
 }
-cmd "generate" subcommand_required=true {
-    alias "g"
-    cmd "completion" {
-        alias "c"
-        alias "complete" "completions" hide=true
-        flag "--cache-key" help="A cache key to use for storing the results of calling the CLI with --usage-cmd" {
-            arg "<CACHE_KEY>"
+cmd generate subcommand_required=#true {
+    alias g
+    cmd completion {
+        alias c
+        alias complete completions hide=#true
+        flag --cache-key help="A cache key to use for storing the results of calling the CLI with --usage-cmd" {
+            arg <CACHE_KEY>
         }
         flag "-f --file" help="A .usage.kdl spec file to use for generating completions" {
-            arg "<FILE>"
+            arg <FILE>
         }
-        flag "--usage-bin" help="Override the bin used for calling back to usage-cli" {
+        flag --usage-bin help="Override the bin used for calling back to usage-cli" {
             long_help "Override the bin used for calling back to usage-cli\n\nYou may need to set this if you have a different bin named \"usage\""
-            arg "<USAGE_BIN>"
+            arg <USAGE_BIN>
         }
-        flag "--usage-cmd" help="A command which generates a usage spec e.g.: `mycli --usage` or `mycli completion usage` Defaults to \"$bin --usage\"" {
-            arg "<USAGE_CMD>"
+        flag --usage-cmd help="A command which generates a usage spec e.g.: `mycli --usage` or `mycli completion usage` Defaults to \"$bin --usage\"" {
+            arg <USAGE_CMD>
         }
-        flag "--include-bash-completion-lib" help="Include https://github.com/scop/bash-completion" {
+        flag --include-bash-completion-lib help="Include https://github.com/scop/bash-completion" {
             long_help "Include https://github.com/scop/bash-completion\n\nThis is required for usage completions to work in bash, but the user may already provide it"
         }
-        arg "<SHELL>" {
-            choices "bash" "fish" "zsh"
+        arg <SHELL> {
+            choices bash fish zsh
         }
-        arg "<BIN>" help="The CLI which we're generates completions for"
+        arg <BIN> help="The CLI which we're generates completions for"
     }
-    cmd "fig" {
+    cmd fig {
         flag "-f --file" help="A usage spec taken in as a file" {
-            arg "<FILE>"
+            arg <FILE>
         }
-        flag "--spec" help="raw string spec input" {
-            arg "<SPEC>"
+        flag --spec help="raw string spec input" {
+            arg <SPEC>
         }
-        flag "--out-file" help="File on where to save the generated Fig spec" {
-            arg "<OUT_FILE>"
+        flag --out-file help="File on where to save the generated Fig spec" {
+            arg <OUT_FILE>
         }
     }
-    cmd "json" help="Outputs a usage spec in json format" {
+    cmd json help="Outputs a usage spec in json format" {
         flag "-f --file" help="A usage spec taken in as a file" {
-            arg "<FILE>"
+            arg <FILE>
         }
-        flag "--spec" help="raw string spec input" {
-            arg "<SPEC>"
+        flag --spec help="raw string spec input" {
+            arg <SPEC>
         }
     }
-    cmd "markdown" {
-        alias "md"
-        flag "-f --file" help="A usage spec taken in as a file" required=true {
-            arg "<FILE>"
+    cmd markdown {
+        alias md
+        flag "-f --file" help="A usage spec taken in as a file" required=#true {
+            arg <FILE>
         }
         flag "-m --multi" help="Render each subcommand as a separate markdown file"
-        flag "--url-prefix" help="Prefix to add to all URLs" {
-            arg "<URL_PREFIX>"
+        flag --url-prefix help="Prefix to add to all URLs" {
+            arg <URL_PREFIX>
         }
-        flag "--html-encode" help="Escape HTML in markdown"
-        flag "--replace-pre-with-code-fences"
-        flag "--out-dir" help="Output markdown files to this directory" {
-            arg "<OUT_DIR>"
+        flag --html-encode help="Escape HTML in markdown"
+        flag --replace-pre-with-code-fences
+        flag --out-dir help="Output markdown files to this directory" {
+            arg <OUT_DIR>
         }
-        flag "--out-file" {
-            arg "<OUT_FILE>"
+        flag --out-file {
+            arg <OUT_FILE>
         }
     }
 }
diff --git a/cliff.toml b/cliff.toml
index 680b9d4c..d88295ba 100644
--- a/cliff.toml
+++ b/cliff.toml
@@ -39,9 +39,9 @@ body = """
         {% endif -%}
     {% endfor -%}
 {% endfor %}
-{% if github.contributors | filter(attribute="is_first_time", value=true) | length != 0 -%}
+{% if github.contributors | filter(attribute="is_first_time", value=#true) | length != 0 -%}
 ### New Contributors
-{% for contributor in github.contributors | filter(attribute="is_first_time", value=true) %}
+{% for contributor in github.contributors | filter(attribute="is_first_time", value=#true) %}
   - @{{ contributor.username }} made their first contribution
     {%- if contributor.pr_number %} in \
       [#{{ contributor.pr_number }}]($REPO/pull/{{ contributor.pr_number }})\
@@ -67,7 +67,7 @@ footer = """
 # remove the leading and trailing whitespace from the template
 trim = true
 postprocessors = [
-  { pattern = '\$REPO', replace = "https://github.com/jdx/usage" },
+    { pattern = '\$REPO', replace = "https://github.com/jdx/usage" },
 ]
 
 [git]
@@ -79,31 +79,31 @@ filter_unconventional = false
 split_commits = false
 # regex for preprocessing the commit messages
 commit_preprocessors = [
-  # remove PR labels from commits
-  { pattern = '\(#([0-9]+)\)', replace = "" },
-  # Check spelling of the commit with https://github.com/crate-ci/typos
-  # If the spelling is incorrect, it will be automatically fixed.
-  #{ pattern = '.*', replace_command = 'typos --write-changes -' },
+    # remove PR labels from commits
+    { pattern = '\(#([0-9]+)\)', replace = "" },
+    # Check spelling of the commit with https://github.com/crate-ci/typos
+    # If the spelling is incorrect, it will be automatically fixed.
+    #{ pattern = '.*', replace_command = 'typos --write-changes -' },
 ]
 # regex for parsing and grouping commits
 commit_parsers = [
-  { message = '^chore\(release\): prepare for', skip = true },
-  { message = '^chore\(pr\)', skip = true },
-  { message = '^chore\(pull\)', skip = true },
-  { message = '^chore: (release|Release)', skip = true },
-  { message = '^Release', skip = true },
-  { message = "^Merge commit", skip = true },
-  { body = '.*security', group = "<!-- 08 -->🛡️ Security" },
-  { message = '^(chore|fix)\(deps\):', group = "<!-- 99 -->📦️ Dependency Updates", scope = "" },
-  { message = '^feat', group = "<!-- 00 -->🚀 Features" },
-  { message = '^fix', group = "<!-- 01 -->🐛 Bug Fixes" },
-  { message = '^refactor', group = "<!-- 02 -->🚜 Refactor" },
-  { message = '^doc', group = "<!-- 03 -->📚 Documentation" },
-  { message = '^style', group = "<!-- 05 -->🎨 Styling" },
-  { message = '^perf', group = "<!-- 04 -->⚡ Performance" },
-  { message = '^test', group = "<!-- 06 -->🧪 Testing" },
-  { message = '^revert', group = "<!-- 09 -->◀️ Revert" },
-  { message = '.', group = "<!-- 10 -->🔍 Other Changes" },
+    { message = '^chore\(release\): prepare for', skip = true },
+    { message = '^chore\(pr\)', skip = true },
+    { message = '^chore\(pull\)', skip = true },
+    { message = '^chore: (release|Release)', skip = true },
+    { message = '^Release', skip = true },
+    { message = "^Merge commit", skip = true },
+    { body = '.*security', group = "<!-- 08 -->🛡️ Security" },
+    { message = '^(chore|fix)\(deps\):', group = "<!-- 99 -->📦️ Dependency Updates", scope = "" },
+    { message = '^feat', group = "<!-- 00 -->🚀 Features" },
+    { message = '^fix', group = "<!-- 01 -->🐛 Bug Fixes" },
+    { message = '^refactor', group = "<!-- 02 -->🚜 Refactor" },
+    { message = '^doc', group = "<!-- 03 -->📚 Documentation" },
+    { message = '^style', group = "<!-- 05 -->🎨 Styling" },
+    { message = '^perf', group = "<!-- 04 -->⚡ Performance" },
+    { message = '^test', group = "<!-- 06 -->🧪 Testing" },
+    { message = '^revert', group = "<!-- 09 -->◀️ Revert" },
+    { message = '.', group = "<!-- 10 -->🔍 Other Changes" },
 ]
 # protect breaking changes from being skipped due to matching a skipping commit_parser
 protect_breaking_commits = false
diff --git a/docs/cli/reference/bash.md b/docs/cli/reference/bash.md
index ce45dced..2752892e 100644
--- a/docs/cli/reference/bash.md
+++ b/docs/cli/reference/bash.md
@@ -7,7 +7,7 @@ Executes a bash script
 
 Typically, this will be called by a script's shebang
 
-If using `var=true` on args/flags, they will be joined with spaces using `shell_words::join()`
+If using `var=#true` on args/flags, they will be joined with spaces using `shell_words::join()`
 to properly escape and quote values with spaces in them.
 
 ## Arguments
diff --git a/docs/cli/reference/commands.json b/docs/cli/reference/commands.json
index 472928ab..fcfc3b8c 100644
--- a/docs/cli/reference/commands.json
+++ b/docs/cli/reference/commands.json
@@ -53,7 +53,7 @@
         "mounts": [],
         "hide": false,
         "help": "Executes a bash script",
-        "help_long": "Executes a bash script\n\nTypically, this will be called by a script's shebang\n\nIf using `var=true` on args/flags, they will be joined with spaces using `shell_words::join()`\nto properly escape and quote values with spaces in them.",
+        "help_long": "Executes a bash script\n\nTypically, this will be called by a script's shebang\n\nIf using `var=#true` on args/flags, they will be joined with spaces using `shell_words::join()`\nto properly escape and quote values with spaces in them.",
         "name": "bash",
         "aliases": [],
         "hidden_aliases": [],
diff --git a/docs/cli/scripts.md b/docs/cli/scripts.md
index 4f6a53fa..663438fb 100644
--- a/docs/cli/scripts.md
+++ b/docs/cli/scripts.md
@@ -55,9 +55,9 @@ fs.appendFileSync(usage_file, `Hello, ${user}\n`);
 
 ## Shell Escaping
 
-### `var=true`
+### `var=#true`
 
-When using `var=true`, the value will be a single string (because that's all env vars can do)
+When using `var=#true`, the value will be a single string (because that's all env vars can do)
 delimited
 by spaces. If an arg itself has a space, then it will have quotes around it. This logic is handled
 by [`shell_words::join()`](https://docs.rs/shell-words/latest/shell_words/fn.join.html). For now,
diff --git a/docs/spec/index.md b/docs/spec/index.md
index ef23c549..dd8385d5 100644
--- a/docs/spec/index.md
+++ b/docs/spec/index.md
@@ -1,7 +1,8 @@
 # Usage Specification
 
 Usage is a spec and CLI for defining CLI tools. Arguments, flags, environment variables, and config
-files can all be defined in a Usage spec. It can be thought of like [OpenAPI (swagger)](https://www.openapis.org/)
+files can all be defined in a Usage spec. It can be thought of
+like [OpenAPI (swagger)](https://www.openapis.org/)
 for CLIs. Here are some potential reasons for defining your CLI with a Usage spec:
 
 - Generate autocompletion scripts
@@ -41,8 +42,8 @@ arg "[file]" help="The file to read"     # optional positional argument
 And here is an example CLI with nested subcommands:
 
 ```sh
-flag "-v --verbose" "Enable verbose logging" global=true count=true
-flag "-q --quiet" "Enable quiet logging" global=true
+flag "-v --verbose" "Enable verbose logging" global=#true count=#true
+flag "-q --quiet" "Enable quiet logging" global=#true
 flag "-u --user <user>" help="User to run as"
 
 cmd "update" help="Update the CLI"
@@ -56,7 +57,7 @@ cmd "config" help="Manage the CLI config" {
   }
   cmd "remove" help="Remove a thing" {
     alias "rm"
-    alias "delete" hide=true # hide alias from docs and completions
+    alias "delete" hide=#true # hide alias from docs and completions
     arg "<name>" help="The name of the thing"
   }
   cmd "list" help="List all things"
@@ -68,7 +69,7 @@ cmd "help" help="Print the CLI help"
 Flags/args can be backed by config files, environment variables, or defaults:
 
 ```sh
-config_file ".mycli.toml" findup=true
+config_file ".mycli.toml" findup=#true
 flag "-u --user <user>" help="User to run as" env="MYCLI_USER" config="settings.user" default="admin"
 ```
 
diff --git a/docs/spec/reference/arg.md b/docs/spec/reference/arg.md
index 8be1ac29..ef2d6aa1 100644
--- a/docs/spec/reference/arg.md
+++ b/docs/spec/reference/arg.md
@@ -7,10 +7,10 @@ arg "[file]"                             # optional positional arg
 arg "<file>" default="file.txt"          # default value for arg
 arg "<file>" parse="mycli parse-file {}" # parse arg value with external command
 
-arg "[file]" var=true # multiple args can be passed (e.g. mycli file1 file2 file3) (0 or more)
-arg "<file>" var=true # multiple args can be passed (e.g. mycli file1 file2 file3) (1 or more)
-arg "<file>" var=true var_min=3 # at least 3 args must be passed
-arg "<file>" var=true var_max=3 # up to 3 args can be passed
+arg "[file]" var=#true # multiple args can be passed (e.g. mycli file1 file2 file3) (0 or more)
+arg "<file>" var=#true # multiple args can be passed (e.g. mycli file1 file2 file3) (1 or more)
+arg "<file>" var=#true var_min=3 # at least 3 args must be passed
+arg "<file>" var=#true var_max=3 # up to 3 args can be passed
 
 arg "<shell>" {
   choices "bash" "zsh" "fish" # <shell> must be one of the choices
diff --git a/docs/spec/reference/cmd.md b/docs/spec/reference/cmd.md
index 42569239..42f98e95 100644
--- a/docs/spec/reference/cmd.md
+++ b/docs/spec/reference/cmd.md
@@ -4,11 +4,11 @@
 # aliases
 cmd "config" help="Manage the CLI config" {
   alias "cfg" "cf" "cg"  # aliases for the command
-  alias "conf" hide=true # hide alias from docs and completions
+  alias "conf" hide=#true # hide alias from docs and completions
 }
 
-cmd "config" hide=true # hide command from docs and completions
-cmd "config" subcommand_required=true # subcommand is not optional
+cmd "config" hide=#true # hide command from docs and completions
+cmd "config" subcommand_required=#true # subcommand is not optional
 
 # these are shown under -h
 cmd "config" before_help="shown before the command"
@@ -44,14 +44,18 @@ cmd "list" {
 
 ## Mounting dynamic commands
 
-A usage spec can define a command to run which emits extra usage spec which will be merged into the cmd.
-For example, assume a CLI named `mycli` has a command `run` which executes a set of tasks, those tasks
-are themselves commands which have their own sets of args/flags dynamically generated. To support this,
+A usage spec can define a command to run which emits extra usage spec which will be merged into the
+cmd.
+For example, assume a CLI named `mycli` has a command `run` which executes a set of tasks, those
+tasks
+are themselves commands which have their own sets of args/flags dynamically generated. To support
+this,
 create a hidden command like `mycli mount-usage-tasks` which emits usage spec for the tasks. Then,
-create a `mount` on the `run` command. Here is the static usage spec for the `mycli` CLI as described:
+create a `mount` on the `run` command. Here is the static usage spec for the `mycli` CLI as
+described:
 
 ```sh
-cmd "mount-usage-tasks" hide=true
+cmd "mount-usage-tasks" hide=#true
 cmd "run" {
 	mount run="mycli mount-usage-tasks"
 }
diff --git a/docs/spec/reference/complete.md b/docs/spec/reference/complete.md
index d5a17ceb..743597a6 100644
--- a/docs/spec/reference/complete.md
+++ b/docs/spec/reference/complete.md
@@ -7,13 +7,14 @@ complete "plugin" run="mycli plugins list"
 
 ## Descriptions
 
-If you set `descriptions=true`, you can provide descriptions for the completions:
+If you set `descriptions=#true`, you can provide descriptions for the completions:
 
 ```sh
-complete "plugin" run="mycli plugins list" descriptions=true
+complete "plugin" run="mycli plugins list" descriptions=#true
 ```
 
-Results will be split on ":" with the first part being the completion value and the second part being the description, e.g.:
+Results will be split on ":" with the first part being the completion value and the second part
+being the description, e.g.:
 
 ```
 user:User's full name
diff --git a/docs/spec/reference/config.md b/docs/spec/reference/config.md
index 4427bdb2..e86eaabd 100644
--- a/docs/spec/reference/config.md
+++ b/docs/spec/reference/config.md
@@ -24,16 +24,16 @@ config {
     file "~/.config/mycli.json"
 
     // local
-    file ".config/mycli.toml" findup=true
-    file ".config/mycli.json" findup=true
-    file ".mycli.dist.toml" findup=true
-    file ".mycli.dist.json" findup=true
-    file ".mycli.toml" findup=true
-    file ".mycli.json" findup=true
-    file ".myclirc" findup=true format="ini"
+    file ".config/mycli.toml" findup=#true
+    file ".config/mycli.json" findup=#true
+    file ".mycli.dist.toml" findup=#true
+    file ".mycli.dist.json" findup=#true
+    file ".mycli.toml" findup=#true
+    file ".mycli.json" findup=#true
+    file ".myclirc" findup=#true format="ini"
 
     // e.g.: .mycli.dev.toml, .mycli.prod.toml
-    file ".mycli.$MYCLI_ENV.toml" findup=true
+    file ".mycli.$MYCLI_ENV.toml" findup=#true
 
     default "user" "admin"
     default "work_dir" "/tmp"
@@ -48,6 +48,6 @@ config {
 Config keys can be aliased to other keys. This is useful for backwards compatibility.
 
 ```kdl
-config_file ".mycli.toml" findup=true
+config_file ".mycli.toml" findup=#true
 config_alias "user" "username"
 ```
diff --git a/docs/spec/reference/flag.md b/docs/spec/reference/flag.md
index e1cff696..65b5d7a6 100644
--- a/docs/spec/reference/flag.md
+++ b/docs/spec/reference/flag.md
@@ -6,15 +6,15 @@ flag "--user" { # another way to define the same flag
   alias "-u"
   arg "<user>"
 }
-flag "--user" { alias "-u" hide=true } # hide alias from docs and completions
+flag "--user" { alias "-u" hide=#true } # hide alias from docs and completions
 
-flag "-f --force" global=true           # global can be set on any subcommand
+flag "-f --force" global=#true           # global can be set on any subcommand
 flag "--file <file>" default="file.txt" # default value for flag
-flag "-v --verbose" count=true          # instead of true/false $usage_verbose is # of times
+flag "-v --verbose" count=#true          # instead of true/false $usage_verbose is # of times
                                         # flag was used (e.g. -vvv = 3)
 
-flag "--color" negate="--no-color" default=true  # $usage_color=true by default
-                                                 # --no-color will set $usage_color=false
+flag "--color" negate="--no-color" default=#true  # $usage_color=#true by default
+                                                 # --no-color will set $usage_color=#false
 
 flag "--color" env="MYCLI_COLOR" # flag can be backed by an env var
 flag "--color" config="ui.color" # flag can be backed by a config file
diff --git a/examples/basic.usage.kdl b/examples/basic.usage.kdl
index dc1aa862..fec7293a 100644
--- a/examples/basic.usage.kdl
+++ b/examples/basic.usage.kdl
@@ -1,17 +1,17 @@
 cmd "plugins" {
-  cmd "install" {
-    arg "plugin"
-    arg "version"
-    flag "-g --global"
-    flag "-d --dir <dir>"
-  }
-  cmd "install_desc" {
-    arg "plugin_desc"
-    arg "version"
-    flag "-g --global"
-    flag "-d --dir <dir>"
-  }
+    cmd "install" {
+        arg "plugin"
+        arg "version"
+        flag "-g --global"
+        flag "-d --dir <dir>"
+    }
+    cmd "install_desc" {
+        arg "plugin_desc"
+        arg "version"
+        flag "-g --global"
+        flag "-d --dir <dir>"
+    }
 }
 
 complete "plugin" run="echo \"plugin-1\nplugin-2\nplugin-3\""
-complete "plugin_desc" descriptions=true run="echo \"plugin-1:desc\nplugin-2:desc\nplugin-3:desc\""
+complete "plugin_desc" descriptions=#true run="echo \"plugin-1:desc\nplugin-2:desc\nplugin-3:desc\""
diff --git a/examples/docs/MISE_INLINE.md b/examples/docs/MISE_INLINE.md
index 28b679fa..c63a3aee 100644
--- a/examples/docs/MISE_INLINE.md
+++ b/examples/docs/MISE_INLINE.md
@@ -1,5 +1,6 @@
 # `mise`
 
+
 mise is a tool for managing runtime versions. https://github.com/jdx/mise
 
 It's a replacement for tools like nvm, nodenv, rbenv, rvm, chruby, pyenv, etc.
@@ -10,7 +11,15 @@ It is inspired by asdf and uses asdf's plugin ecosystem under the hood:
 https://asdf-vm.com/
 
 
-- **Usage**: `mise [FLAGS] <SUBCOMMAND>`
+- **Usage**: `mise [FLAGS] [TASK] <SUBCOMMAND>`
+
+## Arguments
+
+### `[TASK]`
+
+Task to run.
+
+Shorthand for `mise task run <TASK>`.
 
 ## Global Flags
 
@@ -18,44 +27,63 @@ https://asdf-vm.com/
 
 Change directory before running command
 
-### `-P --profile <PROFILE>`
+### `-E --env... <ENV>`
+
+Set the environment for loading `mise.<ENV>.toml`
+
+### `-j --jobs <JOBS>`
+
+How many jobs to run in parallel [default: 8]
 
-Set the profile (environment)
+### `--raw`
+
+Read/write directly to stdin/stdout/stderr instead of by line
+
+### `-y --yes`
+
+Answer yes to all confirmation prompts
 
 ### `-q --quiet`
 
 Suppress non-error messages
 
+### `--silent`
+
+Suppress all task output and mise non-error messages
+
 ### `-v --verbose...`
 
 Show extra output (use -vv for even more)
 
-### `-y --yes`
+## Flags
 
-Answer yes to all confirmation prompts
+### `--output <OUTPUT>`
+
+### `--no-config`
+
+Do not load any config files
+
+Can also use `MISE_NO_CONFIG=1`
 
 ## `mise activate`
 
-- **Usage**: `mise activate [--shims] [-q --quiet] [SHELL_TYPE]`
+- **Usage**: `mise activate [FLAGS] [SHELL_TYPE]`
+- **Source code**: [`src/cli/activate.rs`](https://github.com/jdx/mise/blob/main/src/cli/activate.rs)
 
 Initializes mise in the current shell session
 
-This should go into your shell's rc file.
+This should go into your shell's rc file or login shell.
 Otherwise, it will only take effect in the current session.
-(e.g. ~/.zshrc, ~/.bashrc)
-
-This is only intended to be used in interactive sessions, not scripts.
-mise is only capable of updating PATH when the prompt is displayed to the user.
-For non-interactive use-cases, use shims instead.
+(e.g. ~/.zshrc, ~/.zprofile, ~/.zshenv, ~/.bashrc, ~/.bash_profile, ~/.profile, ~/.config/fish/config.fish)
 
-Typically this can be added with something like the following:
+Typically, this can be added with something like the following:
 
-    echo 'eval "$(mise activate)"' >> ~/.zshrc
+    echo 'eval "$(mise activate zsh)"' >> ~/.zshrc
 
 However, this requires that "mise" is in your PATH. If it is not, you need to
 specify the full path like this:
 
-    echo 'eval "$(/path/to/mise activate)"' >> ~/.zshrc
+    echo 'eval "$(/path/to/mise activate zsh)"' >> ~/.zshrc
 
 Customize status output with `status` settings.
 
@@ -68,10 +96,12 @@ Shell type to generate the script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 ### Flags
 
@@ -82,10 +112,19 @@ Effectively the same as:
 
     PATH="$HOME/.local/share/mise/shims:$PATH"
 
+`mise activate --shims` does not support all the features of `mise activate`.
+See https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path for more information
+
 #### `-q --quiet`
 
 Suppress non-error messages
 
+#### `--no-hook-env`
+
+Do not automatically call hook-env
+
+This can be helpful for debugging mise. If you run `eval "$(mise activate --no-hook-env)"`, then you can call `mise hook-env` manually which will output the env vars to stdout without actually modifying the environment. That way you can do things like `mise hook-env --trace` to get more information or just see the values that hook-env is outputting.
+
 Examples:
 
     $ eval "$(mise activate bash)"
@@ -97,6 +136,7 @@ Examples:
 
 - **Usage**: `mise alias [-p --plugin <PLUGIN>] [--no-header] <SUBCOMMAND>`
 - **Aliases**: `a`
+- **Source code**: [`src/cli/alias/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/mod.rs)
 
 Manage aliases
 
@@ -113,6 +153,7 @@ Don't show table header
 ## `mise alias get`
 
 - **Usage**: `mise alias get <PLUGIN> <ALIAS>`
+- **Source code**: [`src/cli/alias/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/get.rs)
 
 Show an alias for a plugin
 
@@ -130,13 +171,14 @@ The alias to show
 
 Examples:
 
-   $ mise alias get node lts-hydrogen
-   20.0.0
+    $ mise alias get node lts-hydrogen
+    20.0.0
 
 ## `mise alias ls`
 
-- **Usage**: `mise alias ls [--no-header] [PLUGIN]`
+- **Usage**: `mise alias ls [--no-header] [TOOL]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/alias/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/ls.rs)
 
 List aliases
 Shows the aliases that can be specified.
@@ -144,14 +186,14 @@ These can come from user config or from plugins in `bin/list-aliases`.
 
 For user config, aliases are defined like the following in `~/.config/mise/config.toml`:
 
-    [alias.node]
-    lts = "20.0.0"
+    [alias.node.versions]
+    lts = "22.0.0"
 
 ### Arguments
 
-#### `[PLUGIN]`
+#### `[TOOL]`
 
-Show aliases for <PLUGIN>
+Show aliases for <TOOL>
 
 ### Flags
 
@@ -162,12 +204,13 @@ Don't show table header
 Examples:
 
     $ mise aliases
-    node    lts-hydrogen   20.0.0
+    node  lts-jod      22
 
 ## `mise alias set`
 
 - **Usage**: `mise alias set <ARGS>…`
 - **Aliases**: `add`, `create`
+- **Source code**: [`src/cli/alias/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/set.rs)
 
 Add/update an alias for a plugin
 
@@ -189,12 +232,13 @@ The value to set the alias to
 
 Examples:
 
-    $ mise alias set node lts-hydrogen 18.0.0
+    $ mise alias set node lts-jod 22.0.0
 
 ## `mise alias unset`
 
 - **Usage**: `mise alias unset <PLUGIN> <ALIAS>`
 - **Aliases**: `rm`, `remove`, `delete`, `del`
+- **Source code**: [`src/cli/alias/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/unset.rs)
 
 Clears an alias for a plugin
 
@@ -212,11 +256,12 @@ The alias to remove
 
 Examples:
 
-    $ mise alias unset node lts-hydrogen
+    $ mise alias unset node lts-jod
 
 ## `mise asdf`
 
 - **Usage**: `mise asdf [ARGS]...`
+- **Source code**: [`src/cli/asdf.rs`](https://github.com/jdx/mise/blob/main/src/cli/asdf.rs)
 
 [internal] simulates asdf for plugins that call "asdf" internally
 
@@ -230,6 +275,7 @@ all arguments
 
 - **Usage**: `mise backends <SUBCOMMAND>`
 - **Aliases**: `b`
+- **Source code**: [`src/cli/backends/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/backends/mod.rs)
 
 Manage backends
 
@@ -237,28 +283,44 @@ Manage backends
 
 - **Usage**: `mise backends ls`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/backends/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/backends/ls.rs)
 
 List built-in backends
 
 Examples:
 
     $ mise backends ls
+    aqua
+    asdf
     cargo
+    core
+    dotnet
+    gem
     go
     npm
     pipx
     spm
     ubi
+    vfox
 
 ## `mise bin-paths`
 
-- **Usage**: `mise bin-paths`
+- **Usage**: `mise bin-paths [TOOL@VERSION]...`
+- **Source code**: [`src/cli/bin_paths.rs`](https://github.com/jdx/mise/blob/main/src/cli/bin_paths.rs)
 
 List all the active runtime bin paths
 
+### Arguments
+
+#### `[TOOL@VERSION]...`
+
+Tool(s) to look up
+e.g.: ruby@3
+
 ## `mise cache`
 
 - **Usage**: `mise cache <SUBCOMMAND>`
+- **Source code**: [`src/cli/cache/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/mod.rs)
 
 Manage the mise cache
 
@@ -268,6 +330,7 @@ Run `mise cache` with no args to view the current cache directory.
 
 - **Usage**: `mise cache clear [PLUGIN]...`
 - **Aliases**: `c`
+- **Source code**: [`src/cli/cache/clear.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/clear.rs)
 
 Deletes all cache files in mise
 
@@ -281,6 +344,7 @@ Plugin(s) to clear cache for e.g.: node, python
 
 - **Usage**: `mise cache prune [--dry-run] [-v --verbose...] [PLUGIN]...`
 - **Aliases**: `p`
+- **Source code**: [`src/cli/cache/prune.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/prune.rs)
 
 Removes stale mise cache files
 
@@ -305,7 +369,8 @@ Show pruned files
 
 ## `mise completion`
 
-- **Usage**: `mise completion [SHELL]`
+- **Usage**: `mise completion [--include-bash-completion-lib] [SHELL]`
+- **Source code**: [`src/cli/completion.rs`](https://github.com/jdx/mise/blob/main/src/cli/completion.rs)
 
 Generate shell completions
 
@@ -321,6 +386,15 @@ Shell type to generate completions for
 - `fish`
 - `zsh`
 
+### Flags
+
+#### `--include-bash-completion-lib`
+
+Include the bash completion library in the bash completion script
+
+This is required for completions to work in bash, but it is not included by default
+you may source it separately or enable this flag to include it in the script.
+
 Examples:
 
     $ mise completion bash > /etc/bash_completion.d/mise
@@ -331,6 +405,7 @@ Examples:
 
 - **Usage**: `mise config [--no-header] [-J --json] <SUBCOMMAND>`
 - **Aliases**: `cfg`
+- **Source code**: [`src/cli/config/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/mod.rs)
 
 Manage config files
 
@@ -346,13 +421,18 @@ Output in JSON format
 
 ## `mise config generate`
 
-- **Usage**: `mise config generate [-o --output <OUTPUT>]`
+- **Usage**: `mise config generate [-t --tool-versions <TOOL_VERSIONS>] [-o --output <OUTPUT>]`
 - **Aliases**: `g`
+- **Source code**: [`src/cli/config/generate.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/generate.rs)
 
 [experimental] Generate a mise.toml file
 
 ### Flags
 
+#### `-t --tool-versions <TOOL_VERSIONS>`
+
+Path to a .tool-versions file to import tools from
+
 #### `-o --output <OUTPUT>`
 
 Output to file instead of stdout
@@ -365,6 +445,7 @@ Examples:
 ## `mise config get`
 
 - **Usage**: `mise config get [-f --file <FILE>] [KEY]`
+- **Source code**: [`src/cli/config/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/get.rs)
 
 Display the value of a setting in a mise.toml file
 
@@ -390,6 +471,8 @@ Examples:
 ## `mise config ls`
 
 - **Usage**: `mise config ls [--no-header] [-J --json]`
+- **Aliases**: `list`
+- **Source code**: [`src/cli/config/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/ls.rs)
 
 List config files currently in use
 
@@ -406,12 +489,16 @@ Output in JSON format
 Examples:
 
     $ mise config ls
+    Path                        Tools
+    ~/.config/mise/config.toml  pitchfork
+    ~/src/mise/mise.toml        actionlint, bun, cargo-binstall, cargo:cargo-edit, cargo:cargo-insta
 
 ## `mise config set`
 
 - **Usage**: `mise config set [-f --file <FILE>] [-t --type <TYPE>] <KEY> <VALUE>`
+- **Source code**: [`src/cli/config/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/set.rs)
 
-Display the value of a setting in a mise.toml file
+Set the value of a setting in a mise.toml file
 
 ### Arguments
 
@@ -435,20 +522,27 @@ If not provided, the nearest mise.toml file will be used
 
 **Choices:**
 
+- `infer`
 - `string`
 - `integer`
 - `float`
 - `bool`
+- `list`
 
 Examples:
 
     $ mise config set tools.python 3.12
     $ mise config set settings.always_keep_download true
     $ mise config set env.TEST_ENV_VAR ABC
+    $ mise config set settings.disable_tools --type list node,rust
+
+    # Type for `settings` is inferred
+    $ mise config set settings.jobs 4
 
 ## `mise current`
 
 - **Usage**: `mise current [PLUGIN]`
+- **Source code**: [`src/cli/current.rs`](https://github.com/jdx/mise/blob/main/src/cli/current.rs)
 
 Shows current active and installed runtime versions
 
@@ -462,7 +556,7 @@ and/or version. It's designed to fit into scripts more easily.
 Plugin to show versions of e.g.: ruby, node, cargo:eza, npm:prettier, etc
 
 Examples:
-    
+
     # outputs `.tool-versions` compatible format
     $ mise current
     python 3.11.0 3.10.0
@@ -480,6 +574,7 @@ Examples:
 ## `mise deactivate`
 
 - **Usage**: `mise deactivate`
+- **Source code**: [`src/cli/deactivate.rs`](https://github.com/jdx/mise/blob/main/src/cli/deactivate.rs)
 
 Disable mise for current shell session
 
@@ -492,18 +587,20 @@ Examples:
 ## `mise direnv`
 
 - **Usage**: `mise direnv <SUBCOMMAND>`
+- **Source code**: [`src/cli/direnv/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/mod.rs)
 
 Output direnv function to use mise inside direnv
 
 See https://mise.jdx.dev/direnv.html for more information
 
-Because this generates the legacy files based on currently installed plugins,
+Because this generates the idiomatic files based on currently installed plugins,
 you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change.
+direnv may not know to update environment variables when idiomatic file versions change.
 
 ## `mise direnv envrc`
 
 - **Usage**: `mise direnv envrc`
+- **Source code**: [`src/cli/direnv/envrc.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/envrc.rs)
 
 [internal] This is an internal command that writes an envrc file
 for direnv to consume.
@@ -511,6 +608,7 @@ for direnv to consume.
 ## `mise direnv exec`
 
 - **Usage**: `mise direnv exec`
+- **Source code**: [`src/cli/direnv/exec.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/exec.rs)
 
 [internal] This is an internal command that writes an envrc file
 for direnv to consume.
@@ -518,14 +616,15 @@ for direnv to consume.
 ## `mise direnv activate`
 
 - **Usage**: `mise direnv activate`
+- **Source code**: [`src/cli/direnv/activate.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/activate.rs)
 
 Output direnv function to use mise inside direnv
 
 See https://mise.jdx.dev/direnv.html for more information
 
-Because this generates the legacy files based on currently installed plugins,
+Because this generates the idiomatic files based on currently installed plugins,
 you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change.
+direnv may not know to update environment variables when idiomatic file versions change.
 
 Examples:
 
@@ -535,20 +634,86 @@ Examples:
 
 ## `mise doctor`
 
-- **Usage**: `mise doctor`
+- **Usage**: `mise doctor [-J --json] <SUBCOMMAND>`
 - **Aliases**: `dr`
+- **Source code**: [`src/cli/doctor/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/doctor/mod.rs)
 
 Check mise installation for possible problems
 
+### Flags
+
+#### `-J --json`
+
 Examples:
 
     $ mise doctor
     [WARN] plugin node is not installed
 
+## `mise doctor path`
+
+- **Usage**: `mise doctor path [-f --full]`
+- **Source code**: [`src/cli/doctor/path.rs`](https://github.com/jdx/mise/blob/main/src/cli/doctor/path.rs)
+
+Print the current PATH entries mise is providing
+
+### Flags
+
+#### `-f --full`
+
+Print all entries including those not provided by mise
+
+Examples:
+
+    Get the current PATH entries mise is providing
+    $ mise path
+    /home/user/.local/share/mise/installs/node/24.0.0/bin
+    /home/user/.local/share/mise/installs/rust/1.90.0/bin
+    /home/user/.local/share/mise/installs/python/3.10.0/bin
+
+## `mise en`
+
+- **Usage**: `mise en [-s --shell <SHELL>] [DIR]`
+- **Source code**: [`src/cli/en.rs`](https://github.com/jdx/mise/blob/main/src/cli/en.rs)
+
+[experimental] starts a new shell with the mise environment built from the current configuration
+
+This is an alternative to `mise activate` that allows you to explicitly start a mise session.
+It will have the tools and environment variables in the configs loaded.
+Note that changing directories will not update the mise environment.
+
+### Arguments
+
+#### `[DIR]`
+
+Directory to start the shell in
+
+**Default:** `.`
+
+### Flags
+
+#### `-s --shell <SHELL>`
+
+Shell to start
+
+Defaults to $SHELL
+
+Examples:
+
+    $ mise en .
+    $ node -v
+    v20.0.0
+
+    Skip loading bashrc:
+    $ mise en -s "bash --norc"
+
+    Skip loading zshrc:
+    $ mise en -s "zsh -f"
+
 ## `mise env`
 
-- **Usage**: `mise env [-J --json] [-s --shell <SHELL>] [TOOL@VERSION]...`
+- **Usage**: `mise env [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `e`
+- **Source code**: [`src/cli/env.rs`](https://github.com/jdx/mise/blob/main/src/cli/env.rs)
 
 Exports env vars to activate mise a single time
 
@@ -567,6 +732,14 @@ Tool(s) to use
 
 Output in JSON format
 
+#### `--json-extended`
+
+Output in JSON format with additional information (source, tool)
+
+#### `-D --dotenv`
+
+Output in dotenv format
+
 #### `-s --shell <SHELL>`
 
 Shell type to generate environment variables for
@@ -574,10 +747,12 @@ Shell type to generate environment variables for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 Examples:
 
@@ -588,8 +763,9 @@ Examples:
 
 ## `mise exec`
 
-- **Usage**: `mise exec [FLAGS] [TOOL@VERSION]... [COMMAND]...`
+- **Usage**: `mise exec [FLAGS] [TOOL@VERSION]... [-- COMMAND]...`
 - **Aliases**: `x`
+- **Source code**: [`src/cli/exec.rs`](https://github.com/jdx/mise/blob/main/src/cli/exec.rs)
 
 Execute a command with tool(s) set
 
@@ -607,7 +783,7 @@ The "--" separates runtimes from the commands to pass along to the subprocess.
 
 Tool(s) to start e.g.: node@20 python@3.10
 
-#### `[COMMAND]...`
+#### `[-- COMMAND]...`
 
 Command string to execute (same as --command)
 
@@ -637,23 +813,104 @@ Examples:
     # Run a command in a different directory:
     $ mise x -C /path/to/project node@20 -- node ./app.js
 
+## `mise fmt`
+
+- **Usage**: `mise fmt [-a --all]`
+- **Source code**: [`src/cli/fmt.rs`](https://github.com/jdx/mise/blob/main/src/cli/fmt.rs)
+
+Formats mise.toml
+
+Sorts keys and cleans up whitespace in mise.toml
+
+### Flags
+
+#### `-a --all`
+
+Format all files from the current directory
+
+Examples:
+
+    $ mise fmt
+
 ## `mise generate`
 
 - **Usage**: `mise generate <SUBCOMMAND>`
-- **Aliases**: `g`
+- **Aliases**: `gen`
+- **Source code**: [`src/cli/generate/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/mod.rs)
 
 [experimental] Generate files for various tools/services
 
+## `mise generate bootstrap`
+
+- **Usage**: `mise generate bootstrap [FLAGS]`
+- **Source code**: [`src/cli/generate/bootstrap.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/bootstrap.rs)
+
+[experimental] Generate a script to download+execute mise
+
+This is designed to be used in a project where contributors may not have mise installed.
+
+### Flags
+
+#### `-l --localize`
+
+Sandboxes mise internal directories like MISE_DATA_DIR and MISE_CACHE_DIR into a `.mise` directory in the project
+
+This is necessary if users may use a different version of mise outside the project.
+
+#### `--localized-dir <LOCALIZED_DIR>`
+
+Directory to put localized data into
+
+#### `-V --version <VERSION>`
+
+Specify mise version to fetch
+
+#### `-w --write <WRITE>`
+
+instead of outputting the script to stdout, write to a file and make it executable
+
+Examples:
+
+    $ mise generate bootstrap >./bin/mise
+    $ chmod +x ./bin/mise
+    $ ./bin/mise install – automatically downloads mise to .mise if not already installed
+
+## `mise generate config`
+
+- **Usage**: `mise generate config [-t --tool-versions <TOOL_VERSIONS>] [-o --output <OUTPUT>]`
+- **Aliases**: `g`
+- **Source code**: [`src/cli/generate/config.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/config.rs)
+
+[experimental] Generate a mise.toml file
+
+### Flags
+
+#### `-t --tool-versions <TOOL_VERSIONS>`
+
+Path to a .tool-versions file to import tools from
+
+#### `-o --output <OUTPUT>`
+
+Output to file instead of stdout
+
+Examples:
+
+    $ mise cf generate > mise.toml
+    $ mise cf generate --output=mise.toml
+
 ## `mise generate git-pre-commit`
 
 - **Usage**: `mise generate git-pre-commit [FLAGS]`
 - **Aliases**: `pre-commit`
+- **Source code**: [`src/cli/generate/git_pre_commit.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/git_pre_commit.rs)
 
 [experimental] Generate a git pre-commit hook
 
 This command generates a git pre-commit hook that runs a mise task like `mise run pre-commit`
 when you commit changes to your repository.
 
+Staged files are passed to the task as `STAGED`.
+
 ### Flags
 
 #### `--hook <HOOK>`
@@ -676,6 +933,7 @@ Examples:
 ## `mise generate github-action`
 
 - **Usage**: `mise generate github-action [FLAGS]`
+- **Source code**: [`src/cli/generate/github_action.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/github_action.rs)
 
 [experimental] Generate a GitHub Action workflow file
 
@@ -684,7 +942,7 @@ when you push changes to your repository.
 
 ### Flags
 
-#### `-n --name <NAME>`
+#### `--name <NAME>`
 
 the name of the workflow to generate
 
@@ -705,8 +963,9 @@ Examples:
 ## `mise generate task-docs`
 
 - **Usage**: `mise generate task-docs [FLAGS]`
+- **Source code**: [`src/cli/generate/task_docs.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/task_docs.rs)
 
-[experimental] Generate documentation for tasks in a project
+Generate documentation for tasks in a project
 
 ### Flags
 
@@ -745,9 +1004,39 @@ Examples:
 
     $ mise generate task-docs
 
+## `mise generate task-stubs`
+
+- **Usage**: `mise generate task-stubs [-m --mise-bin <MISE_BIN>] [-d --dir <DIR>]`
+- **Source code**: [`src/cli/generate/task_stubs.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/task_stubs.rs)
+
+[experimental] Generates shims to run mise tasks
+
+By default, this will build shims like ./bin/<task>. These can be paired with `mise generate bootstrap`
+so contributors to a project can execute mise tasks without installing mise into their system.
+
+### Flags
+
+#### `-m --mise-bin <MISE_BIN>`
+
+Path to a mise bin to use when running the task stub.
+
+Use `--mise-bin=./bin/mise` to use a mise bin generated from `mise generate bootstrap`
+
+#### `-d --dir <DIR>`
+
+Directory to create task stubs inside of
+
+Examples:
+
+    $ mise task add test -- echo 'running tests'
+    $ mise generate task-stubs
+    $ ./bin/test
+    running tests
+
 ## `mise global`
 
 - **Usage**: `mise global [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/global.rs`](https://github.com/jdx/mise/blob/main/src/cli/global.rs)
 
 Sets/gets the global tool version(s)
 
@@ -805,7 +1094,8 @@ Examples:
 
 ## `mise hook-env`
 
-- **Usage**: `mise hook-env [-s --shell <SHELL>] [-q --quiet]`
+- **Usage**: `mise hook-env [FLAGS]`
+- **Source code**: [`src/cli/hook_env.rs`](https://github.com/jdx/mise/blob/main/src/cli/hook_env.rs)
 
 [internal] called by activate hook to update env vars directory change
 
@@ -818,10 +1108,16 @@ Shell type to generate script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
+
+#### `-f --force`
+
+Skip early exit check
 
 #### `-q --quiet`
 
@@ -830,6 +1126,7 @@ Hide warnings such as when a tool is not installed
 ## `mise hook-not-found`
 
 - **Usage**: `mise hook-not-found [-s --shell <SHELL>] <BIN>`
+- **Source code**: [`src/cli/hook_not_found.rs`](https://github.com/jdx/mise/blob/main/src/cli/hook_not_found.rs)
 
 [internal] called by shell when a command is not found
 
@@ -848,14 +1145,17 @@ Shell type to generate script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 ## `mise implode`
 
 - **Usage**: `mise implode [--config] [-n --dry-run]`
+- **Source code**: [`src/cli/implode.rs`](https://github.com/jdx/mise/blob/main/src/cli/implode.rs)
 
 Removes mise CLI and all related data
 
@@ -875,6 +1175,7 @@ List directories that would be removed without actually removing them
 
 - **Usage**: `mise install [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `i`
+- **Source code**: [`src/cli/install.rs`](https://github.com/jdx/mise/blob/main/src/cli/install.rs)
 
 Install a tool version
 
@@ -920,9 +1221,35 @@ Examples:
     $ mise install node         # install version specified in mise.toml
     $ mise install              # installs everything specified in mise.toml
 
+## `mise install-into`
+
+- **Usage**: `mise install-into <TOOL@VERSION> <PATH>`
+- **Source code**: [`src/cli/install_into.rs`](https://github.com/jdx/mise/blob/main/src/cli/install_into.rs)
+
+Install a tool version to a specific path
+
+Used for building a tool to a directory for use outside of mise
+
+### Arguments
+
+#### `<TOOL@VERSION>`
+
+Tool to install e.g.: node@20
+
+#### `<PATH>`
+
+Path to install the tool into
+
+Examples:
+
+    # install node@20.0.0 into ./mynode
+    $ mise install-into node@20.0.0 ./mynode && ./mynode/bin/node -v
+    20.0.0
+
 ## `mise latest`
 
 - **Usage**: `mise latest [-i --installed] <TOOL@VERSION>`
+- **Source code**: [`src/cli/latest.rs`](https://github.com/jdx/mise/blob/main/src/cli/latest.rs)
 
 Gets the latest available version for a plugin
 
@@ -952,6 +1279,7 @@ Examples:
 
 - **Usage**: `mise link [-f --force] <TOOL@VERSION> <PATH>`
 - **Aliases**: `ln`
+- **Source code**: [`src/cli/link.rs`](https://github.com/jdx/mise/blob/main/src/cli/link.rs)
 
 Symlinks a tool version into mise
 
@@ -975,7 +1303,7 @@ e.g.: ~/.nvm/versions/node/v20.0.0
 Overwrite an existing tool version if it exists
 
 Examples:
-    
+
     # build node-20.0.0 with node-build and link it into mise
     $ node-build 20.0.0 ~/.nodes/20.0.0
     $ mise link node@20.0.0 ~/.nodes/20.0.0
@@ -988,6 +1316,7 @@ Examples:
 ## `mise local`
 
 - **Usage**: `mise local [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/local.rs`](https://github.com/jdx/mise/blob/main/src/cli/local.rs)
 
 Sets/gets tool version in local .tool-versions or mise.toml
 
@@ -1050,8 +1379,9 @@ Examples:
 
 ## `mise ls`
 
-- **Usage**: `mise ls [FLAGS] [PLUGIN]...`
+- **Usage**: `mise ls [FLAGS] [INSTALLED_TOOL]...`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/ls.rs)
 
 List installed and active tool versions
 
@@ -1063,9 +1393,9 @@ It's a useful command to get the current state of your tools.
 
 ### Arguments
 
-#### `[PLUGIN]...`
+#### `[INSTALLED_TOOL]...`
 
-Only show tool versions from [PLUGIN]
+Only show tool versions from [TOOL]
 
 ### Flags
 
@@ -1081,6 +1411,14 @@ Only show tool versions currently specified in the global mise.toml
 
 Only show tool versions that are installed (Hides tools defined in mise.toml but not installed)
 
+#### `-o --offline`
+
+Don't fetch information such as outdated versions
+
+#### `--outdated`
+
+Display whether a version is outdated
+
 #### `-J --json`
 
 Output in JSON format
@@ -1126,6 +1464,7 @@ Examples:
 ## `mise ls-remote`
 
 - **Usage**: `mise ls-remote [--all] [TOOL@VERSION] [PREFIX]`
+- **Source code**: [`src/cli/ls_remote.rs`](https://github.com/jdx/mise/blob/main/src/cli/ls_remote.rs)
 
 List runtime versions available for install.
 
@@ -1135,7 +1474,7 @@ Note that the results may be cached, run `mise cache clean` to clear the cache a
 
 #### `[TOOL@VERSION]`
 
-Plugin to get versions for
+Tool to get versions for
 
 #### `[PREFIX]`
 
@@ -1165,6 +1504,7 @@ Examples:
 ## `mise outdated`
 
 - **Usage**: `mise outdated [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/outdated.rs`](https://github.com/jdx/mise/blob/main/src/cli/outdated.rs)
 
 Shows outdated tool versions
 
@@ -1215,6 +1555,7 @@ Examples:
 
 - **Usage**: `mise plugins [FLAGS] <SUBCOMMAND>`
 - **Aliases**: `p`
+- **Source code**: [`src/cli/plugins/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/mod.rs)
 
 Manage plugins
 
@@ -1241,6 +1582,7 @@ e.g.: https://github.com/asdf-vm/asdf-nodejs.git
 
 - **Usage**: `mise plugins install [FLAGS] [NEW_PLUGIN] [GIT_URL]`
 - **Aliases**: `i`, `a`, `add`
+- **Source code**: [`src/cli/plugins/install.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/install.rs)
 
 Install a plugin
 
@@ -1294,8 +1636,9 @@ Examples:
 
 ## `mise plugins link`
 
-- **Usage**: `mise plugins link [-f --force] <NAME> [PATH]`
+- **Usage**: `mise plugins link [-f --force] <NAME> [DIR]`
 - **Aliases**: `ln`
+- **Source code**: [`src/cli/plugins/link.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/link.rs)
 
 Symlinks a plugin into mise
 
@@ -1308,7 +1651,7 @@ This is used for developing a plugin.
 The name of the plugin
 e.g.: node, ruby
 
-#### `[PATH]`
+#### `[DIR]`
 
 The local path to the plugin
 e.g.: ./mise-node
@@ -1329,8 +1672,9 @@ Examples:
 
 ## `mise plugins ls`
 
-- **Usage**: `mise plugins ls [FLAGS]`
+- **Usage**: `mise plugins ls [-u --urls]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/plugins/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/ls.rs)
 
 List installed plugins
 
@@ -1338,18 +1682,6 @@ Can also show remotely available plugins to install.
 
 ### Flags
 
-#### `-c --core`
-
-The built-in plugins only
-Normally these are not shown
-
-#### `--user`
-
-List installed plugins
-
-This is the default behavior but can be used with --core
-to show core and user plugins
-
 #### `-u --urls`
 
 Show the git url for each plugin
@@ -1369,6 +1701,7 @@ Examples:
 
 - **Usage**: `mise plugins ls-remote [-u --urls] [--only-names]`
 - **Aliases**: `list-remote`, `list-all`
+- **Source code**: [`src/cli/plugins/ls_remote.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/ls_remote.rs)
 
 
 List all available remote plugins
@@ -1393,6 +1726,7 @@ Only show the name of each plugin by default it will show a "*" next to installe
 
 - **Usage**: `mise plugins uninstall [-p --purge] [-a --all] [PLUGIN]...`
 - **Aliases**: `remove`, `rm`
+- **Source code**: [`src/cli/plugins/uninstall.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/uninstall.rs)
 
 Removes a plugin
 
@@ -1420,6 +1754,7 @@ Examples:
 
 - **Usage**: `mise plugins update [-j --jobs <JOBS>] [PLUGIN]...`
 - **Aliases**: `up`, `upgrade`
+- **Source code**: [`src/cli/plugins/update.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/update.rs)
 
 Updates a plugin to the latest version
 
@@ -1446,20 +1781,21 @@ Examples:
 
 ## `mise prune`
 
-- **Usage**: `mise prune [FLAGS] [PLUGIN]...`
+- **Usage**: `mise prune [FLAGS] [INSTALLED_TOOL]...`
+- **Source code**: [`src/cli/prune.rs`](https://github.com/jdx/mise/blob/main/src/cli/prune.rs)
 
 Delete unused versions of tools
 
-mise tracks which config files have been used in ~/.local/share/mise/tracked_config_files
+mise tracks which config files have been used in ~/.local/state/mise/tracked-configs
 Versions which are no longer the latest specified in any of those configs are deleted.
 Versions installed only with environment variables `MISE_<PLUGIN>_VERSION` will be deleted,
 as will versions only referenced on the command line `mise exec <PLUGIN>@<VERSION>`.
 
 ### Arguments
 
-#### `[PLUGIN]...`
+#### `[INSTALLED_TOOL]...`
 
-Prune only versions from this plugin(s)
+Prune only these tools
 
 ### Flags
 
@@ -1483,14 +1819,31 @@ Examples:
 
 ## `mise registry`
 
-- **Usage**: `mise registry`
+- **Usage**: `mise registry [-b --backend <BACKEND>] [--hide-aliased] [NAME]`
+- **Source code**: [`src/cli/registry.rs`](https://github.com/jdx/mise/blob/main/src/cli/registry.rs)
 
-[experimental] List available tools to install
+List available tools to install
 
 This command lists the tools available in the registry as shorthand names.
 
 For example, `poetry` is shorthand for `asdf:mise-plugins/mise-poetry`.
 
+### Arguments
+
+#### `[NAME]`
+
+Show only the specified tool's full name
+
+### Flags
+
+#### `-b --backend <BACKEND>`
+
+Show only tools for this backend
+
+#### `--hide-aliased`
+
+Hide aliased tools
+
 Examples:
 
     $ mise registry
@@ -1498,9 +1851,13 @@ Examples:
     poetry  asdf:mise-plugins/mise-poetry
     ubi     cargo:ubi-cli
 
+    $ mise registry poetry
+    asdf:mise-plugins/mise-poetry
+
 ## `mise reshim`
 
 - **Usage**: `mise reshim [-f --force]`
+- **Source code**: [`src/cli/reshim.rs`](https://github.com/jdx/mise/blob/main/src/cli/reshim.rs)
 
 Creates new shims based on bin paths from currently installed tools.
 
@@ -1513,10 +1870,10 @@ If you think mise should automatically call this for a particular command, pleas
 open an issue on the mise repo. You can also setup a shell function to reshim
 automatically (it's really fast so you don't need to worry about overhead):
 
-npm() {
-  command npm "$@"
-  mise reshim
-}
+    npm() {
+      command npm "$@"
+      mise reshim
+    }
 
 Note that this creates shims for _all_ installed tools, not just the ones that are
 currently active in mise.toml.
@@ -1537,8 +1894,9 @@ Examples:
 
 - **Usage**: `mise run [FLAGS]`
 - **Aliases**: `r`
+- **Source code**: [`src/cli/run.rs`](https://github.com/jdx/mise/blob/main/src/cli/run.rs)
 
-[experimental] Run task(s)
+Run task(s)
 
 This command will run a tasks, or multiple tasks in parallel.
 Tasks may have dependencies on other tasks or on source files.
@@ -1570,6 +1928,10 @@ The name of the script will be the name of the tasks.
 
 Change to this directory before executing the command
 
+#### `-c --continue-on-error`
+
+Continue running tasks even if one fails
+
 #### `-n --dry-run`
 
 Don't actually run the tasks(s), just print them in order of execution
@@ -1578,21 +1940,17 @@ Don't actually run the tasks(s), just print them in order of execution
 
 Force the tasks to run even if outputs are up to date
 
-#### `-p --prefix`
-
-Print stdout/stderr by line, prefixed with the tasks's label
-Defaults to true if --jobs > 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+#### `-s --shell <SHELL>`
 
-#### `-i --interleave`
+Shell to use to run toml tasks
 
-Print directly to stdout/stderr instead of by line
-Defaults to true if --jobs == 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows
+Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`
+Or it can be overridden with the `shell` property on a task.
 
 #### `-t --tool... <TOOL@VERSION>`
 
-Tool(s) to also add e.g.: node@20 python@3.10
+Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
 
 #### `-j --jobs <JOBS>`
 
@@ -1605,9 +1963,31 @@ Configure with `jobs` config or `MISE_JOBS` env var
 Read/write directly to stdin/stdout/stderr instead of by line
 Configure with `raw` config or `MISE_RAW` env var
 
-#### `--timings`
+#### `--no-timings`
+
+Hides elapsed time after each task completes
 
-Shows elapsed time after each tasks
+Default to always hide with `MISE_TASK_TIMINGS=0`
+
+#### `-q --quiet`
+
+Don't show extra output
+
+#### `-S --silent`
+
+Don't show any output except for errors
+
+#### `-o --output <OUTPUT>`
+
+Change how tasks information is output when running tasks
+
+- `prefix` - Print stdout/stderr by line, prefixed with the task's label
+- `interleave` - Print directly to stdout/stderr instead of by line
+- `replacing` - Stdout is replaced each time, stderr is printed as is
+- `timed` - Only show stdout lines if they are displayed for more than 1 second
+- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output
+- `quiet` - Don't show extra output
+- `silent` - Don't show any output including stdout and stderr from the task except for errors
 
 Examples:
 
@@ -1631,6 +2011,7 @@ Examples:
 ## `mise self-update`
 
 - **Usage**: `mise self-update [FLAGS] [VERSION]`
+- **Source code**: [`src/cli/self_update.rs`](https://github.com/jdx/mise/blob/main/src/cli/self_update.rs)
 
 Updates mise itself.
 
@@ -1662,7 +2043,8 @@ Skip confirmation prompt
 
 ## `mise set`
 
-- **Usage**: `mise set [--file <FILE>] [-g --global] [ENV_VARS]...`
+- **Usage**: `mise set [--file <FILE>] [-g --global] [ENV_VAR]...`
+- **Source code**: [`src/cli/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/set.rs)
 
 Set environment variables in mise.toml
 
@@ -1670,7 +2052,7 @@ By default, this command modifies `mise.toml` in the current directory.
 
 ### Arguments
 
-#### `[ENV_VARS]...`
+#### `[ENV_VAR]...`
 
 Environment variable(s) to set
 e.g.: NODE_ENV=production
@@ -1700,19 +2082,67 @@ Examples:
 
 ## `mise settings`
 
-- **Usage**: `mise settings [--keys] <SUBCOMMAND>`
+- **Usage**: `mise settings [FLAGS] [SETTING] [VALUE] <SUBCOMMAND>`
+- **Source code**: [`src/cli/settings/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/mod.rs)
+
+Show current settings
+
+This is the contents of ~/.config/mise/config.toml
+
+Note that aliases are also stored in this file
+but managed separately with `mise aliases`
+
+### Arguments
+
+#### `[SETTING]`
+
+Name of setting
+
+#### `[VALUE]`
+
+Setting value to set
+
+### Global Flags
+
+#### `-l --local`
 
-Manage settings
+Use the local config file instead of the global one
 
 ### Flags
 
-#### `--keys`
+#### `-a --all`
+
+List all settings
+
+#### `-J --json`
+
+Output in JSON format
+
+#### `--json-extended`
+
+Output in JSON format with sources
 
-Only display key names for each setting
+#### `-T --toml`
+
+Output in TOML format
+
+Examples:
+    # list all settings
+    $ mise settings
+
+    # get the value of the setting "always_keep_download"
+    $ mise settings always_keep_download
+
+    # set the value of the setting "always_keep_download" to "true"
+    $ mise settings always_keep_download=true
+
+    # set the value of the setting "node.mirror_url" to "https://npm.taobao.org/mirrors/node"
+    $ mise settings node.mirror_url https://npm.taobao.org/mirrors/node
 
 ## `mise settings add`
 
-- **Usage**: `mise settings add <SETTING> <VALUE>`
+- **Usage**: `mise settings add [-l --local] <SETTING> <VALUE>`
+- **Source code**: [`src/cli/settings/add.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/add.rs)
 
 Adds a setting to the configuration file
 
@@ -1729,13 +2159,20 @@ The setting to set
 
 The value to set
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
     $ mise settings add disable_hints python_multi
 
 ## `mise settings get`
 
-- **Usage**: `mise settings get <SETTING>`
+- **Usage**: `mise settings get [-l --local] <SETTING>`
+- **Source code**: [`src/cli/settings/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/get.rs)
 
 Show a current setting
 
@@ -1750,15 +2187,22 @@ but managed separately with `mise aliases get`
 
 The setting to show
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings get legacy_version_file
+    $ mise settings get idiomatic_version_file
     true
 
 ## `mise settings ls`
 
-- **Usage**: `mise settings ls [--keys]`
+- **Usage**: `mise settings ls [FLAGS] [SETTING]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/settings/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/ls.rs)
 
 Show current settings
 
@@ -1767,21 +2211,49 @@ This is the contents of ~/.config/mise/config.toml
 Note that aliases are also stored in this file
 but managed separately with `mise aliases`
 
-### Flags
+### Arguments
+
+#### `[SETTING]`
+
+Name of setting
+
+### Flags
+
+#### `-a --all`
+
+List all settings
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
+#### `-J --json`
+
+Output in JSON format
 
-#### `--keys`
+#### `--json-extended`
 
-Only display key names for each setting
+Output in JSON format with sources
+
+#### `-T --toml`
+
+Output in TOML format
 
 Examples:
 
-    $ mise settings
-    legacy_version_file = false
+    $ mise settings ls
+    idiomatic_version_file = false
+    ...
+
+    $ mise settings ls python
+    default_packages_file = "~/.default-python-packages"
+    ...
 
 ## `mise settings set`
 
-- **Usage**: `mise settings set <SETTING> <VALUE>`
+- **Usage**: `mise settings set [-l --local] <SETTING> <VALUE>`
 - **Aliases**: `create`
+- **Source code**: [`src/cli/settings/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/set.rs)
 
 Add/update a setting
 
@@ -1797,14 +2269,21 @@ The setting to set
 
 The value to set
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings set legacy_version_file true
+    $ mise settings idiomatic_version_file=true
 
 ## `mise settings unset`
 
-- **Usage**: `mise settings unset <SETTING>`
+- **Usage**: `mise settings unset [-l --local] <KEY>`
 - **Aliases**: `rm`, `remove`, `delete`, `del`
+- **Source code**: [`src/cli/settings/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/unset.rs)
 
 Clears a setting
 
@@ -1812,18 +2291,25 @@ This modifies the contents of ~/.config/mise/config.toml
 
 ### Arguments
 
-#### `<SETTING>`
+#### `<KEY>`
 
 The setting to remove
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings unset legacy_version_file
+    $ mise settings unset idiomatic_version_file
 
 ## `mise shell`
 
-- **Usage**: `mise shell [FLAGS] [TOOL@VERSION]...`
+- **Usage**: `mise shell [FLAGS] <TOOL@VERSION>...`
 - **Aliases**: `sh`
+- **Source code**: [`src/cli/shell.rs`](https://github.com/jdx/mise/blob/main/src/cli/shell.rs)
 
 Sets a tool version for the current session.
 
@@ -1834,7 +2320,7 @@ such as `MISE_NODE_VERSION=20` which is "eval"ed as a shell function created by
 
 ### Arguments
 
-#### `[TOOL@VERSION]...`
+#### `<TOOL@VERSION>...`
 
 Tool(s) to use
 
@@ -1862,17 +2348,21 @@ Examples:
 ## `mise sync`
 
 - **Usage**: `mise sync <SUBCOMMAND>`
+- **Source code**: [`src/cli/sync/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/mod.rs)
 
-Add tool versions from external tools to mise
+Synchronize tools from other version managers with mise
 
 ## `mise sync node`
 
 - **Usage**: `mise sync node [FLAGS]`
+- **Source code**: [`src/cli/sync/node.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/node.rs)
 
 Symlinks all tool versions from an external tool into mise
 
 For example, use this to import all Homebrew node installs into mise
 
+This won't overwrite any existing installs but will overwrite any existing symlinks
+
 ### Flags
 
 #### `--brew`
@@ -1895,32 +2385,71 @@ Examples:
 
 ## `mise sync python`
 
-- **Usage**: `mise sync python <--pyenv>`
+- **Usage**: `mise sync python [--pyenv] [--uv]`
+- **Source code**: [`src/cli/sync/python.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/python.rs)
 
 Symlinks all tool versions from an external tool into mise
 
 For example, use this to import all pyenv installs into mise
 
+This won't overwrite any existing installs but will overwrite any existing symlinks
+
 ### Flags
 
 #### `--pyenv`
 
 Get tool versions from pyenv
 
+#### `--uv`
+
+Sync tool versions with uv (2-way sync)
+
 Examples:
 
     $ pyenv install 3.11.0
     $ mise sync python --pyenv
     $ mise use -g python@3.11.0 - uses pyenv-provided python
+    
+    $ uv python install 3.11.0
+    $ mise install python@3.10.0
+    $ mise sync python --uv
+    $ mise x python@3.11.0 -- python -V - uses uv-provided python
+    $ uv run -p 3.10.0 -- python -V - uses mise-provided python
+
+## `mise sync ruby`
+
+- **Usage**: `mise sync ruby [--brew]`
+- **Source code**: [`src/cli/sync/ruby.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/ruby.rs)
+
+Symlinks all ruby tool versions from an external tool into mise
+
+### Flags
+
+#### `--brew`
+
+Get tool versions from Homebrew
+
+Examples:
+
+    $ brew install ruby
+    $ mise sync ruby --brew
+    $ mise use -g ruby - Use the latest version of Ruby installed by Homebrew
 
 ## `mise tasks`
 
-- **Usage**: `mise tasks [FLAGS] <SUBCOMMAND>`
+- **Usage**: `mise tasks [FLAGS] [TASK] <SUBCOMMAND>`
 - **Aliases**: `t`
+- **Source code**: [`src/cli/tasks/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/mod.rs)
 
-[experimental] Manage tasks
+Manage tasks
 
-### Flags
+### Arguments
+
+#### `[TASK]`
+
+Task name to get info of
+
+### Global Flags
 
 #### `--no-header`
 
@@ -1962,11 +2491,93 @@ Examples:
 
     $ mise tasks ls
 
+## `mise tasks add`
+
+- **Usage**: `mise tasks add [FLAGS] <TASK> [-- RUN]...`
+- **Source code**: [`src/cli/tasks/add.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/add.rs)
+
+Create a new task
+
+### Arguments
+
+#### `<TASK>`
+
+Tasks name to add
+
+#### `[-- RUN]...`
+
+### Flags
+
+#### `--description <DESCRIPTION>`
+
+Description of the task
+
+#### `-a --alias... <ALIAS>`
+
+Other names for the task
+
+#### `--depends-post... <DEPENDS_POST>`
+
+Dependencies to run after the task runs
+
+#### `-w --wait-for... <WAIT_FOR>`
+
+Wait for these tasks to complete if they are to run
+
+#### `-D --dir <DIR>`
+
+Run the task in a specific directory
+
+#### `-H --hide`
+
+Hide the task from `mise task` and completions
+
+#### `-r --raw`
+
+Directly connect stdin/stdout/stderr
+
+#### `-s --sources... <SOURCES>`
+
+Glob patterns of files this task uses as input
+
+#### `--outputs... <OUTPUTS>`
+
+Glob patterns of files this task creates, to skip if they are not modified
+
+#### `--shell <SHELL>`
+
+Run the task in a specific shell
+
+#### `-q --quiet`
+
+Do not print the command before running
+
+#### `--silent`
+
+Do not print the command or its output
+
+#### `-d --depends... <DEPENDS>`
+
+Add dependencies to the task
+
+#### `--run-windows <RUN_WINDOWS>`
+
+Command to run on windows
+
+#### `-f --file`
+
+Create a file task instead of a toml task
+
+Examples:
+
+    $ mise task add pre-commit --depends "test" --depends "render" -- echo pre-commit
+
 ## `mise tasks deps`
 
 - **Usage**: `mise tasks deps [--hidden] [--dot] [TASKS]...`
+- **Source code**: [`src/cli/tasks/deps.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/deps.rs)
 
-[experimental] Display a tree visualization of a dependency graph
+Display a tree visualization of a dependency graph
 
 ### Arguments
 
@@ -2000,8 +2611,9 @@ Examples:
 ## `mise tasks edit`
 
 - **Usage**: `mise tasks edit [-p --path] <TASK>`
+- **Source code**: [`src/cli/tasks/edit.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/edit.rs)
 
-[experimental] Edit a tasks with $EDITOR
+Edit a tasks with $EDITOR
 
 The tasks will be created as a standalone script if it does not already exist.
 
@@ -2025,8 +2637,9 @@ Examples:
 ## `mise tasks info`
 
 - **Usage**: `mise tasks info [-J --json] <TASK>`
+- **Source code**: [`src/cli/tasks/info.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/info.rs)
 
-[experimental] Get information about a task
+Get information about a task
 
 ### Arguments
 
@@ -2071,8 +2684,9 @@ Examples:
 ## `mise tasks ls`
 
 - **Usage**: `mise tasks ls [FLAGS]`
+- **Source code**: [`src/cli/tasks/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/ls.rs)
 
-[experimental] List available tasks to execute
+List available tasks to execute
 These may be included from the config file or from the project's .mise/tasks directory
 mise will merge all tasks from all parent directories into this list.
 
@@ -2126,8 +2740,9 @@ Examples:
 
 - **Usage**: `mise tasks run [FLAGS] [TASK] [ARGS]...`
 - **Aliases**: `r`
+- **Source code**: [`src/cli/tasks/run.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/run.rs)
 
-[experimental] Run task(s)
+Run task(s)
 
 This command will run a tasks, or multiple tasks in parallel.
 Tasks may have dependencies on other tasks or on source files.
@@ -2173,6 +2788,10 @@ Arguments to pass to the tasks. Use ":::" to separate tasks
 
 Change to this directory before executing the command
 
+#### `-c --continue-on-error`
+
+Continue running tasks even if one fails
+
 #### `-n --dry-run`
 
 Don't actually run the tasks(s), just print them in order of execution
@@ -2181,21 +2800,17 @@ Don't actually run the tasks(s), just print them in order of execution
 
 Force the tasks to run even if outputs are up to date
 
-#### `-p --prefix`
-
-Print stdout/stderr by line, prefixed with the tasks's label
-Defaults to true if --jobs > 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+#### `-s --shell <SHELL>`
 
-#### `-i --interleave`
+Shell to use to run toml tasks
 
-Print directly to stdout/stderr instead of by line
-Defaults to true if --jobs == 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows
+Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`
+Or it can be overridden with the `shell` property on a task.
 
 #### `-t --tool... <TOOL@VERSION>`
 
-Tool(s) to also add e.g.: node@20 python@3.10
+Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
 
 #### `-j --jobs <JOBS>`
 
@@ -2208,9 +2823,31 @@ Configure with `jobs` config or `MISE_JOBS` env var
 Read/write directly to stdin/stdout/stderr instead of by line
 Configure with `raw` config or `MISE_RAW` env var
 
-#### `--timings`
+#### `--no-timings`
+
+Hides elapsed time after each task completes
 
-Shows elapsed time after each tasks
+Default to always hide with `MISE_TASK_TIMINGS=0`
+
+#### `-q --quiet`
+
+Don't show extra output
+
+#### `-S --silent`
+
+Don't show any output except for errors
+
+#### `-o --output <OUTPUT>`
+
+Change how tasks information is output when running tasks
+
+- `prefix` - Print stdout/stderr by line, prefixed with the task's label
+- `interleave` - Print directly to stdout/stderr instead of by line
+- `replacing` - Stdout is replaced each time, stderr is printed as is
+- `timed` - Only show stdout lines if they are displayed for more than 1 second
+- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output
+- `quiet` - Don't show extra output
+- `silent` - Don't show any output including stdout and stderr from the task except for errors
 
 Examples:
 
@@ -2231,9 +2868,99 @@ Examples:
     # Execute multiple tasks each with their own arguments.
     $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2
 
+## `mise test-tool`
+
+- **Usage**: `mise test-tool [FLAGS] [TOOL]`
+- **Source code**: [`src/cli/test_tool.rs`](https://github.com/jdx/mise/blob/main/src/cli/test_tool.rs)
+
+Test a tool installs and executes
+
+### Arguments
+
+#### `[TOOL]`
+
+### Flags
+
+#### `-a --all`
+
+#### `--include-non-defined`
+
+Also test tools not defined in registry.toml, guessing how to test it
+
+#### `-j --jobs <JOBS>`
+
+Number of jobs to run in parallel
+[default: 4]
+
+#### `--raw`
+
+Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1
+
+Examples:
+
+    $ mise test-tool ripgrep
+
+## `mise tool`
+
+- **Usage**: `mise tool [FLAGS] <TOOL>`
+- **Source code**: [`src/cli/tool.rs`](https://github.com/jdx/mise/blob/main/src/cli/tool.rs)
+
+Gets information about a tool
+
+### Arguments
+
+#### `<TOOL>`
+
+Tool name to get information about
+
+### Flags
+
+#### `-J --json`
+
+Output in JSON format
+
+#### `--backend`
+
+Only show backend field
+
+#### `--description`
+
+Only show description field
+
+#### `--installed`
+
+Only show installed versions
+
+#### `--active`
+
+Only show active versions
+
+#### `--requested`
+
+Only show requested versions
+
+#### `--config-source`
+
+Only show config source
+
+#### `--tool-options`
+
+Only show tool options
+
+Examples:
+
+    $ mise tool node
+    Backend:            core
+    Installed Versions: 20.0.0 22.0.0
+    Active Version:     20.0.0
+    Requested Version:  20
+    Config Source:      ~/.config/mise/mise.toml
+    Tool Options:       [none]
+
 ## `mise trust`
 
 - **Usage**: `mise trust [FLAGS] [CONFIG_FILE]`
+- **Source code**: [`src/cli/trust.rs`](https://github.com/jdx/mise/blob/main/src/cli/trust.rs)
 
 Marks a config file as trusted
 
@@ -2257,9 +2984,13 @@ The config file to trust
 
 Trust all config files in the current directory and its parents
 
+#### `--ignore`
+
+Do not trust this config and ignore it in the future
+
 #### `--untrust`
 
-No longer trust this config
+No longer trust this config, will prompt in the future
 
 #### `--show`
 
@@ -2277,7 +3008,7 @@ Examples:
 ## `mise uninstall`
 
 - **Usage**: `mise uninstall [-a --all] [-n --dry-run] [INSTALLED_TOOL@VERSION]...`
-- **Aliases**: `remove`, `rm`
+- **Source code**: [`src/cli/uninstall.rs`](https://github.com/jdx/mise/blob/main/src/cli/uninstall.rs)
 
 Removes installed tool versions
 
@@ -2312,7 +3043,8 @@ Examples:
 
 ## `mise unset`
 
-- **Usage**: `mise unset [-f --file <FILE>] [-g --global] [KEYS]...`
+- **Usage**: `mise unset [-f --file <FILE>] [-g --global] [ENV_KEY]...`
+- **Source code**: [`src/cli/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/unset.rs)
 
 Remove environment variable(s) from the config file.
 
@@ -2320,7 +3052,7 @@ By default, this command modifies `mise.toml` in the current directory.
 
 ### Arguments
 
-#### `[KEYS]...`
+#### `[ENV_KEY]...`
 
 Environment variable(s) to remove
 e.g.: NODE_ENV
@@ -2343,10 +3075,42 @@ Examples:
     # Remove NODE_ENV from the global config
     $ mise unset NODE_ENV -g
 
+## `mise unuse`
+
+- **Usage**: `mise unuse [--no-prune] [--global] <INSTALLED_TOOL@VERSION>...`
+- **Aliases**: `rm`, `remove`
+- **Source code**: [`src/cli/unuse.rs`](https://github.com/jdx/mise/blob/main/src/cli/unuse.rs)
+
+Removes installed tool versions from mise.toml
+
+Will also prune the installed version if no other configurations are using it.
+
+### Arguments
+
+#### `<INSTALLED_TOOL@VERSION>...`
+
+Tool(s) to remove
+
+### Flags
+
+#### `--no-prune`
+
+Do not also prune the installed version
+
+#### `--global`
+
+Remove tool from global config
+
+Examples:
+
+    # will uninstall specific version
+    $ mise remove node@18.0.0
+
 ## `mise upgrade`
 
 - **Usage**: `mise upgrade [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `up`
+- **Source code**: [`src/cli/upgrade.rs`](https://github.com/jdx/mise/blob/main/src/cli/upgrade.rs)
 
 Upgrades outdated tools
 
@@ -2354,6 +3118,8 @@ By default, this keeps the range specified in mise.toml. So if you have node@20
 upgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version
 and bump the version in mise.toml.
 
+This will update mise.lock if it is enabled, see https://mise.jdx.dev/configuration/settings.html#lockfile
+
 ### Arguments
 
 #### `[TOOL@VERSION]...`
@@ -2417,6 +3183,7 @@ Examples:
 ## `mise usage`
 
 - **Usage**: `mise usage`
+- **Source code**: [`src/cli/usage.rs`](https://github.com/jdx/mise/blob/main/src/cli/usage.rs)
 
 Generate a usage CLI spec
 
@@ -2426,12 +3193,19 @@ See https://usage.jdx.dev for more information on this specification.
 
 - **Usage**: `mise use [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `u`
+- **Source code**: [`src/cli/use.rs`](https://github.com/jdx/mise/blob/main/src/cli/use.rs)
 
-Installs a tool and adds the version it to mise.toml.
+Installs a tool and adds the version to mise.toml.
 
 This will install the tool version if it is not already installed.
 By default, this will use a `mise.toml` file in the current directory.
 
+In the following order:
+  - If `MISE_DEFAULT_CONFIG_FILENAME` is set, it will use that instead.
+  - If `MISE_OVERRIDE_CONFIG_FILENAMES` is set, it will the first from that list.
+  - If `MISE_ENV` is set, it will use a `mise.<env>.toml` instead.
+  - Otherwise just "mise.toml"
+
 Use the `--global` flag to use the global config file instead.
 
 ### Arguments
@@ -2443,6 +3217,10 @@ Tool(s) to add to config file
 e.g.: node@20, cargo:ripgrep@latest npm:prettier@3
 If no version is specified, it will default to @latest
 
+Tool options can be set with this syntax:
+
+    mise use ubi:BurntSushi/ripgrep[exe=rg]
+
 ### Flags
 
 #### `-f --force`
@@ -2454,7 +3232,7 @@ Force reinstall even if already installed
 Save fuzzy version to config file
 
 e.g.: `mise use --fuzzy node@20` will save 20 as the version
-this is the default behavior unless `MISE_PIN=1` or `MISE_ASDF_COMPAT=1`
+this is the default behavior unless `MISE_PIN=1`
 
 #### `-g --global`
 
@@ -2462,7 +3240,7 @@ Use the global config file (`~/.config/mise/config.toml`) instead of the local o
 
 #### `-e --env <ENV>`
 
-Modify an environment-specific config file like .mise.<env>.toml
+Create/modify an environment-specific config file like .mise.<env>.toml
 
 #### `-j --jobs <JOBS>`
 
@@ -2481,15 +3259,21 @@ Remove the plugin(s) from config file
 
 Specify a path to a config file or directory
 
-If a directory is specified, it will look for `mise.toml` (default) or `.tool-versions` if `MISE_ASDF_COMPAT=1`
+If a directory is specified, it will look for a config file in that directory following the rules above.
 
 #### `--pin`
 
 Save exact version to config file
 e.g.: `mise use --pin node@20` will save 20.0.0 as the version
-Set `MISE_PIN=1` or `MISE_ASDF_COMPAT=1` to make this the default behavior
+Set `MISE_PIN=1` to make this the default behavior
+
+Consider using mise.lock as a better alternative to pinning in mise.toml:
+https://mise.jdx.dev/configuration/settings.html#lockfile
 
 Examples:
+    
+    # run with no arguments to use the interactive selector
+    $ mise use
 
     # set the current version of node to 20.x in mise.toml of current directory
     # will write the fuzzy version (e.g.: 20)
@@ -2509,6 +3293,7 @@ Examples:
 
 - **Usage**: `mise version`
 - **Aliases**: `v`
+- **Source code**: [`src/cli/version.rs`](https://github.com/jdx/mise/blob/main/src/cli/version.rs)
 
 Display the version of mise
 
@@ -2525,47 +3310,626 @@ Examples:
 
 ## `mise watch`
 
-- **Usage**: `mise watch [-t --task... <TASK>] [-g --glob... <GLOB>] [ARGS]...`
+- **Usage**: `mise watch [FLAGS] [TASK] [ARGS]...`
 - **Aliases**: `w`
+- **Source code**: [`src/cli/watch.rs`](https://github.com/jdx/mise/blob/main/src/cli/watch.rs)
 
-[experimental] Run task(s) and watch for changes to rerun it
+Run task(s) and watch for changes to rerun it
 
 This command uses the `watchexec` tool to watch for changes to files and rerun the specified task(s).
 It must be installed for this command to work, but you can install it with `mise use -g watchexec@latest`.
 
 ### Arguments
 
+#### `[TASK]`
+
+Tasks to run
+Can specify multiple tasks by separating with `:::`
+e.g.: `mise run task1 arg1 arg2 ::: task2 arg1 arg2`
+
 #### `[ARGS]...`
 
-Extra arguments
+Task and arguments to run
 
 ### Flags
 
-#### `-t --task... <TASK>`
+#### `-w --watch... <PATH>`
 
-Tasks to run
+Watch a specific file or directory
+
+By default, Watchexec watches the current directory.
+
+When watching a single file, it's often better to watch the containing directory instead, and filter on the filename. Some editors may replace the file with a new one when saving, and some platforms may not detect that or further changes.
+
+Upon starting, Watchexec resolves a "project origin" from the watched paths. See the help for '--project-origin' for more information.
+
+This option can be specified multiple times to watch multiple files or directories.
+
+The special value '/dev/null', provided as the only path watched, will cause Watchexec to not watch any paths. Other event sources (like signals or key events) may still be used.
+
+#### `-W --watch-non-recursive... <PATH>`
+
+Watch a specific directory, non-recursively
+
+Unlike '-w', folders watched with this option are not recursed into.
+
+This option can be specified multiple times to watch multiple directories non-recursively.
+
+#### `-F --watch-file <PATH>`
+
+Watch files and directories from a file
+
+Each line in the file will be interpreted as if given to '-w'.
+
+For more complex uses (like watching non-recursively), use the argfile capability: build a file containing command-line options and pass it to watchexec with `@path/to/argfile`.
+
+The special value '-' will read from STDIN; this in incompatible with '--stdin-quit'.
+
+#### `-c --clear <MODE>`
+
+Clear screen before running command
+
+If this doesn't completely clear the screen, try '--clear=reset'.
+
+**Choices:**
+
+- `clear`
+- `reset`
+
+#### `-o --on-busy-update <MODE>`
+
+What to do when receiving events while the command is running
+
+Default is to 'do-nothing', which ignores events while the command is running, so that changes that occur due to the command are ignored, like compilation outputs. You can also use 'queue' which will run the command once again when the current run has finished if any events occur while it's running, or 'restart', which terminates the running command and starts a new one. Finally, there's 'signal', which only sends a signal; this can be useful with programs that can reload their configuration without a full restart.
+
+The signal can be specified with the '--signal' option.
+
+**Choices:**
+
+- `queue`
+- `do-nothing`
+- `restart`
+- `signal`
+
+#### `-r --restart`
+
+Restart the process if it's still running
+
+This is a shorthand for '--on-busy-update=restart'.
+
+#### `-s --signal <SIGNAL>`
+
+Send a signal to the process when it's still running
+
+Specify a signal to send to the process when it's still running. This implies '--on-busy-update=signal'; otherwise the signal used when that mode is 'restart' is controlled by '--stop-signal'.
+
+See the long documentation for '--stop-signal' for syntax.
+
+Signals are not supported on Windows at the moment, and will always be overridden to 'kill'. See '--stop-signal' for more on Windows "signals".
+
+#### `--stop-signal <SIGNAL>`
+
+Signal to send to stop the command
+
+This is used by 'restart' and 'signal' modes of '--on-busy-update' (unless '--signal' is provided). The restart behaviour is to send the signal, wait for the command to exit, and if it hasn't exited after some time (see '--timeout-stop'), forcefully terminate it.
+
+The default on unix is "SIGTERM".
+
+Input is parsed as a full signal name (like "SIGTERM"), a short signal name (like "TERM"), or a signal number (like "15"). All input is case-insensitive.
+
+On Windows this option is technically supported but only supports the "KILL" event, as Watchexec cannot yet deliver other events. Windows doesn't have signals as such; instead it has termination (here called "KILL" or "STOP") and "CTRL+C", "CTRL+BREAK", and "CTRL+CLOSE" events. For portability the unix signals "SIGKILL", "SIGINT", "SIGTERM", and "SIGHUP" are respectively mapped to these.
+
+#### `--stop-timeout <TIMEOUT>`
+
+Time to wait for the command to exit gracefully
+
+This is used by the 'restart' mode of '--on-busy-update'. After the graceful stop signal is sent, Watchexec will wait for the command to exit. If it hasn't exited after this time, it is forcefully terminated.
+
+Takes a unit-less value in seconds, or a time span value such as "5min 20s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+The default is 10 seconds. Set to 0 to immediately force-kill the command.
+
+This has no practical effect on Windows as the command is always forcefully terminated; see '--stop-signal' for why.
+
+#### `--map-signal... <SIGNAL:SIGNAL>`
+
+Translate signals from the OS to signals to send to the command
+
+Takes a pair of signal names, separated by a colon, such as "TERM:INT" to map SIGTERM to SIGINT. The first signal is the one received by watchexec, and the second is the one sent to the command. The second can be omitted to discard the first signal, such as "TERM:" to not do anything on SIGTERM.
+
+If SIGINT or SIGTERM are mapped, then they no longer quit Watchexec. Besides making it hard to quit Watchexec itself, this is useful to send pass a Ctrl-C to the command without also terminating Watchexec and the underlying program with it, e.g. with "INT:INT".
+
+This option can be specified multiple times to map multiple signals.
+
+Signal syntax is case-insensitive for short names (like "TERM", "USR2") and long names (like "SIGKILL", "SIGHUP"). Signal numbers are also supported (like "15", "31"). On Windows, the forms "STOP", "CTRL+C", and "CTRL+BREAK" are also supported to receive, but Watchexec cannot yet deliver other "signals" than a STOP.
+
+#### `-d --debounce <TIMEOUT>`
+
+Time to wait for new events before taking action
+
+When an event is received, Watchexec will wait for up to this amount of time before handling it (such as running the command). This is essential as what you might perceive as a single change may actually emit many events, and without this behaviour, Watchexec would run much too often. Additionally, it's not infrequent that file writes are not atomic, and each write may emit an event, so this is a good way to avoid running a command while a file is partially written.
+
+An alternative use is to set a high value (like "30min" or longer), to save power or bandwidth on intensive tasks, like an ad-hoc backup script. In those use cases, note that every accumulated event will build up in memory.
+
+Takes a unit-less value in milliseconds, or a time span value such as "5sec 20ms". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+The default is 50 milliseconds. Setting to 0 is highly discouraged.
+
+#### `--stdin-quit`
+
+Exit when stdin closes
+
+This watches the stdin file descriptor for EOF, and exits Watchexec gracefully when it is closed. This is used by some process managers to avoid leaving zombie processes around.
+
+#### `--no-vcs-ignore`
+
+Don't load gitignores
+
+Among other VCS exclude files, like for Mercurial, Subversion, Bazaar, DARCS, Fossil. Note that Watchexec will detect which of these is in use, if any, and only load the relevant files. Both global (like '~/.gitignore') and local (like '.gitignore') files are considered.
+
+This option is useful if you want to watch files that are ignored by Git.
+
+#### `--no-project-ignore`
+
+Don't load project-local ignores
+
+This disables loading of project-local ignore files, like '.gitignore' or '.ignore' in the
+watched project. This is contrasted with '--no-vcs-ignore', which disables loading of Git
+and other VCS ignore files, and with '--no-global-ignore', which disables loading of global
+or user ignore files, like '~/.gitignore' or '~/.config/watchexec/ignore'.
+
+Supported project ignore files:
+
+  - Git: .gitignore at project root and child directories, .git/info/exclude, and the file pointed to by `core.excludesFile` in .git/config.
+  - Mercurial: .hgignore at project root and child directories.
+  - Bazaar: .bzrignore at project root.
+  - Darcs: _darcs/prefs/boring
+  - Fossil: .fossil-settings/ignore-glob
+  - Ripgrep/Watchexec/generic: .ignore at project root and child directories.
+
+VCS ignore files (Git, Mercurial, Bazaar, Darcs, Fossil) are only used if the corresponding
+VCS is discovered to be in use for the project/origin. For example, a .bzrignore in a Git
+repository will be discarded.
+
+#### `--no-global-ignore`
 
-#### `-g --glob... <GLOB>`
+Don't load global ignores
 
-Files to watch
-Defaults to sources from the tasks(s)
+This disables loading of global or user ignore files, like '~/.gitignore',
+'~/.config/watchexec/ignore', or '%APPDATA%\Bazzar\2.0\ignore'. Contrast with
+'--no-vcs-ignore' and '--no-project-ignore'.
+
+Supported global ignore files
+
+  - Git (if core.excludesFile is set): the file at that path
+  - Git (otherwise): the first found of $XDG_CONFIG_HOME/git/ignore, %APPDATA%/.gitignore, %USERPROFILE%/.gitignore, $HOME/.config/git/ignore, $HOME/.gitignore.
+  - Bazaar: the first found of %APPDATA%/Bazzar/2.0/ignore, $HOME/.bazaar/ignore.
+  - Watchexec: the first found of $XDG_CONFIG_HOME/watchexec/ignore, %APPDATA%/watchexec/ignore, %USERPROFILE%/.watchexec/ignore, $HOME/.watchexec/ignore.
+
+Like for project files, Git and Bazaar global files will only be used for the corresponding
+VCS as used in the project.
+
+#### `--no-default-ignore`
+
+Don't use internal default ignores
+
+Watchexec has a set of default ignore patterns, such as editor swap files, `*.pyc`, `*.pyo`, `.DS_Store`, `.bzr`, `_darcs`, `.fossil-settings`, `.git`, `.hg`, `.pijul`, `.svn`, and Watchexec log files.
+
+#### `--no-discover-ignore`
+
+Don't discover ignore files at all
+
+This is a shorthand for '--no-global-ignore', '--no-vcs-ignore', '--no-project-ignore', but even more efficient as it will skip all the ignore discovery mechanisms from the get go.
+
+Note that default ignores are still loaded, see '--no-default-ignore'.
+
+#### `--ignore-nothing`
+
+Don't ignore anything at all
+
+This is a shorthand for '--no-discover-ignore', '--no-default-ignore'.
+
+Note that ignores explicitly loaded via other command line options, such as '--ignore' or '--ignore-file', will still be used.
+
+#### `-p --postpone`
+
+Wait until first change before running command
+
+By default, Watchexec will run the command once immediately. With this option, it will instead wait until an event is detected before running the command as normal.
+
+#### `--delay-run <DURATION>`
+
+Sleep before running the command
+
+This option will cause Watchexec to sleep for the specified amount of time before running the command, after an event is detected. This is like using "sleep 5 && command" in a shell, but portable and slightly more efficient.
+
+Takes a unit-less value in seconds, or a time span value such as "2min 5s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+#### `--poll <INTERVAL>`
+
+Poll for filesystem changes
+
+By default, and where available, Watchexec uses the operating system's native file system watching capabilities. This option disables that and instead uses a polling mechanism, which is less efficient but can work around issues with some file systems (like network shares) or edge cases.
+
+Optionally takes a unit-less value in milliseconds, or a time span value such as "2s 500ms", to use as the polling interval. If not specified, the default is 30 seconds. Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+Aliased as '--force-poll'.
+
+#### `--shell <SHELL>`
+
+Use a different shell
+
+By default, Watchexec will use '$SHELL' if it's defined or a default of 'sh' on Unix-likes, and either 'pwsh', 'powershell', or 'cmd' (CMD.EXE) on Windows, depending on what Watchexec detects is the running shell.
+
+With this option, you can override that and use a different shell, for example one with more features or one which has your custom aliases and functions.
+
+If the value has spaces, it is parsed as a command line, and the first word used as the shell program, with the rest as arguments to the shell.
+
+The command is run with the '-c' flag (except for 'cmd' on Windows, where it's '/C').
+
+The special value 'none' can be used to disable shell use entirely. In that case, the command provided to Watchexec will be parsed, with the first word being the executable and the rest being the arguments, and executed directly. Note that this parsing is rudimentary, and may not work as expected in all cases.
+
+Using 'none' is a little more efficient and can enable a stricter interpretation of the input, but it also means that you can't use shell features like globbing, redirection, control flow, logic, or pipes.
 
 Examples:
-    
-    $ mise watch -t build
+
+Use without shell:
+
+$ watchexec -n -- zsh -x -o shwordsplit scr
+
+Use with powershell core:
+
+$ watchexec --shell=pwsh -- Test-Connection localhost
+
+Use with CMD.exe:
+
+$ watchexec --shell=cmd -- dir
+
+Use with a different unix shell:
+
+$ watchexec --shell=bash -- 'echo $BASH_VERSION'
+
+Use with a unix shell and options:
+
+$ watchexec --shell='zsh -x -o shwordsplit' -- scr
+
+#### `-n`
+
+Shorthand for '--shell=none'
+
+#### `--emit-events-to <MODE>`
+
+Configure event emission
+
+Watchexec can emit event information when running a command, which can be used by the child
+process to target specific changed files.
+
+One thing to take care with is assuming inherent behaviour where there is only chance.
+Notably, it could appear as if the `RENAMED` variable contains both the original and the new
+path being renamed. In previous versions, it would even appear on some platforms as if the
+original always came before the new. However, none of this was true. It's impossible to
+reliably and portably know which changed path is the old or new, "half" renames may appear
+(only the original, only the new), "unknown" renames may appear (change was a rename, but
+whether it was the old or new isn't known), rename events might split across two debouncing
+boundaries, and so on.
+
+This option controls where that information is emitted. It defaults to 'none', which doesn't
+emit event information at all. The other options are 'environment' (deprecated), 'stdio',
+'file', 'json-stdio', and 'json-file'.
+
+The 'stdio' and 'file' modes are text-based: 'stdio' writes absolute paths to the stdin of
+the command, one per line, each prefixed with `create:`, `remove:`, `rename:`, `modify:`,
+or `other:`, then closes the handle; 'file' writes the same thing to a temporary file, and
+its path is given with the $WATCHEXEC_EVENTS_FILE environment variable.
+
+There are also two JSON modes, which are based on JSON objects and can represent the full
+set of events Watchexec handles. Here's an example of a folder being created on Linux:
+
+```json
+  {
+    "tags": [
+      {
+        "kind": "path",
+        "absolute": "/home/user/your/new-folder",
+        "filetype": "dir"
+      },
+      {
+        "kind": "fs",
+        "simple": "create",
+        "full": "Create(Folder)"
+      },
+      {
+        "kind": "source",
+        "source": "filesystem",
+      }
+    ],
+    "metadata": {
+      "notify-backend": "inotify"
+    }
+  }
+```
+
+The fields are as follows:
+
+  - `tags`, structured event data.
+  - `tags[].kind`, which can be:
+    * 'path', along with:
+      + `absolute`, an absolute path.
+      + `filetype`, a file type if known ('dir', 'file', 'symlink', 'other').
+    * 'fs':
+      + `simple`, the "simple" event type ('access', 'create', 'modify', 'remove', or 'other').
+      + `full`, the "full" event type, which is too complex to fully describe here, but looks like 'General(Precise(Specific))'.
+    * 'source', along with:
+      + `source`, the source of the event ('filesystem', 'keyboard', 'mouse', 'os', 'time', 'internal').
+    * 'keyboard', along with:
+      + `keycode`. Currently only the value 'eof' is supported.
+    * 'process', for events caused by processes:
+      + `pid`, the process ID.
+    * 'signal', for signals sent to Watchexec:
+      + `signal`, the normalised signal name ('hangup', 'interrupt', 'quit', 'terminate', 'user1', 'user2').
+    * 'completion', for when a command ends:
+      + `disposition`, the exit disposition ('success', 'error', 'signal', 'stop', 'exception', 'continued').
+      + `code`, the exit, signal, stop, or exception code.
+  - `metadata`, additional information about the event.
+
+The 'json-stdio' mode will emit JSON events to the standard input of the command, one per
+line, then close stdin. The 'json-file' mode will create a temporary file, write the
+events to it, and provide the path to the file with the $WATCHEXEC_EVENTS_FILE
+environment variable.
+
+Finally, the 'environment' mode was the default until 2.0. It sets environment variables
+with the paths of the affected files, for filesystem events:
+
+$WATCHEXEC_COMMON_PATH is set to the longest common path of all of the below variables,
+and so should be prepended to each path to obtain the full/real path. Then:
+
+  - $WATCHEXEC_CREATED_PATH is set when files/folders were created
+  - $WATCHEXEC_REMOVED_PATH is set when files/folders were removed
+  - $WATCHEXEC_RENAMED_PATH is set when files/folders were renamed
+  - $WATCHEXEC_WRITTEN_PATH is set when files/folders were modified
+  - $WATCHEXEC_META_CHANGED_PATH is set when files/folders' metadata were modified
+  - $WATCHEXEC_OTHERWISE_CHANGED_PATH is set for every other kind of pathed event
+
+Multiple paths are separated by the system path separator, ';' on Windows and ':' on unix.
+Within each variable, paths are deduplicated and sorted in binary order (i.e. neither
+Unicode nor locale aware).
+
+This is the legacy mode, is deprecated, and will be removed in the future. The environment
+is a very restricted space, while also limited in what it can usefully represent. Large
+numbers of files will either cause the environment to be truncated, or may error or crash
+the process entirely. The $WATCHEXEC_COMMON_PATH is also unintuitive, as demonstrated by the
+multiple confused queries that have landed in my inbox over the years.
+
+**Choices:**
+
+- `environment`
+- `stdio`
+- `file`
+- `json-stdio`
+- `json-file`
+- `none`
+
+#### `--only-emit-events`
+
+Only emit events to stdout, run no commands.
+
+This is a convenience option for using Watchexec as a file watcher, without running any commands. It is almost equivalent to using `cat` as the command, except that it will not spawn a new process for each event.
+
+This option requires `--emit-events-to` to be set, and restricts the available modes to `stdio` and `json-stdio`, modifying their behaviour to write to stdout instead of the stdin of the command.
+
+#### `-E --env... <KEY=VALUE>`
+
+Add env vars to the command
+
+This is a convenience option for setting environment variables for the command, without setting them for the Watchexec process itself.
+
+Use key=value syntax. Multiple variables can be set by repeating the option.
+
+#### `--wrap-process <MODE>`
+
+Configure how the process is wrapped
+
+By default, Watchexec will run the command in a process group in Unix, and in a Job Object in Windows.
+
+Some Unix programs prefer running in a session, while others do not work in a process group.
+
+Use 'group' to use a process group, 'session' to use a process session, and 'none' to run the command directly. On Windows, either of 'group' or 'session' will use a Job Object.
+
+**Choices:**
+
+- `group`
+- `session`
+- `none`
+
+#### `-N --notify`
+
+Alert when commands start and end
+
+With this, Watchexec will emit a desktop notification when a command starts and ends, on supported platforms. On unsupported platforms, it may silently do nothing, or log a warning.
+
+#### `--color <MODE>`
+
+When to use terminal colours
+
+Setting the environment variable `NO_COLOR` to any value is equivalent to `--color=never`.
+
+**Choices:**
+
+- `auto`
+- `always`
+- `never`
+
+#### `--timings`
+
+Print how long the command took to run
+
+This may not be exactly accurate, as it includes some overhead from Watchexec itself. Use the `time` utility, high-precision timers, or benchmarking tools for more accurate results.
+
+#### `-q --quiet`
+
+Don't print starting and stopping messages
+
+By default Watchexec will print a message when the command starts and stops. This option disables this behaviour, so only the command's output, warnings, and errors will be printed.
+
+#### `--bell`
+
+Ring the terminal bell on command completion
+
+#### `--project-origin <DIRECTORY>`
+
+Set the project origin
+
+Watchexec will attempt to discover the project's "origin" (or "root") by searching for a variety of markers, like files or directory patterns. It does its best but sometimes gets it it wrong, and you can override that with this option.
+
+The project origin is used to determine the path of certain ignore files, which VCS is being used, the meaning of a leading '/' in filtering patterns, and maybe more in the future.
+
+When set, Watchexec will also not bother searching, which can be significantly faster.
+
+#### `--workdir <DIRECTORY>`
+
+Set the working directory
+
+By default, the working directory of the command is the working directory of Watchexec. You can change that with this option. Note that paths may be less intuitive to use with this.
+
+#### `-e --exts... <EXTENSIONS>`
+
+Filename extensions to filter to
+
+This is a quick filter to only emit events for files with the given extensions. Extensions can be given with or without the leading dot (e.g. 'js' or '.js'). Multiple extensions can be given by repeating the option or by separating them with commas.
+
+#### `-f --filter... <PATTERN>`
+
+Filename patterns to filter to
+
+Provide a glob-like filter pattern, and only events for files matching the pattern will be emitted. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.
+
+#### `--filter-file... <PATH>`
+
+Files to load filters from
+
+Provide a path to a file containing filters, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--filter' option.
+
+This can also be used via the $WATCHEXEC_FILTER_FILES environment variable.
+
+#### `-J --filter-prog... <EXPRESSION>`
+
+[experimental] Filter programs.
+
+/!\ This option is EXPERIMENTAL and may change and/or vanish without notice.
+
+Provide your own custom filter programs in jaq (similar to jq) syntax. Programs are given an event in the same format as described in '--emit-events-to' and must return a boolean. Invalid programs will make watchexec fail to start; use '-v' to see program runtime errors.
+
+In addition to the jaq stdlib, watchexec adds some custom filter definitions:
+
+- 'path | file_meta' returns file metadata or null if the file does not exist.
+
+- 'path | file_size' returns the size of the file at path, or null if it does not exist.
+
+- 'path | file_read(bytes)' returns a string with the first n bytes of the file at path. If the file is smaller than n bytes, the whole file is returned. There is no filter to read the whole file at once to encourage limiting the amount of data read and processed.
+
+- 'string | hash', and 'path | file_hash' return the hash of the string or file at path. No guarantee is made about the algorithm used: treat it as an opaque value.
+
+- 'any | kv_store(key)', 'kv_fetch(key)', and 'kv_clear' provide a simple key-value store. Data is kept in memory only, there is no persistence. Consistency is not guaranteed.
+
+- 'any | printout', 'any | printerr', and 'any | log(level)' will print or log any given value to stdout, stderr, or the log (levels = error, warn, info, debug, trace), and pass the value through (so '[1] | log("debug") | .[]' will produce a '1' and log '[1]').
+
+All filtering done with such programs, and especially those using kv or filesystem access, is much slower than the other filtering methods. If filtering is too slow, events will back up and stall watchexec. Take care when designing your filters.
+
+If the argument to this option starts with an '@', the rest of the argument is taken to be the path to a file containing a jaq program.
+
+Jaq programs are run in order, after all other filters, and short-circuit: if a filter (jaq or not) rejects an event, execution stops there, and no other filters are run. Additionally, they stop after outputting the first value, so you'll want to use 'any' or 'all' when iterating, otherwise only the first item will be processed, which can be quite confusing!
+
+Find user-contributed programs or submit your own useful ones at <https://github.com/watchexec/watchexec/discussions/592>.
+
+## Examples:
+
+Regexp ignore filter on paths:
+
+'all(.tags[] | select(.kind == "path"); .absolute | test("[.]test[.]js$")) | not'
+
+Pass any event that creates a file:
+
+'any(.tags[] | select(.kind == "fs"); .simple == "create")'
+
+Pass events that touch executable files:
+
+'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | metadata | .executable)'
+
+Ignore files that start with shebangs:
+
+'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | read(2) == "#!") | not'
+
+#### `-i --ignore... <PATTERN>`
+
+Filename patterns to filter out
+
+Provide a glob-like filter pattern, and events for files matching the pattern will be excluded. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.
+
+#### `--ignore-file... <PATH>`
+
+Files to load ignores from
+
+Provide a path to a file containing ignores, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--ignore' option.
+
+This can also be used via the $WATCHEXEC_IGNORE_FILES environment variable.
+
+#### `--fs-events... <EVENTS>`
+
+Filesystem events to filter to
+
+This is a quick filter to only emit events for the given types of filesystem changes. Choose from 'access', 'create', 'remove', 'rename', 'modify', 'metadata'. Multiple types can be given by repeating the option or by separating them with commas. By default, this is all types except for 'access'.
+
+This may apply filtering at the kernel level when possible, which can be more efficient, but may be more confusing when reading the logs.
+
+**Choices:**
+
+- `access`
+- `create`
+- `remove`
+- `rename`
+- `modify`
+- `metadata`
+
+#### `--no-meta`
+
+Don't emit fs events for metadata changes
+
+This is a shorthand for '--fs-events create,remove,rename,modify'. Using it alongside the '--fs-events' option is non-sensical and not allowed.
+
+#### `--print-events`
+
+Print events that trigger actions
+
+This prints the events that triggered the action when handling it (after debouncing), in a human readable form. This is useful for debugging filters.
+
+Use '-vvv' instead when you need more diagnostic information.
+
+#### `--manual`
+
+Show the manual page
+
+This shows the manual page for Watchexec, if the output is a terminal and the 'man' program is available. If not, the manual page is printed to stdout in ROFF format (suitable for writing to a watchexec.1 file).
+
+Examples:
+
+    $ mise watch build
     Runs the "build" tasks. Will re-run the tasks when any of its sources change.
     Uses "sources" from the tasks definition to determine which files to watch.
 
-    $ mise watch -t build --glob src/**/*.rs
+    $ mise watch build --glob src/**/*.rs
     Runs the "build" tasks but specify the files to watch with a glob pattern.
     This overrides the "sources" from the tasks definition.
 
-    $ mise run -t build --clear
+    $ mise watch build --clear
     Extra arguments are passed to watchexec. See `watchexec --help` for details.
 
+    $ mise watch serve --watch src --exts rs --restart
+    Starts an api server, watching for changes to "*.rs" files in "./src" and kills/restarts the server when they change.
+
 ## `mise where`
 
 - **Usage**: `mise where <TOOL@VERSION>`
+- **Source code**: [`src/cli/where.rs`](https://github.com/jdx/mise/blob/main/src/cli/where.rs)
 
 Display the installation path for a tool
 
@@ -2595,7 +3959,8 @@ Examples:
 
 ## `mise which`
 
-- **Usage**: `mise which [FLAGS] <BIN_NAME>`
+- **Usage**: `mise which [FLAGS] [BIN_NAME]`
+- **Source code**: [`src/cli/which.rs`](https://github.com/jdx/mise/blob/main/src/cli/which.rs)
 
 Shows the path that a tool's bin points to.
 
@@ -2603,7 +3968,7 @@ Use this to figure out what version of a tool is currently active.
 
 ### Arguments
 
-#### `<BIN_NAME>`
+#### `[BIN_NAME]`
 
 The bin to look up
 
@@ -2636,11 +4001,13 @@ Examples:
 ## `mise render-help`
 
 - **Usage**: `mise render-help`
+- **Source code**: [`src/cli/render_help.rs`](https://github.com/jdx/mise/blob/main/src/cli/render_help.rs)
 
 internal command to generate markdown from help
 
 ## `mise render-mangen`
 
 - **Usage**: `mise render-mangen`
+- **Source code**: [`src/cli/render_mangen.rs`](https://github.com/jdx/mise/blob/main/src/cli/render_mangen.rs)
 
 internal command to generate markdown from help
diff --git a/examples/docs/MISE_MULTI.md b/examples/docs/MISE_MULTI.md
index 28b679fa..c63a3aee 100644
--- a/examples/docs/MISE_MULTI.md
+++ b/examples/docs/MISE_MULTI.md
@@ -1,5 +1,6 @@
 # `mise`
 
+
 mise is a tool for managing runtime versions. https://github.com/jdx/mise
 
 It's a replacement for tools like nvm, nodenv, rbenv, rvm, chruby, pyenv, etc.
@@ -10,7 +11,15 @@ It is inspired by asdf and uses asdf's plugin ecosystem under the hood:
 https://asdf-vm.com/
 
 
-- **Usage**: `mise [FLAGS] <SUBCOMMAND>`
+- **Usage**: `mise [FLAGS] [TASK] <SUBCOMMAND>`
+
+## Arguments
+
+### `[TASK]`
+
+Task to run.
+
+Shorthand for `mise task run <TASK>`.
 
 ## Global Flags
 
@@ -18,44 +27,63 @@ https://asdf-vm.com/
 
 Change directory before running command
 
-### `-P --profile <PROFILE>`
+### `-E --env... <ENV>`
+
+Set the environment for loading `mise.<ENV>.toml`
+
+### `-j --jobs <JOBS>`
+
+How many jobs to run in parallel [default: 8]
 
-Set the profile (environment)
+### `--raw`
+
+Read/write directly to stdin/stdout/stderr instead of by line
+
+### `-y --yes`
+
+Answer yes to all confirmation prompts
 
 ### `-q --quiet`
 
 Suppress non-error messages
 
+### `--silent`
+
+Suppress all task output and mise non-error messages
+
 ### `-v --verbose...`
 
 Show extra output (use -vv for even more)
 
-### `-y --yes`
+## Flags
 
-Answer yes to all confirmation prompts
+### `--output <OUTPUT>`
+
+### `--no-config`
+
+Do not load any config files
+
+Can also use `MISE_NO_CONFIG=1`
 
 ## `mise activate`
 
-- **Usage**: `mise activate [--shims] [-q --quiet] [SHELL_TYPE]`
+- **Usage**: `mise activate [FLAGS] [SHELL_TYPE]`
+- **Source code**: [`src/cli/activate.rs`](https://github.com/jdx/mise/blob/main/src/cli/activate.rs)
 
 Initializes mise in the current shell session
 
-This should go into your shell's rc file.
+This should go into your shell's rc file or login shell.
 Otherwise, it will only take effect in the current session.
-(e.g. ~/.zshrc, ~/.bashrc)
-
-This is only intended to be used in interactive sessions, not scripts.
-mise is only capable of updating PATH when the prompt is displayed to the user.
-For non-interactive use-cases, use shims instead.
+(e.g. ~/.zshrc, ~/.zprofile, ~/.zshenv, ~/.bashrc, ~/.bash_profile, ~/.profile, ~/.config/fish/config.fish)
 
-Typically this can be added with something like the following:
+Typically, this can be added with something like the following:
 
-    echo 'eval "$(mise activate)"' >> ~/.zshrc
+    echo 'eval "$(mise activate zsh)"' >> ~/.zshrc
 
 However, this requires that "mise" is in your PATH. If it is not, you need to
 specify the full path like this:
 
-    echo 'eval "$(/path/to/mise activate)"' >> ~/.zshrc
+    echo 'eval "$(/path/to/mise activate zsh)"' >> ~/.zshrc
 
 Customize status output with `status` settings.
 
@@ -68,10 +96,12 @@ Shell type to generate the script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 ### Flags
 
@@ -82,10 +112,19 @@ Effectively the same as:
 
     PATH="$HOME/.local/share/mise/shims:$PATH"
 
+`mise activate --shims` does not support all the features of `mise activate`.
+See https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path for more information
+
 #### `-q --quiet`
 
 Suppress non-error messages
 
+#### `--no-hook-env`
+
+Do not automatically call hook-env
+
+This can be helpful for debugging mise. If you run `eval "$(mise activate --no-hook-env)"`, then you can call `mise hook-env` manually which will output the env vars to stdout without actually modifying the environment. That way you can do things like `mise hook-env --trace` to get more information or just see the values that hook-env is outputting.
+
 Examples:
 
     $ eval "$(mise activate bash)"
@@ -97,6 +136,7 @@ Examples:
 
 - **Usage**: `mise alias [-p --plugin <PLUGIN>] [--no-header] <SUBCOMMAND>`
 - **Aliases**: `a`
+- **Source code**: [`src/cli/alias/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/mod.rs)
 
 Manage aliases
 
@@ -113,6 +153,7 @@ Don't show table header
 ## `mise alias get`
 
 - **Usage**: `mise alias get <PLUGIN> <ALIAS>`
+- **Source code**: [`src/cli/alias/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/get.rs)
 
 Show an alias for a plugin
 
@@ -130,13 +171,14 @@ The alias to show
 
 Examples:
 
-   $ mise alias get node lts-hydrogen
-   20.0.0
+    $ mise alias get node lts-hydrogen
+    20.0.0
 
 ## `mise alias ls`
 
-- **Usage**: `mise alias ls [--no-header] [PLUGIN]`
+- **Usage**: `mise alias ls [--no-header] [TOOL]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/alias/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/ls.rs)
 
 List aliases
 Shows the aliases that can be specified.
@@ -144,14 +186,14 @@ These can come from user config or from plugins in `bin/list-aliases`.
 
 For user config, aliases are defined like the following in `~/.config/mise/config.toml`:
 
-    [alias.node]
-    lts = "20.0.0"
+    [alias.node.versions]
+    lts = "22.0.0"
 
 ### Arguments
 
-#### `[PLUGIN]`
+#### `[TOOL]`
 
-Show aliases for <PLUGIN>
+Show aliases for <TOOL>
 
 ### Flags
 
@@ -162,12 +204,13 @@ Don't show table header
 Examples:
 
     $ mise aliases
-    node    lts-hydrogen   20.0.0
+    node  lts-jod      22
 
 ## `mise alias set`
 
 - **Usage**: `mise alias set <ARGS>…`
 - **Aliases**: `add`, `create`
+- **Source code**: [`src/cli/alias/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/set.rs)
 
 Add/update an alias for a plugin
 
@@ -189,12 +232,13 @@ The value to set the alias to
 
 Examples:
 
-    $ mise alias set node lts-hydrogen 18.0.0
+    $ mise alias set node lts-jod 22.0.0
 
 ## `mise alias unset`
 
 - **Usage**: `mise alias unset <PLUGIN> <ALIAS>`
 - **Aliases**: `rm`, `remove`, `delete`, `del`
+- **Source code**: [`src/cli/alias/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/alias/unset.rs)
 
 Clears an alias for a plugin
 
@@ -212,11 +256,12 @@ The alias to remove
 
 Examples:
 
-    $ mise alias unset node lts-hydrogen
+    $ mise alias unset node lts-jod
 
 ## `mise asdf`
 
 - **Usage**: `mise asdf [ARGS]...`
+- **Source code**: [`src/cli/asdf.rs`](https://github.com/jdx/mise/blob/main/src/cli/asdf.rs)
 
 [internal] simulates asdf for plugins that call "asdf" internally
 
@@ -230,6 +275,7 @@ all arguments
 
 - **Usage**: `mise backends <SUBCOMMAND>`
 - **Aliases**: `b`
+- **Source code**: [`src/cli/backends/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/backends/mod.rs)
 
 Manage backends
 
@@ -237,28 +283,44 @@ Manage backends
 
 - **Usage**: `mise backends ls`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/backends/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/backends/ls.rs)
 
 List built-in backends
 
 Examples:
 
     $ mise backends ls
+    aqua
+    asdf
     cargo
+    core
+    dotnet
+    gem
     go
     npm
     pipx
     spm
     ubi
+    vfox
 
 ## `mise bin-paths`
 
-- **Usage**: `mise bin-paths`
+- **Usage**: `mise bin-paths [TOOL@VERSION]...`
+- **Source code**: [`src/cli/bin_paths.rs`](https://github.com/jdx/mise/blob/main/src/cli/bin_paths.rs)
 
 List all the active runtime bin paths
 
+### Arguments
+
+#### `[TOOL@VERSION]...`
+
+Tool(s) to look up
+e.g.: ruby@3
+
 ## `mise cache`
 
 - **Usage**: `mise cache <SUBCOMMAND>`
+- **Source code**: [`src/cli/cache/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/mod.rs)
 
 Manage the mise cache
 
@@ -268,6 +330,7 @@ Run `mise cache` with no args to view the current cache directory.
 
 - **Usage**: `mise cache clear [PLUGIN]...`
 - **Aliases**: `c`
+- **Source code**: [`src/cli/cache/clear.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/clear.rs)
 
 Deletes all cache files in mise
 
@@ -281,6 +344,7 @@ Plugin(s) to clear cache for e.g.: node, python
 
 - **Usage**: `mise cache prune [--dry-run] [-v --verbose...] [PLUGIN]...`
 - **Aliases**: `p`
+- **Source code**: [`src/cli/cache/prune.rs`](https://github.com/jdx/mise/blob/main/src/cli/cache/prune.rs)
 
 Removes stale mise cache files
 
@@ -305,7 +369,8 @@ Show pruned files
 
 ## `mise completion`
 
-- **Usage**: `mise completion [SHELL]`
+- **Usage**: `mise completion [--include-bash-completion-lib] [SHELL]`
+- **Source code**: [`src/cli/completion.rs`](https://github.com/jdx/mise/blob/main/src/cli/completion.rs)
 
 Generate shell completions
 
@@ -321,6 +386,15 @@ Shell type to generate completions for
 - `fish`
 - `zsh`
 
+### Flags
+
+#### `--include-bash-completion-lib`
+
+Include the bash completion library in the bash completion script
+
+This is required for completions to work in bash, but it is not included by default
+you may source it separately or enable this flag to include it in the script.
+
 Examples:
 
     $ mise completion bash > /etc/bash_completion.d/mise
@@ -331,6 +405,7 @@ Examples:
 
 - **Usage**: `mise config [--no-header] [-J --json] <SUBCOMMAND>`
 - **Aliases**: `cfg`
+- **Source code**: [`src/cli/config/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/mod.rs)
 
 Manage config files
 
@@ -346,13 +421,18 @@ Output in JSON format
 
 ## `mise config generate`
 
-- **Usage**: `mise config generate [-o --output <OUTPUT>]`
+- **Usage**: `mise config generate [-t --tool-versions <TOOL_VERSIONS>] [-o --output <OUTPUT>]`
 - **Aliases**: `g`
+- **Source code**: [`src/cli/config/generate.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/generate.rs)
 
 [experimental] Generate a mise.toml file
 
 ### Flags
 
+#### `-t --tool-versions <TOOL_VERSIONS>`
+
+Path to a .tool-versions file to import tools from
+
 #### `-o --output <OUTPUT>`
 
 Output to file instead of stdout
@@ -365,6 +445,7 @@ Examples:
 ## `mise config get`
 
 - **Usage**: `mise config get [-f --file <FILE>] [KEY]`
+- **Source code**: [`src/cli/config/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/get.rs)
 
 Display the value of a setting in a mise.toml file
 
@@ -390,6 +471,8 @@ Examples:
 ## `mise config ls`
 
 - **Usage**: `mise config ls [--no-header] [-J --json]`
+- **Aliases**: `list`
+- **Source code**: [`src/cli/config/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/ls.rs)
 
 List config files currently in use
 
@@ -406,12 +489,16 @@ Output in JSON format
 Examples:
 
     $ mise config ls
+    Path                        Tools
+    ~/.config/mise/config.toml  pitchfork
+    ~/src/mise/mise.toml        actionlint, bun, cargo-binstall, cargo:cargo-edit, cargo:cargo-insta
 
 ## `mise config set`
 
 - **Usage**: `mise config set [-f --file <FILE>] [-t --type <TYPE>] <KEY> <VALUE>`
+- **Source code**: [`src/cli/config/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/config/set.rs)
 
-Display the value of a setting in a mise.toml file
+Set the value of a setting in a mise.toml file
 
 ### Arguments
 
@@ -435,20 +522,27 @@ If not provided, the nearest mise.toml file will be used
 
 **Choices:**
 
+- `infer`
 - `string`
 - `integer`
 - `float`
 - `bool`
+- `list`
 
 Examples:
 
     $ mise config set tools.python 3.12
     $ mise config set settings.always_keep_download true
     $ mise config set env.TEST_ENV_VAR ABC
+    $ mise config set settings.disable_tools --type list node,rust
+
+    # Type for `settings` is inferred
+    $ mise config set settings.jobs 4
 
 ## `mise current`
 
 - **Usage**: `mise current [PLUGIN]`
+- **Source code**: [`src/cli/current.rs`](https://github.com/jdx/mise/blob/main/src/cli/current.rs)
 
 Shows current active and installed runtime versions
 
@@ -462,7 +556,7 @@ and/or version. It's designed to fit into scripts more easily.
 Plugin to show versions of e.g.: ruby, node, cargo:eza, npm:prettier, etc
 
 Examples:
-    
+
     # outputs `.tool-versions` compatible format
     $ mise current
     python 3.11.0 3.10.0
@@ -480,6 +574,7 @@ Examples:
 ## `mise deactivate`
 
 - **Usage**: `mise deactivate`
+- **Source code**: [`src/cli/deactivate.rs`](https://github.com/jdx/mise/blob/main/src/cli/deactivate.rs)
 
 Disable mise for current shell session
 
@@ -492,18 +587,20 @@ Examples:
 ## `mise direnv`
 
 - **Usage**: `mise direnv <SUBCOMMAND>`
+- **Source code**: [`src/cli/direnv/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/mod.rs)
 
 Output direnv function to use mise inside direnv
 
 See https://mise.jdx.dev/direnv.html for more information
 
-Because this generates the legacy files based on currently installed plugins,
+Because this generates the idiomatic files based on currently installed plugins,
 you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change.
+direnv may not know to update environment variables when idiomatic file versions change.
 
 ## `mise direnv envrc`
 
 - **Usage**: `mise direnv envrc`
+- **Source code**: [`src/cli/direnv/envrc.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/envrc.rs)
 
 [internal] This is an internal command that writes an envrc file
 for direnv to consume.
@@ -511,6 +608,7 @@ for direnv to consume.
 ## `mise direnv exec`
 
 - **Usage**: `mise direnv exec`
+- **Source code**: [`src/cli/direnv/exec.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/exec.rs)
 
 [internal] This is an internal command that writes an envrc file
 for direnv to consume.
@@ -518,14 +616,15 @@ for direnv to consume.
 ## `mise direnv activate`
 
 - **Usage**: `mise direnv activate`
+- **Source code**: [`src/cli/direnv/activate.rs`](https://github.com/jdx/mise/blob/main/src/cli/direnv/activate.rs)
 
 Output direnv function to use mise inside direnv
 
 See https://mise.jdx.dev/direnv.html for more information
 
-Because this generates the legacy files based on currently installed plugins,
+Because this generates the idiomatic files based on currently installed plugins,
 you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change.
+direnv may not know to update environment variables when idiomatic file versions change.
 
 Examples:
 
@@ -535,20 +634,86 @@ Examples:
 
 ## `mise doctor`
 
-- **Usage**: `mise doctor`
+- **Usage**: `mise doctor [-J --json] <SUBCOMMAND>`
 - **Aliases**: `dr`
+- **Source code**: [`src/cli/doctor/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/doctor/mod.rs)
 
 Check mise installation for possible problems
 
+### Flags
+
+#### `-J --json`
+
 Examples:
 
     $ mise doctor
     [WARN] plugin node is not installed
 
+## `mise doctor path`
+
+- **Usage**: `mise doctor path [-f --full]`
+- **Source code**: [`src/cli/doctor/path.rs`](https://github.com/jdx/mise/blob/main/src/cli/doctor/path.rs)
+
+Print the current PATH entries mise is providing
+
+### Flags
+
+#### `-f --full`
+
+Print all entries including those not provided by mise
+
+Examples:
+
+    Get the current PATH entries mise is providing
+    $ mise path
+    /home/user/.local/share/mise/installs/node/24.0.0/bin
+    /home/user/.local/share/mise/installs/rust/1.90.0/bin
+    /home/user/.local/share/mise/installs/python/3.10.0/bin
+
+## `mise en`
+
+- **Usage**: `mise en [-s --shell <SHELL>] [DIR]`
+- **Source code**: [`src/cli/en.rs`](https://github.com/jdx/mise/blob/main/src/cli/en.rs)
+
+[experimental] starts a new shell with the mise environment built from the current configuration
+
+This is an alternative to `mise activate` that allows you to explicitly start a mise session.
+It will have the tools and environment variables in the configs loaded.
+Note that changing directories will not update the mise environment.
+
+### Arguments
+
+#### `[DIR]`
+
+Directory to start the shell in
+
+**Default:** `.`
+
+### Flags
+
+#### `-s --shell <SHELL>`
+
+Shell to start
+
+Defaults to $SHELL
+
+Examples:
+
+    $ mise en .
+    $ node -v
+    v20.0.0
+
+    Skip loading bashrc:
+    $ mise en -s "bash --norc"
+
+    Skip loading zshrc:
+    $ mise en -s "zsh -f"
+
 ## `mise env`
 
-- **Usage**: `mise env [-J --json] [-s --shell <SHELL>] [TOOL@VERSION]...`
+- **Usage**: `mise env [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `e`
+- **Source code**: [`src/cli/env.rs`](https://github.com/jdx/mise/blob/main/src/cli/env.rs)
 
 Exports env vars to activate mise a single time
 
@@ -567,6 +732,14 @@ Tool(s) to use
 
 Output in JSON format
 
+#### `--json-extended`
+
+Output in JSON format with additional information (source, tool)
+
+#### `-D --dotenv`
+
+Output in dotenv format
+
 #### `-s --shell <SHELL>`
 
 Shell type to generate environment variables for
@@ -574,10 +747,12 @@ Shell type to generate environment variables for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 Examples:
 
@@ -588,8 +763,9 @@ Examples:
 
 ## `mise exec`
 
-- **Usage**: `mise exec [FLAGS] [TOOL@VERSION]... [COMMAND]...`
+- **Usage**: `mise exec [FLAGS] [TOOL@VERSION]... [-- COMMAND]...`
 - **Aliases**: `x`
+- **Source code**: [`src/cli/exec.rs`](https://github.com/jdx/mise/blob/main/src/cli/exec.rs)
 
 Execute a command with tool(s) set
 
@@ -607,7 +783,7 @@ The "--" separates runtimes from the commands to pass along to the subprocess.
 
 Tool(s) to start e.g.: node@20 python@3.10
 
-#### `[COMMAND]...`
+#### `[-- COMMAND]...`
 
 Command string to execute (same as --command)
 
@@ -637,23 +813,104 @@ Examples:
     # Run a command in a different directory:
     $ mise x -C /path/to/project node@20 -- node ./app.js
 
+## `mise fmt`
+
+- **Usage**: `mise fmt [-a --all]`
+- **Source code**: [`src/cli/fmt.rs`](https://github.com/jdx/mise/blob/main/src/cli/fmt.rs)
+
+Formats mise.toml
+
+Sorts keys and cleans up whitespace in mise.toml
+
+### Flags
+
+#### `-a --all`
+
+Format all files from the current directory
+
+Examples:
+
+    $ mise fmt
+
 ## `mise generate`
 
 - **Usage**: `mise generate <SUBCOMMAND>`
-- **Aliases**: `g`
+- **Aliases**: `gen`
+- **Source code**: [`src/cli/generate/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/mod.rs)
 
 [experimental] Generate files for various tools/services
 
+## `mise generate bootstrap`
+
+- **Usage**: `mise generate bootstrap [FLAGS]`
+- **Source code**: [`src/cli/generate/bootstrap.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/bootstrap.rs)
+
+[experimental] Generate a script to download+execute mise
+
+This is designed to be used in a project where contributors may not have mise installed.
+
+### Flags
+
+#### `-l --localize`
+
+Sandboxes mise internal directories like MISE_DATA_DIR and MISE_CACHE_DIR into a `.mise` directory in the project
+
+This is necessary if users may use a different version of mise outside the project.
+
+#### `--localized-dir <LOCALIZED_DIR>`
+
+Directory to put localized data into
+
+#### `-V --version <VERSION>`
+
+Specify mise version to fetch
+
+#### `-w --write <WRITE>`
+
+instead of outputting the script to stdout, write to a file and make it executable
+
+Examples:
+
+    $ mise generate bootstrap >./bin/mise
+    $ chmod +x ./bin/mise
+    $ ./bin/mise install – automatically downloads mise to .mise if not already installed
+
+## `mise generate config`
+
+- **Usage**: `mise generate config [-t --tool-versions <TOOL_VERSIONS>] [-o --output <OUTPUT>]`
+- **Aliases**: `g`
+- **Source code**: [`src/cli/generate/config.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/config.rs)
+
+[experimental] Generate a mise.toml file
+
+### Flags
+
+#### `-t --tool-versions <TOOL_VERSIONS>`
+
+Path to a .tool-versions file to import tools from
+
+#### `-o --output <OUTPUT>`
+
+Output to file instead of stdout
+
+Examples:
+
+    $ mise cf generate > mise.toml
+    $ mise cf generate --output=mise.toml
+
 ## `mise generate git-pre-commit`
 
 - **Usage**: `mise generate git-pre-commit [FLAGS]`
 - **Aliases**: `pre-commit`
+- **Source code**: [`src/cli/generate/git_pre_commit.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/git_pre_commit.rs)
 
 [experimental] Generate a git pre-commit hook
 
 This command generates a git pre-commit hook that runs a mise task like `mise run pre-commit`
 when you commit changes to your repository.
 
+Staged files are passed to the task as `STAGED`.
+
 ### Flags
 
 #### `--hook <HOOK>`
@@ -676,6 +933,7 @@ Examples:
 ## `mise generate github-action`
 
 - **Usage**: `mise generate github-action [FLAGS]`
+- **Source code**: [`src/cli/generate/github_action.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/github_action.rs)
 
 [experimental] Generate a GitHub Action workflow file
 
@@ -684,7 +942,7 @@ when you push changes to your repository.
 
 ### Flags
 
-#### `-n --name <NAME>`
+#### `--name <NAME>`
 
 the name of the workflow to generate
 
@@ -705,8 +963,9 @@ Examples:
 ## `mise generate task-docs`
 
 - **Usage**: `mise generate task-docs [FLAGS]`
+- **Source code**: [`src/cli/generate/task_docs.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/task_docs.rs)
 
-[experimental] Generate documentation for tasks in a project
+Generate documentation for tasks in a project
 
 ### Flags
 
@@ -745,9 +1004,39 @@ Examples:
 
     $ mise generate task-docs
 
+## `mise generate task-stubs`
+
+- **Usage**: `mise generate task-stubs [-m --mise-bin <MISE_BIN>] [-d --dir <DIR>]`
+- **Source code**: [`src/cli/generate/task_stubs.rs`](https://github.com/jdx/mise/blob/main/src/cli/generate/task_stubs.rs)
+
+[experimental] Generates shims to run mise tasks
+
+By default, this will build shims like ./bin/<task>. These can be paired with `mise generate bootstrap`
+so contributors to a project can execute mise tasks without installing mise into their system.
+
+### Flags
+
+#### `-m --mise-bin <MISE_BIN>`
+
+Path to a mise bin to use when running the task stub.
+
+Use `--mise-bin=./bin/mise` to use a mise bin generated from `mise generate bootstrap`
+
+#### `-d --dir <DIR>`
+
+Directory to create task stubs inside of
+
+Examples:
+
+    $ mise task add test -- echo 'running tests'
+    $ mise generate task-stubs
+    $ ./bin/test
+    running tests
+
 ## `mise global`
 
 - **Usage**: `mise global [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/global.rs`](https://github.com/jdx/mise/blob/main/src/cli/global.rs)
 
 Sets/gets the global tool version(s)
 
@@ -805,7 +1094,8 @@ Examples:
 
 ## `mise hook-env`
 
-- **Usage**: `mise hook-env [-s --shell <SHELL>] [-q --quiet]`
+- **Usage**: `mise hook-env [FLAGS]`
+- **Source code**: [`src/cli/hook_env.rs`](https://github.com/jdx/mise/blob/main/src/cli/hook_env.rs)
 
 [internal] called by activate hook to update env vars directory change
 
@@ -818,10 +1108,16 @@ Shell type to generate script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
+
+#### `-f --force`
+
+Skip early exit check
 
 #### `-q --quiet`
 
@@ -830,6 +1126,7 @@ Hide warnings such as when a tool is not installed
 ## `mise hook-not-found`
 
 - **Usage**: `mise hook-not-found [-s --shell <SHELL>] <BIN>`
+- **Source code**: [`src/cli/hook_not_found.rs`](https://github.com/jdx/mise/blob/main/src/cli/hook_not_found.rs)
 
 [internal] called by shell when a command is not found
 
@@ -848,14 +1145,17 @@ Shell type to generate script for
 **Choices:**
 
 - `bash`
+- `elvish`
 - `fish`
 - `nu`
 - `xonsh`
 - `zsh`
+- `pwsh`
 
 ## `mise implode`
 
 - **Usage**: `mise implode [--config] [-n --dry-run]`
+- **Source code**: [`src/cli/implode.rs`](https://github.com/jdx/mise/blob/main/src/cli/implode.rs)
 
 Removes mise CLI and all related data
 
@@ -875,6 +1175,7 @@ List directories that would be removed without actually removing them
 
 - **Usage**: `mise install [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `i`
+- **Source code**: [`src/cli/install.rs`](https://github.com/jdx/mise/blob/main/src/cli/install.rs)
 
 Install a tool version
 
@@ -920,9 +1221,35 @@ Examples:
     $ mise install node         # install version specified in mise.toml
     $ mise install              # installs everything specified in mise.toml
 
+## `mise install-into`
+
+- **Usage**: `mise install-into <TOOL@VERSION> <PATH>`
+- **Source code**: [`src/cli/install_into.rs`](https://github.com/jdx/mise/blob/main/src/cli/install_into.rs)
+
+Install a tool version to a specific path
+
+Used for building a tool to a directory for use outside of mise
+
+### Arguments
+
+#### `<TOOL@VERSION>`
+
+Tool to install e.g.: node@20
+
+#### `<PATH>`
+
+Path to install the tool into
+
+Examples:
+
+    # install node@20.0.0 into ./mynode
+    $ mise install-into node@20.0.0 ./mynode && ./mynode/bin/node -v
+    20.0.0
+
 ## `mise latest`
 
 - **Usage**: `mise latest [-i --installed] <TOOL@VERSION>`
+- **Source code**: [`src/cli/latest.rs`](https://github.com/jdx/mise/blob/main/src/cli/latest.rs)
 
 Gets the latest available version for a plugin
 
@@ -952,6 +1279,7 @@ Examples:
 
 - **Usage**: `mise link [-f --force] <TOOL@VERSION> <PATH>`
 - **Aliases**: `ln`
+- **Source code**: [`src/cli/link.rs`](https://github.com/jdx/mise/blob/main/src/cli/link.rs)
 
 Symlinks a tool version into mise
 
@@ -975,7 +1303,7 @@ e.g.: ~/.nvm/versions/node/v20.0.0
 Overwrite an existing tool version if it exists
 
 Examples:
-    
+
     # build node-20.0.0 with node-build and link it into mise
     $ node-build 20.0.0 ~/.nodes/20.0.0
     $ mise link node@20.0.0 ~/.nodes/20.0.0
@@ -988,6 +1316,7 @@ Examples:
 ## `mise local`
 
 - **Usage**: `mise local [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/local.rs`](https://github.com/jdx/mise/blob/main/src/cli/local.rs)
 
 Sets/gets tool version in local .tool-versions or mise.toml
 
@@ -1050,8 +1379,9 @@ Examples:
 
 ## `mise ls`
 
-- **Usage**: `mise ls [FLAGS] [PLUGIN]...`
+- **Usage**: `mise ls [FLAGS] [INSTALLED_TOOL]...`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/ls.rs)
 
 List installed and active tool versions
 
@@ -1063,9 +1393,9 @@ It's a useful command to get the current state of your tools.
 
 ### Arguments
 
-#### `[PLUGIN]...`
+#### `[INSTALLED_TOOL]...`
 
-Only show tool versions from [PLUGIN]
+Only show tool versions from [TOOL]
 
 ### Flags
 
@@ -1081,6 +1411,14 @@ Only show tool versions currently specified in the global mise.toml
 
 Only show tool versions that are installed (Hides tools defined in mise.toml but not installed)
 
+#### `-o --offline`
+
+Don't fetch information such as outdated versions
+
+#### `--outdated`
+
+Display whether a version is outdated
+
 #### `-J --json`
 
 Output in JSON format
@@ -1126,6 +1464,7 @@ Examples:
 ## `mise ls-remote`
 
 - **Usage**: `mise ls-remote [--all] [TOOL@VERSION] [PREFIX]`
+- **Source code**: [`src/cli/ls_remote.rs`](https://github.com/jdx/mise/blob/main/src/cli/ls_remote.rs)
 
 List runtime versions available for install.
 
@@ -1135,7 +1474,7 @@ Note that the results may be cached, run `mise cache clean` to clear the cache a
 
 #### `[TOOL@VERSION]`
 
-Plugin to get versions for
+Tool to get versions for
 
 #### `[PREFIX]`
 
@@ -1165,6 +1504,7 @@ Examples:
 ## `mise outdated`
 
 - **Usage**: `mise outdated [FLAGS] [TOOL@VERSION]...`
+- **Source code**: [`src/cli/outdated.rs`](https://github.com/jdx/mise/blob/main/src/cli/outdated.rs)
 
 Shows outdated tool versions
 
@@ -1215,6 +1555,7 @@ Examples:
 
 - **Usage**: `mise plugins [FLAGS] <SUBCOMMAND>`
 - **Aliases**: `p`
+- **Source code**: [`src/cli/plugins/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/mod.rs)
 
 Manage plugins
 
@@ -1241,6 +1582,7 @@ e.g.: https://github.com/asdf-vm/asdf-nodejs.git
 
 - **Usage**: `mise plugins install [FLAGS] [NEW_PLUGIN] [GIT_URL]`
 - **Aliases**: `i`, `a`, `add`
+- **Source code**: [`src/cli/plugins/install.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/install.rs)
 
 Install a plugin
 
@@ -1294,8 +1636,9 @@ Examples:
 
 ## `mise plugins link`
 
-- **Usage**: `mise plugins link [-f --force] <NAME> [PATH]`
+- **Usage**: `mise plugins link [-f --force] <NAME> [DIR]`
 - **Aliases**: `ln`
+- **Source code**: [`src/cli/plugins/link.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/link.rs)
 
 Symlinks a plugin into mise
 
@@ -1308,7 +1651,7 @@ This is used for developing a plugin.
 The name of the plugin
 e.g.: node, ruby
 
-#### `[PATH]`
+#### `[DIR]`
 
 The local path to the plugin
 e.g.: ./mise-node
@@ -1329,8 +1672,9 @@ Examples:
 
 ## `mise plugins ls`
 
-- **Usage**: `mise plugins ls [FLAGS]`
+- **Usage**: `mise plugins ls [-u --urls]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/plugins/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/ls.rs)
 
 List installed plugins
 
@@ -1338,18 +1682,6 @@ Can also show remotely available plugins to install.
 
 ### Flags
 
-#### `-c --core`
-
-The built-in plugins only
-Normally these are not shown
-
-#### `--user`
-
-List installed plugins
-
-This is the default behavior but can be used with --core
-to show core and user plugins
-
 #### `-u --urls`
 
 Show the git url for each plugin
@@ -1369,6 +1701,7 @@ Examples:
 
 - **Usage**: `mise plugins ls-remote [-u --urls] [--only-names]`
 - **Aliases**: `list-remote`, `list-all`
+- **Source code**: [`src/cli/plugins/ls_remote.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/ls_remote.rs)
 
 
 List all available remote plugins
@@ -1393,6 +1726,7 @@ Only show the name of each plugin by default it will show a "*" next to installe
 
 - **Usage**: `mise plugins uninstall [-p --purge] [-a --all] [PLUGIN]...`
 - **Aliases**: `remove`, `rm`
+- **Source code**: [`src/cli/plugins/uninstall.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/uninstall.rs)
 
 Removes a plugin
 
@@ -1420,6 +1754,7 @@ Examples:
 
 - **Usage**: `mise plugins update [-j --jobs <JOBS>] [PLUGIN]...`
 - **Aliases**: `up`, `upgrade`
+- **Source code**: [`src/cli/plugins/update.rs`](https://github.com/jdx/mise/blob/main/src/cli/plugins/update.rs)
 
 Updates a plugin to the latest version
 
@@ -1446,20 +1781,21 @@ Examples:
 
 ## `mise prune`
 
-- **Usage**: `mise prune [FLAGS] [PLUGIN]...`
+- **Usage**: `mise prune [FLAGS] [INSTALLED_TOOL]...`
+- **Source code**: [`src/cli/prune.rs`](https://github.com/jdx/mise/blob/main/src/cli/prune.rs)
 
 Delete unused versions of tools
 
-mise tracks which config files have been used in ~/.local/share/mise/tracked_config_files
+mise tracks which config files have been used in ~/.local/state/mise/tracked-configs
 Versions which are no longer the latest specified in any of those configs are deleted.
 Versions installed only with environment variables `MISE_<PLUGIN>_VERSION` will be deleted,
 as will versions only referenced on the command line `mise exec <PLUGIN>@<VERSION>`.
 
 ### Arguments
 
-#### `[PLUGIN]...`
+#### `[INSTALLED_TOOL]...`
 
-Prune only versions from this plugin(s)
+Prune only these tools
 
 ### Flags
 
@@ -1483,14 +1819,31 @@ Examples:
 
 ## `mise registry`
 
-- **Usage**: `mise registry`
+- **Usage**: `mise registry [-b --backend <BACKEND>] [--hide-aliased] [NAME]`
+- **Source code**: [`src/cli/registry.rs`](https://github.com/jdx/mise/blob/main/src/cli/registry.rs)
 
-[experimental] List available tools to install
+List available tools to install
 
 This command lists the tools available in the registry as shorthand names.
 
 For example, `poetry` is shorthand for `asdf:mise-plugins/mise-poetry`.
 
+### Arguments
+
+#### `[NAME]`
+
+Show only the specified tool's full name
+
+### Flags
+
+#### `-b --backend <BACKEND>`
+
+Show only tools for this backend
+
+#### `--hide-aliased`
+
+Hide aliased tools
+
 Examples:
 
     $ mise registry
@@ -1498,9 +1851,13 @@ Examples:
     poetry  asdf:mise-plugins/mise-poetry
     ubi     cargo:ubi-cli
 
+    $ mise registry poetry
+    asdf:mise-plugins/mise-poetry
+
 ## `mise reshim`
 
 - **Usage**: `mise reshim [-f --force]`
+- **Source code**: [`src/cli/reshim.rs`](https://github.com/jdx/mise/blob/main/src/cli/reshim.rs)
 
 Creates new shims based on bin paths from currently installed tools.
 
@@ -1513,10 +1870,10 @@ If you think mise should automatically call this for a particular command, pleas
 open an issue on the mise repo. You can also setup a shell function to reshim
 automatically (it's really fast so you don't need to worry about overhead):
 
-npm() {
-  command npm "$@"
-  mise reshim
-}
+    npm() {
+      command npm "$@"
+      mise reshim
+    }
 
 Note that this creates shims for _all_ installed tools, not just the ones that are
 currently active in mise.toml.
@@ -1537,8 +1894,9 @@ Examples:
 
 - **Usage**: `mise run [FLAGS]`
 - **Aliases**: `r`
+- **Source code**: [`src/cli/run.rs`](https://github.com/jdx/mise/blob/main/src/cli/run.rs)
 
-[experimental] Run task(s)
+Run task(s)
 
 This command will run a tasks, or multiple tasks in parallel.
 Tasks may have dependencies on other tasks or on source files.
@@ -1570,6 +1928,10 @@ The name of the script will be the name of the tasks.
 
 Change to this directory before executing the command
 
+#### `-c --continue-on-error`
+
+Continue running tasks even if one fails
+
 #### `-n --dry-run`
 
 Don't actually run the tasks(s), just print them in order of execution
@@ -1578,21 +1940,17 @@ Don't actually run the tasks(s), just print them in order of execution
 
 Force the tasks to run even if outputs are up to date
 
-#### `-p --prefix`
-
-Print stdout/stderr by line, prefixed with the tasks's label
-Defaults to true if --jobs > 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+#### `-s --shell <SHELL>`
 
-#### `-i --interleave`
+Shell to use to run toml tasks
 
-Print directly to stdout/stderr instead of by line
-Defaults to true if --jobs == 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows
+Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`
+Or it can be overridden with the `shell` property on a task.
 
 #### `-t --tool... <TOOL@VERSION>`
 
-Tool(s) to also add e.g.: node@20 python@3.10
+Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
 
 #### `-j --jobs <JOBS>`
 
@@ -1605,9 +1963,31 @@ Configure with `jobs` config or `MISE_JOBS` env var
 Read/write directly to stdin/stdout/stderr instead of by line
 Configure with `raw` config or `MISE_RAW` env var
 
-#### `--timings`
+#### `--no-timings`
+
+Hides elapsed time after each task completes
 
-Shows elapsed time after each tasks
+Default to always hide with `MISE_TASK_TIMINGS=0`
+
+#### `-q --quiet`
+
+Don't show extra output
+
+#### `-S --silent`
+
+Don't show any output except for errors
+
+#### `-o --output <OUTPUT>`
+
+Change how tasks information is output when running tasks
+
+- `prefix` - Print stdout/stderr by line, prefixed with the task's label
+- `interleave` - Print directly to stdout/stderr instead of by line
+- `replacing` - Stdout is replaced each time, stderr is printed as is
+- `timed` - Only show stdout lines if they are displayed for more than 1 second
+- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output
+- `quiet` - Don't show extra output
+- `silent` - Don't show any output including stdout and stderr from the task except for errors
 
 Examples:
 
@@ -1631,6 +2011,7 @@ Examples:
 ## `mise self-update`
 
 - **Usage**: `mise self-update [FLAGS] [VERSION]`
+- **Source code**: [`src/cli/self_update.rs`](https://github.com/jdx/mise/blob/main/src/cli/self_update.rs)
 
 Updates mise itself.
 
@@ -1662,7 +2043,8 @@ Skip confirmation prompt
 
 ## `mise set`
 
-- **Usage**: `mise set [--file <FILE>] [-g --global] [ENV_VARS]...`
+- **Usage**: `mise set [--file <FILE>] [-g --global] [ENV_VAR]...`
+- **Source code**: [`src/cli/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/set.rs)
 
 Set environment variables in mise.toml
 
@@ -1670,7 +2052,7 @@ By default, this command modifies `mise.toml` in the current directory.
 
 ### Arguments
 
-#### `[ENV_VARS]...`
+#### `[ENV_VAR]...`
 
 Environment variable(s) to set
 e.g.: NODE_ENV=production
@@ -1700,19 +2082,67 @@ Examples:
 
 ## `mise settings`
 
-- **Usage**: `mise settings [--keys] <SUBCOMMAND>`
+- **Usage**: `mise settings [FLAGS] [SETTING] [VALUE] <SUBCOMMAND>`
+- **Source code**: [`src/cli/settings/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/mod.rs)
+
+Show current settings
+
+This is the contents of ~/.config/mise/config.toml
+
+Note that aliases are also stored in this file
+but managed separately with `mise aliases`
+
+### Arguments
+
+#### `[SETTING]`
+
+Name of setting
+
+#### `[VALUE]`
+
+Setting value to set
+
+### Global Flags
+
+#### `-l --local`
 
-Manage settings
+Use the local config file instead of the global one
 
 ### Flags
 
-#### `--keys`
+#### `-a --all`
+
+List all settings
+
+#### `-J --json`
+
+Output in JSON format
+
+#### `--json-extended`
+
+Output in JSON format with sources
 
-Only display key names for each setting
+#### `-T --toml`
+
+Output in TOML format
+
+Examples:
+    # list all settings
+    $ mise settings
+
+    # get the value of the setting "always_keep_download"
+    $ mise settings always_keep_download
+
+    # set the value of the setting "always_keep_download" to "true"
+    $ mise settings always_keep_download=true
+
+    # set the value of the setting "node.mirror_url" to "https://npm.taobao.org/mirrors/node"
+    $ mise settings node.mirror_url https://npm.taobao.org/mirrors/node
 
 ## `mise settings add`
 
-- **Usage**: `mise settings add <SETTING> <VALUE>`
+- **Usage**: `mise settings add [-l --local] <SETTING> <VALUE>`
+- **Source code**: [`src/cli/settings/add.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/add.rs)
 
 Adds a setting to the configuration file
 
@@ -1729,13 +2159,20 @@ The setting to set
 
 The value to set
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
     $ mise settings add disable_hints python_multi
 
 ## `mise settings get`
 
-- **Usage**: `mise settings get <SETTING>`
+- **Usage**: `mise settings get [-l --local] <SETTING>`
+- **Source code**: [`src/cli/settings/get.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/get.rs)
 
 Show a current setting
 
@@ -1750,15 +2187,22 @@ but managed separately with `mise aliases get`
 
 The setting to show
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings get legacy_version_file
+    $ mise settings get idiomatic_version_file
     true
 
 ## `mise settings ls`
 
-- **Usage**: `mise settings ls [--keys]`
+- **Usage**: `mise settings ls [FLAGS] [SETTING]`
 - **Aliases**: `list`
+- **Source code**: [`src/cli/settings/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/ls.rs)
 
 Show current settings
 
@@ -1767,21 +2211,49 @@ This is the contents of ~/.config/mise/config.toml
 Note that aliases are also stored in this file
 but managed separately with `mise aliases`
 
-### Flags
+### Arguments
+
+#### `[SETTING]`
+
+Name of setting
+
+### Flags
+
+#### `-a --all`
+
+List all settings
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
+#### `-J --json`
+
+Output in JSON format
 
-#### `--keys`
+#### `--json-extended`
 
-Only display key names for each setting
+Output in JSON format with sources
+
+#### `-T --toml`
+
+Output in TOML format
 
 Examples:
 
-    $ mise settings
-    legacy_version_file = false
+    $ mise settings ls
+    idiomatic_version_file = false
+    ...
+
+    $ mise settings ls python
+    default_packages_file = "~/.default-python-packages"
+    ...
 
 ## `mise settings set`
 
-- **Usage**: `mise settings set <SETTING> <VALUE>`
+- **Usage**: `mise settings set [-l --local] <SETTING> <VALUE>`
 - **Aliases**: `create`
+- **Source code**: [`src/cli/settings/set.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/set.rs)
 
 Add/update a setting
 
@@ -1797,14 +2269,21 @@ The setting to set
 
 The value to set
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings set legacy_version_file true
+    $ mise settings idiomatic_version_file=true
 
 ## `mise settings unset`
 
-- **Usage**: `mise settings unset <SETTING>`
+- **Usage**: `mise settings unset [-l --local] <KEY>`
 - **Aliases**: `rm`, `remove`, `delete`, `del`
+- **Source code**: [`src/cli/settings/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/settings/unset.rs)
 
 Clears a setting
 
@@ -1812,18 +2291,25 @@ This modifies the contents of ~/.config/mise/config.toml
 
 ### Arguments
 
-#### `<SETTING>`
+#### `<KEY>`
 
 The setting to remove
 
+### Flags
+
+#### `-l --local`
+
+Use the local config file instead of the global one
+
 Examples:
 
-    $ mise settings unset legacy_version_file
+    $ mise settings unset idiomatic_version_file
 
 ## `mise shell`
 
-- **Usage**: `mise shell [FLAGS] [TOOL@VERSION]...`
+- **Usage**: `mise shell [FLAGS] <TOOL@VERSION>...`
 - **Aliases**: `sh`
+- **Source code**: [`src/cli/shell.rs`](https://github.com/jdx/mise/blob/main/src/cli/shell.rs)
 
 Sets a tool version for the current session.
 
@@ -1834,7 +2320,7 @@ such as `MISE_NODE_VERSION=20` which is "eval"ed as a shell function created by
 
 ### Arguments
 
-#### `[TOOL@VERSION]...`
+#### `<TOOL@VERSION>...`
 
 Tool(s) to use
 
@@ -1862,17 +2348,21 @@ Examples:
 ## `mise sync`
 
 - **Usage**: `mise sync <SUBCOMMAND>`
+- **Source code**: [`src/cli/sync/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/mod.rs)
 
-Add tool versions from external tools to mise
+Synchronize tools from other version managers with mise
 
 ## `mise sync node`
 
 - **Usage**: `mise sync node [FLAGS]`
+- **Source code**: [`src/cli/sync/node.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/node.rs)
 
 Symlinks all tool versions from an external tool into mise
 
 For example, use this to import all Homebrew node installs into mise
 
+This won't overwrite any existing installs but will overwrite any existing symlinks
+
 ### Flags
 
 #### `--brew`
@@ -1895,32 +2385,71 @@ Examples:
 
 ## `mise sync python`
 
-- **Usage**: `mise sync python <--pyenv>`
+- **Usage**: `mise sync python [--pyenv] [--uv]`
+- **Source code**: [`src/cli/sync/python.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/python.rs)
 
 Symlinks all tool versions from an external tool into mise
 
 For example, use this to import all pyenv installs into mise
 
+This won't overwrite any existing installs but will overwrite any existing symlinks
+
 ### Flags
 
 #### `--pyenv`
 
 Get tool versions from pyenv
 
+#### `--uv`
+
+Sync tool versions with uv (2-way sync)
+
 Examples:
 
     $ pyenv install 3.11.0
     $ mise sync python --pyenv
     $ mise use -g python@3.11.0 - uses pyenv-provided python
+    
+    $ uv python install 3.11.0
+    $ mise install python@3.10.0
+    $ mise sync python --uv
+    $ mise x python@3.11.0 -- python -V - uses uv-provided python
+    $ uv run -p 3.10.0 -- python -V - uses mise-provided python
+
+## `mise sync ruby`
+
+- **Usage**: `mise sync ruby [--brew]`
+- **Source code**: [`src/cli/sync/ruby.rs`](https://github.com/jdx/mise/blob/main/src/cli/sync/ruby.rs)
+
+Symlinks all ruby tool versions from an external tool into mise
+
+### Flags
+
+#### `--brew`
+
+Get tool versions from Homebrew
+
+Examples:
+
+    $ brew install ruby
+    $ mise sync ruby --brew
+    $ mise use -g ruby - Use the latest version of Ruby installed by Homebrew
 
 ## `mise tasks`
 
-- **Usage**: `mise tasks [FLAGS] <SUBCOMMAND>`
+- **Usage**: `mise tasks [FLAGS] [TASK] <SUBCOMMAND>`
 - **Aliases**: `t`
+- **Source code**: [`src/cli/tasks/mod.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/mod.rs)
 
-[experimental] Manage tasks
+Manage tasks
 
-### Flags
+### Arguments
+
+#### `[TASK]`
+
+Task name to get info of
+
+### Global Flags
 
 #### `--no-header`
 
@@ -1962,11 +2491,93 @@ Examples:
 
     $ mise tasks ls
 
+## `mise tasks add`
+
+- **Usage**: `mise tasks add [FLAGS] <TASK> [-- RUN]...`
+- **Source code**: [`src/cli/tasks/add.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/add.rs)
+
+Create a new task
+
+### Arguments
+
+#### `<TASK>`
+
+Tasks name to add
+
+#### `[-- RUN]...`
+
+### Flags
+
+#### `--description <DESCRIPTION>`
+
+Description of the task
+
+#### `-a --alias... <ALIAS>`
+
+Other names for the task
+
+#### `--depends-post... <DEPENDS_POST>`
+
+Dependencies to run after the task runs
+
+#### `-w --wait-for... <WAIT_FOR>`
+
+Wait for these tasks to complete if they are to run
+
+#### `-D --dir <DIR>`
+
+Run the task in a specific directory
+
+#### `-H --hide`
+
+Hide the task from `mise task` and completions
+
+#### `-r --raw`
+
+Directly connect stdin/stdout/stderr
+
+#### `-s --sources... <SOURCES>`
+
+Glob patterns of files this task uses as input
+
+#### `--outputs... <OUTPUTS>`
+
+Glob patterns of files this task creates, to skip if they are not modified
+
+#### `--shell <SHELL>`
+
+Run the task in a specific shell
+
+#### `-q --quiet`
+
+Do not print the command before running
+
+#### `--silent`
+
+Do not print the command or its output
+
+#### `-d --depends... <DEPENDS>`
+
+Add dependencies to the task
+
+#### `--run-windows <RUN_WINDOWS>`
+
+Command to run on windows
+
+#### `-f --file`
+
+Create a file task instead of a toml task
+
+Examples:
+
+    $ mise task add pre-commit --depends "test" --depends "render" -- echo pre-commit
+
 ## `mise tasks deps`
 
 - **Usage**: `mise tasks deps [--hidden] [--dot] [TASKS]...`
+- **Source code**: [`src/cli/tasks/deps.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/deps.rs)
 
-[experimental] Display a tree visualization of a dependency graph
+Display a tree visualization of a dependency graph
 
 ### Arguments
 
@@ -2000,8 +2611,9 @@ Examples:
 ## `mise tasks edit`
 
 - **Usage**: `mise tasks edit [-p --path] <TASK>`
+- **Source code**: [`src/cli/tasks/edit.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/edit.rs)
 
-[experimental] Edit a tasks with $EDITOR
+Edit a tasks with $EDITOR
 
 The tasks will be created as a standalone script if it does not already exist.
 
@@ -2025,8 +2637,9 @@ Examples:
 ## `mise tasks info`
 
 - **Usage**: `mise tasks info [-J --json] <TASK>`
+- **Source code**: [`src/cli/tasks/info.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/info.rs)
 
-[experimental] Get information about a task
+Get information about a task
 
 ### Arguments
 
@@ -2071,8 +2684,9 @@ Examples:
 ## `mise tasks ls`
 
 - **Usage**: `mise tasks ls [FLAGS]`
+- **Source code**: [`src/cli/tasks/ls.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/ls.rs)
 
-[experimental] List available tasks to execute
+List available tasks to execute
 These may be included from the config file or from the project's .mise/tasks directory
 mise will merge all tasks from all parent directories into this list.
 
@@ -2126,8 +2740,9 @@ Examples:
 
 - **Usage**: `mise tasks run [FLAGS] [TASK] [ARGS]...`
 - **Aliases**: `r`
+- **Source code**: [`src/cli/tasks/run.rs`](https://github.com/jdx/mise/blob/main/src/cli/tasks/run.rs)
 
-[experimental] Run task(s)
+Run task(s)
 
 This command will run a tasks, or multiple tasks in parallel.
 Tasks may have dependencies on other tasks or on source files.
@@ -2173,6 +2788,10 @@ Arguments to pass to the tasks. Use ":::" to separate tasks
 
 Change to this directory before executing the command
 
+#### `-c --continue-on-error`
+
+Continue running tasks even if one fails
+
 #### `-n --dry-run`
 
 Don't actually run the tasks(s), just print them in order of execution
@@ -2181,21 +2800,17 @@ Don't actually run the tasks(s), just print them in order of execution
 
 Force the tasks to run even if outputs are up to date
 
-#### `-p --prefix`
-
-Print stdout/stderr by line, prefixed with the tasks's label
-Defaults to true if --jobs > 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+#### `-s --shell <SHELL>`
 
-#### `-i --interleave`
+Shell to use to run toml tasks
 
-Print directly to stdout/stderr instead of by line
-Defaults to true if --jobs == 1
-Configure with `task_output` config or `MISE_TASK_OUTPUT` env var
+Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows
+Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`
+Or it can be overridden with the `shell` property on a task.
 
 #### `-t --tool... <TOOL@VERSION>`
 
-Tool(s) to also add e.g.: node@20 python@3.10
+Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
 
 #### `-j --jobs <JOBS>`
 
@@ -2208,9 +2823,31 @@ Configure with `jobs` config or `MISE_JOBS` env var
 Read/write directly to stdin/stdout/stderr instead of by line
 Configure with `raw` config or `MISE_RAW` env var
 
-#### `--timings`
+#### `--no-timings`
+
+Hides elapsed time after each task completes
 
-Shows elapsed time after each tasks
+Default to always hide with `MISE_TASK_TIMINGS=0`
+
+#### `-q --quiet`
+
+Don't show extra output
+
+#### `-S --silent`
+
+Don't show any output except for errors
+
+#### `-o --output <OUTPUT>`
+
+Change how tasks information is output when running tasks
+
+- `prefix` - Print stdout/stderr by line, prefixed with the task's label
+- `interleave` - Print directly to stdout/stderr instead of by line
+- `replacing` - Stdout is replaced each time, stderr is printed as is
+- `timed` - Only show stdout lines if they are displayed for more than 1 second
+- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output
+- `quiet` - Don't show extra output
+- `silent` - Don't show any output including stdout and stderr from the task except for errors
 
 Examples:
 
@@ -2231,9 +2868,99 @@ Examples:
     # Execute multiple tasks each with their own arguments.
     $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2
 
+## `mise test-tool`
+
+- **Usage**: `mise test-tool [FLAGS] [TOOL]`
+- **Source code**: [`src/cli/test_tool.rs`](https://github.com/jdx/mise/blob/main/src/cli/test_tool.rs)
+
+Test a tool installs and executes
+
+### Arguments
+
+#### `[TOOL]`
+
+### Flags
+
+#### `-a --all`
+
+#### `--include-non-defined`
+
+Also test tools not defined in registry.toml, guessing how to test it
+
+#### `-j --jobs <JOBS>`
+
+Number of jobs to run in parallel
+[default: 4]
+
+#### `--raw`
+
+Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1
+
+Examples:
+
+    $ mise test-tool ripgrep
+
+## `mise tool`
+
+- **Usage**: `mise tool [FLAGS] <TOOL>`
+- **Source code**: [`src/cli/tool.rs`](https://github.com/jdx/mise/blob/main/src/cli/tool.rs)
+
+Gets information about a tool
+
+### Arguments
+
+#### `<TOOL>`
+
+Tool name to get information about
+
+### Flags
+
+#### `-J --json`
+
+Output in JSON format
+
+#### `--backend`
+
+Only show backend field
+
+#### `--description`
+
+Only show description field
+
+#### `--installed`
+
+Only show installed versions
+
+#### `--active`
+
+Only show active versions
+
+#### `--requested`
+
+Only show requested versions
+
+#### `--config-source`
+
+Only show config source
+
+#### `--tool-options`
+
+Only show tool options
+
+Examples:
+
+    $ mise tool node
+    Backend:            core
+    Installed Versions: 20.0.0 22.0.0
+    Active Version:     20.0.0
+    Requested Version:  20
+    Config Source:      ~/.config/mise/mise.toml
+    Tool Options:       [none]
+
 ## `mise trust`
 
 - **Usage**: `mise trust [FLAGS] [CONFIG_FILE]`
+- **Source code**: [`src/cli/trust.rs`](https://github.com/jdx/mise/blob/main/src/cli/trust.rs)
 
 Marks a config file as trusted
 
@@ -2257,9 +2984,13 @@ The config file to trust
 
 Trust all config files in the current directory and its parents
 
+#### `--ignore`
+
+Do not trust this config and ignore it in the future
+
 #### `--untrust`
 
-No longer trust this config
+No longer trust this config, will prompt in the future
 
 #### `--show`
 
@@ -2277,7 +3008,7 @@ Examples:
 ## `mise uninstall`
 
 - **Usage**: `mise uninstall [-a --all] [-n --dry-run] [INSTALLED_TOOL@VERSION]...`
-- **Aliases**: `remove`, `rm`
+- **Source code**: [`src/cli/uninstall.rs`](https://github.com/jdx/mise/blob/main/src/cli/uninstall.rs)
 
 Removes installed tool versions
 
@@ -2312,7 +3043,8 @@ Examples:
 
 ## `mise unset`
 
-- **Usage**: `mise unset [-f --file <FILE>] [-g --global] [KEYS]...`
+- **Usage**: `mise unset [-f --file <FILE>] [-g --global] [ENV_KEY]...`
+- **Source code**: [`src/cli/unset.rs`](https://github.com/jdx/mise/blob/main/src/cli/unset.rs)
 
 Remove environment variable(s) from the config file.
 
@@ -2320,7 +3052,7 @@ By default, this command modifies `mise.toml` in the current directory.
 
 ### Arguments
 
-#### `[KEYS]...`
+#### `[ENV_KEY]...`
 
 Environment variable(s) to remove
 e.g.: NODE_ENV
@@ -2343,10 +3075,42 @@ Examples:
     # Remove NODE_ENV from the global config
     $ mise unset NODE_ENV -g
 
+## `mise unuse`
+
+- **Usage**: `mise unuse [--no-prune] [--global] <INSTALLED_TOOL@VERSION>...`
+- **Aliases**: `rm`, `remove`
+- **Source code**: [`src/cli/unuse.rs`](https://github.com/jdx/mise/blob/main/src/cli/unuse.rs)
+
+Removes installed tool versions from mise.toml
+
+Will also prune the installed version if no other configurations are using it.
+
+### Arguments
+
+#### `<INSTALLED_TOOL@VERSION>...`
+
+Tool(s) to remove
+
+### Flags
+
+#### `--no-prune`
+
+Do not also prune the installed version
+
+#### `--global`
+
+Remove tool from global config
+
+Examples:
+
+    # will uninstall specific version
+    $ mise remove node@18.0.0
+
 ## `mise upgrade`
 
 - **Usage**: `mise upgrade [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `up`
+- **Source code**: [`src/cli/upgrade.rs`](https://github.com/jdx/mise/blob/main/src/cli/upgrade.rs)
 
 Upgrades outdated tools
 
@@ -2354,6 +3118,8 @@ By default, this keeps the range specified in mise.toml. So if you have node@20
 upgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version
 and bump the version in mise.toml.
 
+This will update mise.lock if it is enabled, see https://mise.jdx.dev/configuration/settings.html#lockfile
+
 ### Arguments
 
 #### `[TOOL@VERSION]...`
@@ -2417,6 +3183,7 @@ Examples:
 ## `mise usage`
 
 - **Usage**: `mise usage`
+- **Source code**: [`src/cli/usage.rs`](https://github.com/jdx/mise/blob/main/src/cli/usage.rs)
 
 Generate a usage CLI spec
 
@@ -2426,12 +3193,19 @@ See https://usage.jdx.dev for more information on this specification.
 
 - **Usage**: `mise use [FLAGS] [TOOL@VERSION]...`
 - **Aliases**: `u`
+- **Source code**: [`src/cli/use.rs`](https://github.com/jdx/mise/blob/main/src/cli/use.rs)
 
-Installs a tool and adds the version it to mise.toml.
+Installs a tool and adds the version to mise.toml.
 
 This will install the tool version if it is not already installed.
 By default, this will use a `mise.toml` file in the current directory.
 
+In the following order:
+  - If `MISE_DEFAULT_CONFIG_FILENAME` is set, it will use that instead.
+  - If `MISE_OVERRIDE_CONFIG_FILENAMES` is set, it will the first from that list.
+  - If `MISE_ENV` is set, it will use a `mise.<env>.toml` instead.
+  - Otherwise just "mise.toml"
+
 Use the `--global` flag to use the global config file instead.
 
 ### Arguments
@@ -2443,6 +3217,10 @@ Tool(s) to add to config file
 e.g.: node@20, cargo:ripgrep@latest npm:prettier@3
 If no version is specified, it will default to @latest
 
+Tool options can be set with this syntax:
+
+    mise use ubi:BurntSushi/ripgrep[exe=rg]
+
 ### Flags
 
 #### `-f --force`
@@ -2454,7 +3232,7 @@ Force reinstall even if already installed
 Save fuzzy version to config file
 
 e.g.: `mise use --fuzzy node@20` will save 20 as the version
-this is the default behavior unless `MISE_PIN=1` or `MISE_ASDF_COMPAT=1`
+this is the default behavior unless `MISE_PIN=1`
 
 #### `-g --global`
 
@@ -2462,7 +3240,7 @@ Use the global config file (`~/.config/mise/config.toml`) instead of the local o
 
 #### `-e --env <ENV>`
 
-Modify an environment-specific config file like .mise.<env>.toml
+Create/modify an environment-specific config file like .mise.<env>.toml
 
 #### `-j --jobs <JOBS>`
 
@@ -2481,15 +3259,21 @@ Remove the plugin(s) from config file
 
 Specify a path to a config file or directory
 
-If a directory is specified, it will look for `mise.toml` (default) or `.tool-versions` if `MISE_ASDF_COMPAT=1`
+If a directory is specified, it will look for a config file in that directory following the rules above.
 
 #### `--pin`
 
 Save exact version to config file
 e.g.: `mise use --pin node@20` will save 20.0.0 as the version
-Set `MISE_PIN=1` or `MISE_ASDF_COMPAT=1` to make this the default behavior
+Set `MISE_PIN=1` to make this the default behavior
+
+Consider using mise.lock as a better alternative to pinning in mise.toml:
+https://mise.jdx.dev/configuration/settings.html#lockfile
 
 Examples:
+    
+    # run with no arguments to use the interactive selector
+    $ mise use
 
     # set the current version of node to 20.x in mise.toml of current directory
     # will write the fuzzy version (e.g.: 20)
@@ -2509,6 +3293,7 @@ Examples:
 
 - **Usage**: `mise version`
 - **Aliases**: `v`
+- **Source code**: [`src/cli/version.rs`](https://github.com/jdx/mise/blob/main/src/cli/version.rs)
 
 Display the version of mise
 
@@ -2525,47 +3310,626 @@ Examples:
 
 ## `mise watch`
 
-- **Usage**: `mise watch [-t --task... <TASK>] [-g --glob... <GLOB>] [ARGS]...`
+- **Usage**: `mise watch [FLAGS] [TASK] [ARGS]...`
 - **Aliases**: `w`
+- **Source code**: [`src/cli/watch.rs`](https://github.com/jdx/mise/blob/main/src/cli/watch.rs)
 
-[experimental] Run task(s) and watch for changes to rerun it
+Run task(s) and watch for changes to rerun it
 
 This command uses the `watchexec` tool to watch for changes to files and rerun the specified task(s).
 It must be installed for this command to work, but you can install it with `mise use -g watchexec@latest`.
 
 ### Arguments
 
+#### `[TASK]`
+
+Tasks to run
+Can specify multiple tasks by separating with `:::`
+e.g.: `mise run task1 arg1 arg2 ::: task2 arg1 arg2`
+
 #### `[ARGS]...`
 
-Extra arguments
+Task and arguments to run
 
 ### Flags
 
-#### `-t --task... <TASK>`
+#### `-w --watch... <PATH>`
 
-Tasks to run
+Watch a specific file or directory
+
+By default, Watchexec watches the current directory.
+
+When watching a single file, it's often better to watch the containing directory instead, and filter on the filename. Some editors may replace the file with a new one when saving, and some platforms may not detect that or further changes.
+
+Upon starting, Watchexec resolves a "project origin" from the watched paths. See the help for '--project-origin' for more information.
+
+This option can be specified multiple times to watch multiple files or directories.
+
+The special value '/dev/null', provided as the only path watched, will cause Watchexec to not watch any paths. Other event sources (like signals or key events) may still be used.
+
+#### `-W --watch-non-recursive... <PATH>`
+
+Watch a specific directory, non-recursively
+
+Unlike '-w', folders watched with this option are not recursed into.
+
+This option can be specified multiple times to watch multiple directories non-recursively.
+
+#### `-F --watch-file <PATH>`
+
+Watch files and directories from a file
+
+Each line in the file will be interpreted as if given to '-w'.
+
+For more complex uses (like watching non-recursively), use the argfile capability: build a file containing command-line options and pass it to watchexec with `@path/to/argfile`.
+
+The special value '-' will read from STDIN; this in incompatible with '--stdin-quit'.
+
+#### `-c --clear <MODE>`
+
+Clear screen before running command
+
+If this doesn't completely clear the screen, try '--clear=reset'.
+
+**Choices:**
+
+- `clear`
+- `reset`
+
+#### `-o --on-busy-update <MODE>`
+
+What to do when receiving events while the command is running
+
+Default is to 'do-nothing', which ignores events while the command is running, so that changes that occur due to the command are ignored, like compilation outputs. You can also use 'queue' which will run the command once again when the current run has finished if any events occur while it's running, or 'restart', which terminates the running command and starts a new one. Finally, there's 'signal', which only sends a signal; this can be useful with programs that can reload their configuration without a full restart.
+
+The signal can be specified with the '--signal' option.
+
+**Choices:**
+
+- `queue`
+- `do-nothing`
+- `restart`
+- `signal`
+
+#### `-r --restart`
+
+Restart the process if it's still running
+
+This is a shorthand for '--on-busy-update=restart'.
+
+#### `-s --signal <SIGNAL>`
+
+Send a signal to the process when it's still running
+
+Specify a signal to send to the process when it's still running. This implies '--on-busy-update=signal'; otherwise the signal used when that mode is 'restart' is controlled by '--stop-signal'.
+
+See the long documentation for '--stop-signal' for syntax.
+
+Signals are not supported on Windows at the moment, and will always be overridden to 'kill'. See '--stop-signal' for more on Windows "signals".
+
+#### `--stop-signal <SIGNAL>`
+
+Signal to send to stop the command
+
+This is used by 'restart' and 'signal' modes of '--on-busy-update' (unless '--signal' is provided). The restart behaviour is to send the signal, wait for the command to exit, and if it hasn't exited after some time (see '--timeout-stop'), forcefully terminate it.
+
+The default on unix is "SIGTERM".
+
+Input is parsed as a full signal name (like "SIGTERM"), a short signal name (like "TERM"), or a signal number (like "15"). All input is case-insensitive.
+
+On Windows this option is technically supported but only supports the "KILL" event, as Watchexec cannot yet deliver other events. Windows doesn't have signals as such; instead it has termination (here called "KILL" or "STOP") and "CTRL+C", "CTRL+BREAK", and "CTRL+CLOSE" events. For portability the unix signals "SIGKILL", "SIGINT", "SIGTERM", and "SIGHUP" are respectively mapped to these.
+
+#### `--stop-timeout <TIMEOUT>`
+
+Time to wait for the command to exit gracefully
+
+This is used by the 'restart' mode of '--on-busy-update'. After the graceful stop signal is sent, Watchexec will wait for the command to exit. If it hasn't exited after this time, it is forcefully terminated.
+
+Takes a unit-less value in seconds, or a time span value such as "5min 20s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+The default is 10 seconds. Set to 0 to immediately force-kill the command.
+
+This has no practical effect on Windows as the command is always forcefully terminated; see '--stop-signal' for why.
+
+#### `--map-signal... <SIGNAL:SIGNAL>`
+
+Translate signals from the OS to signals to send to the command
+
+Takes a pair of signal names, separated by a colon, such as "TERM:INT" to map SIGTERM to SIGINT. The first signal is the one received by watchexec, and the second is the one sent to the command. The second can be omitted to discard the first signal, such as "TERM:" to not do anything on SIGTERM.
+
+If SIGINT or SIGTERM are mapped, then they no longer quit Watchexec. Besides making it hard to quit Watchexec itself, this is useful to send pass a Ctrl-C to the command without also terminating Watchexec and the underlying program with it, e.g. with "INT:INT".
+
+This option can be specified multiple times to map multiple signals.
+
+Signal syntax is case-insensitive for short names (like "TERM", "USR2") and long names (like "SIGKILL", "SIGHUP"). Signal numbers are also supported (like "15", "31"). On Windows, the forms "STOP", "CTRL+C", and "CTRL+BREAK" are also supported to receive, but Watchexec cannot yet deliver other "signals" than a STOP.
+
+#### `-d --debounce <TIMEOUT>`
+
+Time to wait for new events before taking action
+
+When an event is received, Watchexec will wait for up to this amount of time before handling it (such as running the command). This is essential as what you might perceive as a single change may actually emit many events, and without this behaviour, Watchexec would run much too often. Additionally, it's not infrequent that file writes are not atomic, and each write may emit an event, so this is a good way to avoid running a command while a file is partially written.
+
+An alternative use is to set a high value (like "30min" or longer), to save power or bandwidth on intensive tasks, like an ad-hoc backup script. In those use cases, note that every accumulated event will build up in memory.
+
+Takes a unit-less value in milliseconds, or a time span value such as "5sec 20ms". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+The default is 50 milliseconds. Setting to 0 is highly discouraged.
+
+#### `--stdin-quit`
+
+Exit when stdin closes
+
+This watches the stdin file descriptor for EOF, and exits Watchexec gracefully when it is closed. This is used by some process managers to avoid leaving zombie processes around.
+
+#### `--no-vcs-ignore`
+
+Don't load gitignores
+
+Among other VCS exclude files, like for Mercurial, Subversion, Bazaar, DARCS, Fossil. Note that Watchexec will detect which of these is in use, if any, and only load the relevant files. Both global (like '~/.gitignore') and local (like '.gitignore') files are considered.
+
+This option is useful if you want to watch files that are ignored by Git.
+
+#### `--no-project-ignore`
+
+Don't load project-local ignores
+
+This disables loading of project-local ignore files, like '.gitignore' or '.ignore' in the
+watched project. This is contrasted with '--no-vcs-ignore', which disables loading of Git
+and other VCS ignore files, and with '--no-global-ignore', which disables loading of global
+or user ignore files, like '~/.gitignore' or '~/.config/watchexec/ignore'.
+
+Supported project ignore files:
+
+  - Git: .gitignore at project root and child directories, .git/info/exclude, and the file pointed to by `core.excludesFile` in .git/config.
+  - Mercurial: .hgignore at project root and child directories.
+  - Bazaar: .bzrignore at project root.
+  - Darcs: _darcs/prefs/boring
+  - Fossil: .fossil-settings/ignore-glob
+  - Ripgrep/Watchexec/generic: .ignore at project root and child directories.
+
+VCS ignore files (Git, Mercurial, Bazaar, Darcs, Fossil) are only used if the corresponding
+VCS is discovered to be in use for the project/origin. For example, a .bzrignore in a Git
+repository will be discarded.
+
+#### `--no-global-ignore`
 
-#### `-g --glob... <GLOB>`
+Don't load global ignores
 
-Files to watch
-Defaults to sources from the tasks(s)
+This disables loading of global or user ignore files, like '~/.gitignore',
+'~/.config/watchexec/ignore', or '%APPDATA%\Bazzar\2.0\ignore'. Contrast with
+'--no-vcs-ignore' and '--no-project-ignore'.
+
+Supported global ignore files
+
+  - Git (if core.excludesFile is set): the file at that path
+  - Git (otherwise): the first found of $XDG_CONFIG_HOME/git/ignore, %APPDATA%/.gitignore, %USERPROFILE%/.gitignore, $HOME/.config/git/ignore, $HOME/.gitignore.
+  - Bazaar: the first found of %APPDATA%/Bazzar/2.0/ignore, $HOME/.bazaar/ignore.
+  - Watchexec: the first found of $XDG_CONFIG_HOME/watchexec/ignore, %APPDATA%/watchexec/ignore, %USERPROFILE%/.watchexec/ignore, $HOME/.watchexec/ignore.
+
+Like for project files, Git and Bazaar global files will only be used for the corresponding
+VCS as used in the project.
+
+#### `--no-default-ignore`
+
+Don't use internal default ignores
+
+Watchexec has a set of default ignore patterns, such as editor swap files, `*.pyc`, `*.pyo`, `.DS_Store`, `.bzr`, `_darcs`, `.fossil-settings`, `.git`, `.hg`, `.pijul`, `.svn`, and Watchexec log files.
+
+#### `--no-discover-ignore`
+
+Don't discover ignore files at all
+
+This is a shorthand for '--no-global-ignore', '--no-vcs-ignore', '--no-project-ignore', but even more efficient as it will skip all the ignore discovery mechanisms from the get go.
+
+Note that default ignores are still loaded, see '--no-default-ignore'.
+
+#### `--ignore-nothing`
+
+Don't ignore anything at all
+
+This is a shorthand for '--no-discover-ignore', '--no-default-ignore'.
+
+Note that ignores explicitly loaded via other command line options, such as '--ignore' or '--ignore-file', will still be used.
+
+#### `-p --postpone`
+
+Wait until first change before running command
+
+By default, Watchexec will run the command once immediately. With this option, it will instead wait until an event is detected before running the command as normal.
+
+#### `--delay-run <DURATION>`
+
+Sleep before running the command
+
+This option will cause Watchexec to sleep for the specified amount of time before running the command, after an event is detected. This is like using "sleep 5 && command" in a shell, but portable and slightly more efficient.
+
+Takes a unit-less value in seconds, or a time span value such as "2min 5s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+#### `--poll <INTERVAL>`
+
+Poll for filesystem changes
+
+By default, and where available, Watchexec uses the operating system's native file system watching capabilities. This option disables that and instead uses a polling mechanism, which is less efficient but can work around issues with some file systems (like network shares) or edge cases.
+
+Optionally takes a unit-less value in milliseconds, or a time span value such as "2s 500ms", to use as the polling interval. If not specified, the default is 30 seconds. Providing a unit-less value is deprecated and will warn; it will be an error in the future.
+
+Aliased as '--force-poll'.
+
+#### `--shell <SHELL>`
+
+Use a different shell
+
+By default, Watchexec will use '$SHELL' if it's defined or a default of 'sh' on Unix-likes, and either 'pwsh', 'powershell', or 'cmd' (CMD.EXE) on Windows, depending on what Watchexec detects is the running shell.
+
+With this option, you can override that and use a different shell, for example one with more features or one which has your custom aliases and functions.
+
+If the value has spaces, it is parsed as a command line, and the first word used as the shell program, with the rest as arguments to the shell.
+
+The command is run with the '-c' flag (except for 'cmd' on Windows, where it's '/C').
+
+The special value 'none' can be used to disable shell use entirely. In that case, the command provided to Watchexec will be parsed, with the first word being the executable and the rest being the arguments, and executed directly. Note that this parsing is rudimentary, and may not work as expected in all cases.
+
+Using 'none' is a little more efficient and can enable a stricter interpretation of the input, but it also means that you can't use shell features like globbing, redirection, control flow, logic, or pipes.
 
 Examples:
-    
-    $ mise watch -t build
+
+Use without shell:
+
+$ watchexec -n -- zsh -x -o shwordsplit scr
+
+Use with powershell core:
+
+$ watchexec --shell=pwsh -- Test-Connection localhost
+
+Use with CMD.exe:
+
+$ watchexec --shell=cmd -- dir
+
+Use with a different unix shell:
+
+$ watchexec --shell=bash -- 'echo $BASH_VERSION'
+
+Use with a unix shell and options:
+
+$ watchexec --shell='zsh -x -o shwordsplit' -- scr
+
+#### `-n`
+
+Shorthand for '--shell=none'
+
+#### `--emit-events-to <MODE>`
+
+Configure event emission
+
+Watchexec can emit event information when running a command, which can be used by the child
+process to target specific changed files.
+
+One thing to take care with is assuming inherent behaviour where there is only chance.
+Notably, it could appear as if the `RENAMED` variable contains both the original and the new
+path being renamed. In previous versions, it would even appear on some platforms as if the
+original always came before the new. However, none of this was true. It's impossible to
+reliably and portably know which changed path is the old or new, "half" renames may appear
+(only the original, only the new), "unknown" renames may appear (change was a rename, but
+whether it was the old or new isn't known), rename events might split across two debouncing
+boundaries, and so on.
+
+This option controls where that information is emitted. It defaults to 'none', which doesn't
+emit event information at all. The other options are 'environment' (deprecated), 'stdio',
+'file', 'json-stdio', and 'json-file'.
+
+The 'stdio' and 'file' modes are text-based: 'stdio' writes absolute paths to the stdin of
+the command, one per line, each prefixed with `create:`, `remove:`, `rename:`, `modify:`,
+or `other:`, then closes the handle; 'file' writes the same thing to a temporary file, and
+its path is given with the $WATCHEXEC_EVENTS_FILE environment variable.
+
+There are also two JSON modes, which are based on JSON objects and can represent the full
+set of events Watchexec handles. Here's an example of a folder being created on Linux:
+
+```json
+  {
+    "tags": [
+      {
+        "kind": "path",
+        "absolute": "/home/user/your/new-folder",
+        "filetype": "dir"
+      },
+      {
+        "kind": "fs",
+        "simple": "create",
+        "full": "Create(Folder)"
+      },
+      {
+        "kind": "source",
+        "source": "filesystem",
+      }
+    ],
+    "metadata": {
+      "notify-backend": "inotify"
+    }
+  }
+```
+
+The fields are as follows:
+
+  - `tags`, structured event data.
+  - `tags[].kind`, which can be:
+    * 'path', along with:
+      + `absolute`, an absolute path.
+      + `filetype`, a file type if known ('dir', 'file', 'symlink', 'other').
+    * 'fs':
+      + `simple`, the "simple" event type ('access', 'create', 'modify', 'remove', or 'other').
+      + `full`, the "full" event type, which is too complex to fully describe here, but looks like 'General(Precise(Specific))'.
+    * 'source', along with:
+      + `source`, the source of the event ('filesystem', 'keyboard', 'mouse', 'os', 'time', 'internal').
+    * 'keyboard', along with:
+      + `keycode`. Currently only the value 'eof' is supported.
+    * 'process', for events caused by processes:
+      + `pid`, the process ID.
+    * 'signal', for signals sent to Watchexec:
+      + `signal`, the normalised signal name ('hangup', 'interrupt', 'quit', 'terminate', 'user1', 'user2').
+    * 'completion', for when a command ends:
+      + `disposition`, the exit disposition ('success', 'error', 'signal', 'stop', 'exception', 'continued').
+      + `code`, the exit, signal, stop, or exception code.
+  - `metadata`, additional information about the event.
+
+The 'json-stdio' mode will emit JSON events to the standard input of the command, one per
+line, then close stdin. The 'json-file' mode will create a temporary file, write the
+events to it, and provide the path to the file with the $WATCHEXEC_EVENTS_FILE
+environment variable.
+
+Finally, the 'environment' mode was the default until 2.0. It sets environment variables
+with the paths of the affected files, for filesystem events:
+
+$WATCHEXEC_COMMON_PATH is set to the longest common path of all of the below variables,
+and so should be prepended to each path to obtain the full/real path. Then:
+
+  - $WATCHEXEC_CREATED_PATH is set when files/folders were created
+  - $WATCHEXEC_REMOVED_PATH is set when files/folders were removed
+  - $WATCHEXEC_RENAMED_PATH is set when files/folders were renamed
+  - $WATCHEXEC_WRITTEN_PATH is set when files/folders were modified
+  - $WATCHEXEC_META_CHANGED_PATH is set when files/folders' metadata were modified
+  - $WATCHEXEC_OTHERWISE_CHANGED_PATH is set for every other kind of pathed event
+
+Multiple paths are separated by the system path separator, ';' on Windows and ':' on unix.
+Within each variable, paths are deduplicated and sorted in binary order (i.e. neither
+Unicode nor locale aware).
+
+This is the legacy mode, is deprecated, and will be removed in the future. The environment
+is a very restricted space, while also limited in what it can usefully represent. Large
+numbers of files will either cause the environment to be truncated, or may error or crash
+the process entirely. The $WATCHEXEC_COMMON_PATH is also unintuitive, as demonstrated by the
+multiple confused queries that have landed in my inbox over the years.
+
+**Choices:**
+
+- `environment`
+- `stdio`
+- `file`
+- `json-stdio`
+- `json-file`
+- `none`
+
+#### `--only-emit-events`
+
+Only emit events to stdout, run no commands.
+
+This is a convenience option for using Watchexec as a file watcher, without running any commands. It is almost equivalent to using `cat` as the command, except that it will not spawn a new process for each event.
+
+This option requires `--emit-events-to` to be set, and restricts the available modes to `stdio` and `json-stdio`, modifying their behaviour to write to stdout instead of the stdin of the command.
+
+#### `-E --env... <KEY=VALUE>`
+
+Add env vars to the command
+
+This is a convenience option for setting environment variables for the command, without setting them for the Watchexec process itself.
+
+Use key=value syntax. Multiple variables can be set by repeating the option.
+
+#### `--wrap-process <MODE>`
+
+Configure how the process is wrapped
+
+By default, Watchexec will run the command in a process group in Unix, and in a Job Object in Windows.
+
+Some Unix programs prefer running in a session, while others do not work in a process group.
+
+Use 'group' to use a process group, 'session' to use a process session, and 'none' to run the command directly. On Windows, either of 'group' or 'session' will use a Job Object.
+
+**Choices:**
+
+- `group`
+- `session`
+- `none`
+
+#### `-N --notify`
+
+Alert when commands start and end
+
+With this, Watchexec will emit a desktop notification when a command starts and ends, on supported platforms. On unsupported platforms, it may silently do nothing, or log a warning.
+
+#### `--color <MODE>`
+
+When to use terminal colours
+
+Setting the environment variable `NO_COLOR` to any value is equivalent to `--color=never`.
+
+**Choices:**
+
+- `auto`
+- `always`
+- `never`
+
+#### `--timings`
+
+Print how long the command took to run
+
+This may not be exactly accurate, as it includes some overhead from Watchexec itself. Use the `time` utility, high-precision timers, or benchmarking tools for more accurate results.
+
+#### `-q --quiet`
+
+Don't print starting and stopping messages
+
+By default Watchexec will print a message when the command starts and stops. This option disables this behaviour, so only the command's output, warnings, and errors will be printed.
+
+#### `--bell`
+
+Ring the terminal bell on command completion
+
+#### `--project-origin <DIRECTORY>`
+
+Set the project origin
+
+Watchexec will attempt to discover the project's "origin" (or "root") by searching for a variety of markers, like files or directory patterns. It does its best but sometimes gets it it wrong, and you can override that with this option.
+
+The project origin is used to determine the path of certain ignore files, which VCS is being used, the meaning of a leading '/' in filtering patterns, and maybe more in the future.
+
+When set, Watchexec will also not bother searching, which can be significantly faster.
+
+#### `--workdir <DIRECTORY>`
+
+Set the working directory
+
+By default, the working directory of the command is the working directory of Watchexec. You can change that with this option. Note that paths may be less intuitive to use with this.
+
+#### `-e --exts... <EXTENSIONS>`
+
+Filename extensions to filter to
+
+This is a quick filter to only emit events for files with the given extensions. Extensions can be given with or without the leading dot (e.g. 'js' or '.js'). Multiple extensions can be given by repeating the option or by separating them with commas.
+
+#### `-f --filter... <PATTERN>`
+
+Filename patterns to filter to
+
+Provide a glob-like filter pattern, and only events for files matching the pattern will be emitted. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.
+
+#### `--filter-file... <PATH>`
+
+Files to load filters from
+
+Provide a path to a file containing filters, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--filter' option.
+
+This can also be used via the $WATCHEXEC_FILTER_FILES environment variable.
+
+#### `-J --filter-prog... <EXPRESSION>`
+
+[experimental] Filter programs.
+
+/!\ This option is EXPERIMENTAL and may change and/or vanish without notice.
+
+Provide your own custom filter programs in jaq (similar to jq) syntax. Programs are given an event in the same format as described in '--emit-events-to' and must return a boolean. Invalid programs will make watchexec fail to start; use '-v' to see program runtime errors.
+
+In addition to the jaq stdlib, watchexec adds some custom filter definitions:
+
+- 'path | file_meta' returns file metadata or null if the file does not exist.
+
+- 'path | file_size' returns the size of the file at path, or null if it does not exist.
+
+- 'path | file_read(bytes)' returns a string with the first n bytes of the file at path. If the file is smaller than n bytes, the whole file is returned. There is no filter to read the whole file at once to encourage limiting the amount of data read and processed.
+
+- 'string | hash', and 'path | file_hash' return the hash of the string or file at path. No guarantee is made about the algorithm used: treat it as an opaque value.
+
+- 'any | kv_store(key)', 'kv_fetch(key)', and 'kv_clear' provide a simple key-value store. Data is kept in memory only, there is no persistence. Consistency is not guaranteed.
+
+- 'any | printout', 'any | printerr', and 'any | log(level)' will print or log any given value to stdout, stderr, or the log (levels = error, warn, info, debug, trace), and pass the value through (so '[1] | log("debug") | .[]' will produce a '1' and log '[1]').
+
+All filtering done with such programs, and especially those using kv or filesystem access, is much slower than the other filtering methods. If filtering is too slow, events will back up and stall watchexec. Take care when designing your filters.
+
+If the argument to this option starts with an '@', the rest of the argument is taken to be the path to a file containing a jaq program.
+
+Jaq programs are run in order, after all other filters, and short-circuit: if a filter (jaq or not) rejects an event, execution stops there, and no other filters are run. Additionally, they stop after outputting the first value, so you'll want to use 'any' or 'all' when iterating, otherwise only the first item will be processed, which can be quite confusing!
+
+Find user-contributed programs or submit your own useful ones at <https://github.com/watchexec/watchexec/discussions/592>.
+
+## Examples:
+
+Regexp ignore filter on paths:
+
+'all(.tags[] | select(.kind == "path"); .absolute | test("[.]test[.]js$")) | not'
+
+Pass any event that creates a file:
+
+'any(.tags[] | select(.kind == "fs"); .simple == "create")'
+
+Pass events that touch executable files:
+
+'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | metadata | .executable)'
+
+Ignore files that start with shebangs:
+
+'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | read(2) == "#!") | not'
+
+#### `-i --ignore... <PATTERN>`
+
+Filename patterns to filter out
+
+Provide a glob-like filter pattern, and events for files matching the pattern will be excluded. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.
+
+#### `--ignore-file... <PATH>`
+
+Files to load ignores from
+
+Provide a path to a file containing ignores, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--ignore' option.
+
+This can also be used via the $WATCHEXEC_IGNORE_FILES environment variable.
+
+#### `--fs-events... <EVENTS>`
+
+Filesystem events to filter to
+
+This is a quick filter to only emit events for the given types of filesystem changes. Choose from 'access', 'create', 'remove', 'rename', 'modify', 'metadata'. Multiple types can be given by repeating the option or by separating them with commas. By default, this is all types except for 'access'.
+
+This may apply filtering at the kernel level when possible, which can be more efficient, but may be more confusing when reading the logs.
+
+**Choices:**
+
+- `access`
+- `create`
+- `remove`
+- `rename`
+- `modify`
+- `metadata`
+
+#### `--no-meta`
+
+Don't emit fs events for metadata changes
+
+This is a shorthand for '--fs-events create,remove,rename,modify'. Using it alongside the '--fs-events' option is non-sensical and not allowed.
+
+#### `--print-events`
+
+Print events that trigger actions
+
+This prints the events that triggered the action when handling it (after debouncing), in a human readable form. This is useful for debugging filters.
+
+Use '-vvv' instead when you need more diagnostic information.
+
+#### `--manual`
+
+Show the manual page
+
+This shows the manual page for Watchexec, if the output is a terminal and the 'man' program is available. If not, the manual page is printed to stdout in ROFF format (suitable for writing to a watchexec.1 file).
+
+Examples:
+
+    $ mise watch build
     Runs the "build" tasks. Will re-run the tasks when any of its sources change.
     Uses "sources" from the tasks definition to determine which files to watch.
 
-    $ mise watch -t build --glob src/**/*.rs
+    $ mise watch build --glob src/**/*.rs
     Runs the "build" tasks but specify the files to watch with a glob pattern.
     This overrides the "sources" from the tasks definition.
 
-    $ mise run -t build --clear
+    $ mise watch build --clear
     Extra arguments are passed to watchexec. See `watchexec --help` for details.
 
+    $ mise watch serve --watch src --exts rs --restart
+    Starts an api server, watching for changes to "*.rs" files in "./src" and kills/restarts the server when they change.
+
 ## `mise where`
 
 - **Usage**: `mise where <TOOL@VERSION>`
+- **Source code**: [`src/cli/where.rs`](https://github.com/jdx/mise/blob/main/src/cli/where.rs)
 
 Display the installation path for a tool
 
@@ -2595,7 +3959,8 @@ Examples:
 
 ## `mise which`
 
-- **Usage**: `mise which [FLAGS] <BIN_NAME>`
+- **Usage**: `mise which [FLAGS] [BIN_NAME]`
+- **Source code**: [`src/cli/which.rs`](https://github.com/jdx/mise/blob/main/src/cli/which.rs)
 
 Shows the path that a tool's bin points to.
 
@@ -2603,7 +3968,7 @@ Use this to figure out what version of a tool is currently active.
 
 ### Arguments
 
-#### `<BIN_NAME>`
+#### `[BIN_NAME]`
 
 The bin to look up
 
@@ -2636,11 +4001,13 @@ Examples:
 ## `mise render-help`
 
 - **Usage**: `mise render-help`
+- **Source code**: [`src/cli/render_help.rs`](https://github.com/jdx/mise/blob/main/src/cli/render_help.rs)
 
 internal command to generate markdown from help
 
 ## `mise render-mangen`
 
 - **Usage**: `mise render-mangen`
+- **Source code**: [`src/cli/render_mangen.rs`](https://github.com/jdx/mise/blob/main/src/cli/render_mangen.rs)
 
 internal command to generate markdown from help
diff --git a/examples/mise.usage.kdl b/examples/mise.usage.kdl
index ed97c5aa..a410862b 100644
--- a/examples/mise.usage.kdl
+++ b/examples/mise.usage.kdl
@@ -1,1515 +1,1180 @@
-name "mise"
-bin "mise"
+min_usage_version "1.3"
+name mise
+bin mise
 about "The front-end to your dev env"
-long_about r"mise is a tool for managing runtime versions. https://github.com/jdx/mise
-
-It's a replacement for tools like nvm, nodenv, rbenv, rvm, chruby, pyenv, etc.
-that works for any language. It's also great for managing linters/tools like
-jq and shellcheck.
-
-It is inspired by asdf and uses asdf's plugin ecosystem under the hood:
-https://asdf-vm.com/"
-usage "Usage: mise [OPTIONS] <COMMAND>"
-flag "-C --cd" help="Change directory before running command" global=true {
-    arg "<DIR>"
-}
-flag "-P --profile" help="Set the profile (environment)" global=true {
-    arg "<PROFILE>"
-}
-flag "--debug" help="Sets log level to debug" hide=true global=true
-flag "--log-level" help="Set the log output verbosity" hide=true global=true {
-    arg "<LEVEL>" {
-        choices "error" "warn" "info" "debug" "trace"
-    }
-}
-flag "-q --quiet" help="Suppress non-error messages" global=true
-flag "--trace" help="Sets log level to trace" hide=true global=true
-flag "-v --verbose" help="Show extra output (use -vv for even more)" var=true global=true count=true
-flag "-y --yes" help="Answer yes to all confirmation prompts" global=true
-cmd "activate" help="Initializes mise in the current shell session" {
-    long_help r#"Initializes mise in the current shell session
-
-This should go into your shell's rc file.
-Otherwise, it will only take effect in the current session.
-(e.g. ~/.zshrc, ~/.bashrc)
-
-This is only intended to be used in interactive sessions, not scripts.
-mise is only capable of updating PATH when the prompt is displayed to the user.
-For non-interactive use-cases, use shims instead.
-
-Typically this can be added with something like the following:
-
-    echo 'eval "$(mise activate)"' >> ~/.zshrc
-
-However, this requires that "mise" is in your PATH. If it is not, you need to
-specify the full path like this:
-
-    echo 'eval "$(/path/to/mise activate)"' >> ~/.zshrc
-
-Customize status output with `status` settings."#
-    after_long_help r#"Examples:
-
-    $ eval "$(mise activate bash)"
-    $ eval "$(mise activate zsh)"
-    $ mise activate fish | source
-    $ execx($(mise activate xonsh))
-"#
-    flag "-s --shell" help="Shell type to generate the script for" hide=true {
-        arg "<SHELL>" {
-            choices "bash" "fish" "nu" "xonsh" "zsh"
+long_about "\nmise is a tool for managing runtime versions. https://github.com/jdx/mise\n\nIt's a replacement for tools like nvm, nodenv, rbenv, rvm, chruby, pyenv, etc.\nthat works for any language. It's also great for managing linters/tools like\njq and shellcheck.\n\nIt is inspired by asdf and uses asdf's plugin ecosystem under the hood:\nhttps://asdf-vm.com/"
+usage "Usage: mise [OPTIONS] [TASK] [COMMAND]"
+flag "-C --cd" help="Change directory before running command" global=#true {
+    arg <DIR>
+}
+flag "-c --continue-on-error" help="Continue running tasks even if one fails" hide=#true
+flag "-n --dry-run" help="Dry run, don't actually do anything" hide=#true
+flag "-E --env" help="Set the environment for loading `mise.<ENV>.toml`" var=#true global=#true {
+    arg <ENV>
+}
+flag "-f --force" help="Force the operation" hide=#true
+flag "-i --interleave" help="Set the log output verbosity" hide=#true
+flag "-j --jobs" help="How many jobs to run in parallel [default: 8]" global=#true {
+    arg <JOBS>
+}
+flag "-p --prefix" hide=#true
+flag --output {
+    arg <OUTPUT>
+}
+flag "-P --profile" help="Set the profile (environment)" var=#true hide=#true global=#true {
+    arg <PROFILE>
+}
+flag "-s --shell" hide=#true {
+    arg <SHELL>
+}
+flag "-t --tool" help="Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10" var=#true hide=#true {
+    arg <TOOL@VERSION>
+}
+flag --raw help="Read/write directly to stdin/stdout/stderr instead of by line" global=#true
+flag --timings help="Shows elapsed time after each task completes" hide=#true {
+    long_help "Shows elapsed time after each task completes\n\nDefault to always show with `MISE_TASK_TIMINGS=1`"
+}
+flag --no-config help="Do not load any config files" {
+    long_help "Do not load any config files\n\nCan also use `MISE_NO_CONFIG=1`"
+}
+flag --no-timings help="Hides elapsed time after each task completes" hide=#true {
+    long_help "Hides elapsed time after each task completes\n\nDefault to always hide with `MISE_TASK_TIMINGS=0`"
+}
+flag "-V --version" hide=#true
+flag "-y --yes" help="Answer yes to all confirmation prompts" global=#true
+flag --debug help="Sets log level to debug" hide=#true global=#true
+flag --log-level hide=#true global=#true {
+    arg <LEVEL> {
+        choices trace debug info warning error
+    }
+}
+flag "-q --quiet" help="Suppress non-error messages" global=#true
+flag --silent help="Suppress all task output and mise non-error messages" global=#true
+flag --trace help="Sets log level to trace" hide=#true global=#true
+flag "-v --verbose" help="Show extra output (use -vv for even more)" var=#true global=#true count=#true
+arg "[TASK]" help="Task to run" help_long="Task to run.\n\nShorthand for `mise task run <TASK>`." required=#false
+arg "[TASK_ARGS]..." help="Task arguments" required=#false var=#true hide=#true
+arg "[-- TASK_ARGS_LAST]..." required=#false var=#true hide=#true
+cmd activate help="Initializes mise in the current shell session" {
+    long_help "Initializes mise in the current shell session\n\nThis should go into your shell's rc file or login shell.\nOtherwise, it will only take effect in the current session.\n(e.g. ~/.zshrc, ~/.zprofile, ~/.zshenv, ~/.bashrc, ~/.bash_profile, ~/.profile, ~/.config/fish/config.fish)\n\nTypically, this can be added with something like the following:\n\n    echo 'eval \"$(mise activate zsh)\"' >> ~/.zshrc\n\nHowever, this requires that \"mise\" is in your PATH. If it is not, you need to\nspecify the full path like this:\n\n    echo 'eval \"$(/path/to/mise activate zsh)\"' >> ~/.zshrc\n\nCustomize status output with `status` settings."
+    after_long_help "Examples:\n\n    $ eval \"$(mise activate bash)\"\n    $ eval \"$(mise activate zsh)\"\n    $ mise activate fish | source\n    $ execx($(mise activate xonsh))\n"
+    flag "-s --shell" help="Shell type to generate the script for" hide=#true {
+        arg <SHELL> {
+            choices bash elvish fish nu xonsh zsh pwsh
         }
     }
-    flag "--status" help="Show \"mise: <PLUGIN>@<VERSION>\" message when changing directories" hide=true
-    flag "--shims" help="Use shims instead of modifying PATH\nEffectively the same as:" {
-        long_help "Use shims instead of modifying PATH\nEffectively the same as:\n\n    PATH=\"$HOME/.local/share/mise/shims:$PATH\""
+    flag --status help="Show \"mise: <PLUGIN>@<VERSION>\" message when changing directories" hide=#true
+    flag --shims help="Use shims instead of modifying PATH\nEffectively the same as:" {
+        long_help "Use shims instead of modifying PATH\nEffectively the same as:\n\n    PATH=\"$HOME/.local/share/mise/shims:$PATH\"\n\n`mise activate --shims` does not support all the features of `mise activate`.\nSee https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path for more information"
     }
     flag "-q --quiet" help="Suppress non-error messages"
-    arg "[SHELL_TYPE]" help="Shell type to generate the script for" {
-        choices "bash" "fish" "nu" "xonsh" "zsh"
+    flag --no-hook-env help="Do not automatically call hook-env" {
+        long_help "Do not automatically call hook-env\n\nThis can be helpful for debugging mise. If you run `eval \"$(mise activate --no-hook-env)\"`, then you can call `mise hook-env` manually which will output the env vars to stdout without actually modifying the environment. That way you can do things like `mise hook-env --trace` to get more information or just see the values that hook-env is outputting."
+    }
+    arg "[SHELL_TYPE]" help="Shell type to generate the script for" required=#false {
+        choices bash elvish fish nu xonsh zsh pwsh
     }
 }
-cmd "alias" help="Manage aliases" {
-    alias "a"
-    alias "aliases" hide=true
+cmd alias help="Manage aliases" {
+    alias a
+    alias aliases hide=#true
     flag "-p --plugin" help="filter aliases by plugin" {
-        arg "<PLUGIN>"
+        arg <PLUGIN>
+    }
+    flag --no-header help="Don't show table header"
+    cmd get help="Show an alias for a plugin" {
+        long_help "Show an alias for a plugin\n\nThis is the contents of an alias.<PLUGIN> entry in ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise alias get node lts-hydrogen\n    20.0.0\n"
+        arg <PLUGIN> help="The plugin to show the alias for"
+        arg <ALIAS> help="The alias to show"
+    }
+    cmd ls help="List aliases\nShows the aliases that can be specified.\nThese can come from user config or from plugins in `bin/list-aliases`." {
+        alias list
+        long_help "List aliases\nShows the aliases that can be specified.\nThese can come from user config or from plugins in `bin/list-aliases`.\n\nFor user config, aliases are defined like the following in `~/.config/mise/config.toml`:\n\n    [alias.node.versions]\n    lts = \"22.0.0\""
+        after_long_help "Examples:\n\n    $ mise aliases\n    node  lts-jod      22\n"
+        flag --no-header help="Don't show table header"
+        arg "[TOOL]" help="Show aliases for <TOOL>" required=#false
+    }
+    cmd set help="Add/update an alias for a plugin" {
+        alias add create
+        long_help "Add/update an alias for a plugin\n\nThis modifies the contents of ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise alias set node lts-jod 22.0.0\n"
+        arg <PLUGIN> help="The plugin to set the alias for"
+        arg <ALIAS> help="The alias to set"
+        arg <VALUE> help="The value to set the alias to"
+    }
+    cmd unset help="Clears an alias for a plugin" {
+        alias rm remove delete del
+        long_help "Clears an alias for a plugin\n\nThis modifies the contents of ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise alias unset node lts-jod\n"
+        arg <PLUGIN> help="The plugin to remove the alias from"
+        arg <ALIAS> help="The alias to remove"
     }
-    flag "--no-header" help="Don't show table header"
-    cmd "get" help="Show an alias for a plugin" {
-        long_help r"Show an alias for a plugin
-
-This is the contents of an alias.<PLUGIN> entry in ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-   $ mise alias get node lts-hydrogen
-   20.0.0
-"
-        arg "<PLUGIN>" help="The plugin to show the alias for"
-        arg "<ALIAS>" help="The alias to show"
-    }
-    cmd "ls" help="List aliases\nShows the aliases that can be specified.\nThese can come from user config or from plugins in `bin/list-aliases`." {
-        alias "list"
-        long_help r#"List aliases
-Shows the aliases that can be specified.
-These can come from user config or from plugins in `bin/list-aliases`.
-
-For user config, aliases are defined like the following in `~/.config/mise/config.toml`:
-
-    [alias.node]
-    lts = "20.0.0""#
-        after_long_help r"Examples:
-
-    $ mise aliases
-    node    lts-hydrogen   20.0.0
-"
-        flag "--no-header" help="Don't show table header"
-        arg "[PLUGIN]" help="Show aliases for <PLUGIN>"
-    }
-    cmd "set" help="Add/update an alias for a plugin" {
-        alias "add" "create"
-        long_help r"Add/update an alias for a plugin
-
-This modifies the contents of ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    $ mise alias set node lts-hydrogen 18.0.0
-"
-        arg "<PLUGIN>" help="The plugin to set the alias for"
-        arg "<ALIAS>" help="The alias to set"
-        arg "<VALUE>" help="The value to set the alias to"
-    }
-    cmd "unset" help="Clears an alias for a plugin" {
-        alias "rm" "remove" "delete" "del"
-        long_help r"Clears an alias for a plugin
-
-This modifies the contents of ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    $ mise alias unset node lts-hydrogen
-"
-        arg "<PLUGIN>" help="The plugin to remove the alias from"
-        arg "<ALIAS>" help="The alias to remove"
+}
+cmd asdf hide=#true help="[internal] simulates asdf for plugins that call \"asdf\" internally" {
+    arg "[ARGS]..." help="all arguments" required=#false double_dash=automatic var=#true
+}
+cmd backends help="Manage backends" {
+    alias b
+    alias backend backend-list hide=#true
+    cmd ls help="List built-in backends" {
+        alias list
+        after_long_help "Examples:\n\n    $ mise backends ls\n    aqua\n    asdf\n    cargo\n    core\n    dotnet\n    gem\n    go\n    npm\n    pipx\n    spm\n    ubi\n    vfox\n"
     }
 }
-cmd "asdf" hide=true help="[internal] simulates asdf for plugins that call \"asdf\" internally" {
-    arg "[ARGS]..." help="all arguments" var=true
+cmd bin-paths help="List all the active runtime bin paths" {
+    arg "[TOOL@VERSION]..." help="Tool(s) to look up\ne.g.: ruby@3" required=#false var=#true
 }
-cmd "backends" help="Manage backends" {
-    alias "b"
-    alias "backend" "backend-list" hide=true
-    cmd "ls" help="List built-in backends" {
-        alias "list"
-        after_long_help r"Examples:
-
-    $ mise backends ls
-    cargo
-    go
-    npm
-    pipx
-    spm
-    ubi
-"
-    }
-}
-cmd "bin-paths" help="List all the active runtime bin paths"
-cmd "cache" help="Manage the mise cache" {
-    long_help r"Manage the mise cache
-
-Run `mise cache` with no args to view the current cache directory."
-    cmd "clear" help="Deletes all cache files in mise" {
-        alias "c"
-        alias "clean" hide=true
-        arg "[PLUGIN]..." help="Plugin(s) to clear cache for e.g.: node, python" var=true
-    }
-    cmd "prune" help="Removes stale mise cache files" {
-        alias "p"
-        long_help r"Removes stale mise cache files
-
-By default, this command will remove files that have not been accessed in 30 days.
-Change this with the MISE_CACHE_PRUNE_AGE environment variable."
-        flag "--dry-run" help="Just show what would be pruned"
-        flag "-v --verbose" help="Show pruned files" var=true count=true
-        arg "[PLUGIN]..." help="Plugin(s) to clear cache for e.g.: node, python" var=true
+cmd cache help="Manage the mise cache" {
+    long_help "Manage the mise cache\n\nRun `mise cache` with no args to view the current cache directory."
+    cmd clear help="Deletes all cache files in mise" {
+        alias c
+        alias clean hide=#true
+        flag --outdate help="Mark all cache files as old" hide=#true
+        arg "[PLUGIN]..." help="Plugin(s) to clear cache for e.g.: node, python" required=#false var=#true
+    }
+    cmd prune help="Removes stale mise cache files" {
+        alias p
+        long_help "Removes stale mise cache files\n\nBy default, this command will remove files that have not been accessed in 30 days.\nChange this with the MISE_CACHE_PRUNE_AGE environment variable."
+        flag --dry-run help="Just show what would be pruned"
+        flag "-v --verbose" help="Show pruned files" var=#true count=#true
+        arg "[PLUGIN]..." help="Plugin(s) to clear cache for e.g.: node, python" required=#false var=#true
     }
 }
-cmd "completion" help="Generate shell completions" {
-    alias "complete" "completions" hide=true
-    after_long_help r"Examples:
-
-    $ mise completion bash > /etc/bash_completion.d/mise
-    $ mise completion zsh  > /usr/local/share/zsh/site-functions/_mise
-    $ mise completion fish > ~/.config/fish/completions/mise.fish
-"
-    flag "-s --shell" help="Shell type to generate completions for" hide=true {
-        arg "<SHELL_TYPE>" {
-            choices "bash" "fish" "zsh"
+cmd completion help="Generate shell completions" {
+    alias complete completions hide=#true
+    after_long_help "Examples:\n\n    $ mise completion bash > /etc/bash_completion.d/mise\n    $ mise completion zsh  > /usr/local/share/zsh/site-functions/_mise\n    $ mise completion fish > ~/.config/fish/completions/mise.fish\n"
+    flag "-s --shell" help="Shell type to generate completions for" hide=#true {
+        arg <SHELL_TYPE> {
+            choices bash fish zsh
         }
     }
-    flag "--usage" help="Always use usage for completions.\nCurrently, usage is the default for fish and bash but not zsh since it has a few quirks\nto work out first." hide=true {
+    flag --usage help="Always use usage for completions.\nCurrently, usage is the default for fish and bash but not zsh since it has a few quirks\nto work out first." hide=#true {
         long_help "Always use usage for completions.\nCurrently, usage is the default for fish and bash but not zsh since it has a few quirks\nto work out first.\n\nThis requires the `usage` CLI to be installed.\nhttps://usage.jdx.dev"
     }
-    arg "[SHELL]" help="Shell type to generate completions for" {
-        choices "bash" "fish" "zsh"
+    flag --include-bash-completion-lib help="Include the bash completion library in the bash completion script" {
+        long_help "Include the bash completion library in the bash completion script\n\nThis is required for completions to work in bash, but it is not included by default\nyou may source it separately or enable this flag to include it in the script."
+    }
+    arg "[SHELL]" help="Shell type to generate completions for" required=#false {
+        choices bash fish zsh
     }
 }
-cmd "config" help="Manage config files" {
-    alias "cfg"
-    alias "toml" hide=true
-    flag "--no-header" help="Do not print table header"
+cmd config help="Manage config files" {
+    alias cfg
+    alias toml hide=#true
+    flag --no-header help="Do not print table header"
     flag "-J --json" help="Output in JSON format"
-    cmd "generate" help="[experimental] Generate a mise.toml file" {
-        alias "g"
-        after_long_help r"Examples:
-
-    $ mise cf generate > mise.toml
-    $ mise cf generate --output=mise.toml
-"
+    cmd generate help="[experimental] Generate a mise.toml file" {
+        alias g
+        after_long_help "Examples:\n\n    $ mise cf generate > mise.toml\n    $ mise cf generate --output=mise.toml\n"
+        flag "-t --tool-versions" help="Path to a .tool-versions file to import tools from" {
+            arg <TOOL_VERSIONS>
+        }
         flag "-o --output" help="Output to file instead of stdout" {
-            arg "<OUTPUT>"
+            arg <OUTPUT>
         }
     }
-    cmd "get" help="Display the value of a setting in a mise.toml file" {
-        after_long_help r"Examples:
-
-    $ mise toml get tools.python
-    3.12
-"
+    cmd get help="Display the value of a setting in a mise.toml file" {
+        after_long_help "Examples:\n\n    $ mise toml get tools.python\n    3.12\n"
         flag "-f --file" help="The path to the mise.toml file to edit" {
             long_help "The path to the mise.toml file to edit\n\nIf not provided, the nearest mise.toml file will be used"
-            arg "<FILE>"
+            arg <FILE>
         }
-        arg "[KEY]" help="The path of the config to display"
+        arg "[KEY]" help="The path of the config to display" required=#false
     }
-    cmd "ls" help="List config files currently in use" {
-        after_long_help r"Examples:
-
-    $ mise config ls
-"
-        flag "--no-header" help="Do not print table header"
+    cmd ls help="List config files currently in use" {
+        alias list
+        after_long_help "Examples:\n\n    $ mise config ls\n    Path                        Tools\n    ~/.config/mise/config.toml  pitchfork\n    ~/src/mise/mise.toml        actionlint, bun, cargo-binstall, cargo:cargo-edit, cargo:cargo-insta\n"
+        flag --no-header help="Do not print table header"
         flag "-J --json" help="Output in JSON format"
     }
-    cmd "set" help="Display the value of a setting in a mise.toml file" {
-        after_long_help r"Examples:
-
-    $ mise config set tools.python 3.12
-    $ mise config set settings.always_keep_download true
-    $ mise config set env.TEST_ENV_VAR ABC
-"
+    cmd set help="Set the value of a setting in a mise.toml file" {
+        after_long_help "Examples:\n\n    $ mise config set tools.python 3.12\n    $ mise config set settings.always_keep_download true\n    $ mise config set env.TEST_ENV_VAR ABC\n    $ mise config set settings.disable_tools --type list node,rust\n\n    # Type for `settings` is inferred\n    $ mise config set settings.jobs 4\n"
         flag "-f --file" help="The path to the mise.toml file to edit" {
             long_help "The path to the mise.toml file to edit\n\nIf not provided, the nearest mise.toml file will be used"
-            arg "<FILE>"
+            arg <FILE>
         }
         flag "-t --type" {
-            arg "<TYPE>" {
-                choices "string" "integer" "float" "bool"
+            arg <TYPE> {
+                choices infer string integer float bool list
             }
         }
-        arg "<KEY>" help="The path of the config to display"
-        arg "<VALUE>" help="The value to set the key to"
+        arg <KEY> help="The path of the config to display"
+        arg <VALUE> help="The value to set the key to"
     }
 }
-cmd "current" help="Shows current active and installed runtime versions" {
-    long_help r"Shows current active and installed runtime versions
-
-This is similar to `mise ls --current`, but this only shows the runtime
-and/or version. It's designed to fit into scripts more easily."
-    after_long_help r"Examples:
-    
-    # outputs `.tool-versions` compatible format
-    $ mise current
-    python 3.11.0 3.10.0
-    shfmt 3.6.0
-    shellcheck 0.9.0
-    node 20.0.0
-
-    $ mise current node
-    20.0.0
-
-    # can output multiple versions
-    $ mise current python
-    3.11.0 3.10.0
-"
-    arg "[PLUGIN]" help="Plugin to show versions of e.g.: ruby, node, cargo:eza, npm:prettier, etc"
-}
-cmd "deactivate" help="Disable mise for current shell session" {
-    long_help r"Disable mise for current shell session
-
-This can be used to temporarily disable mise in a shell session."
-    after_long_help r"Examples:
-
-    $ mise deactivate
-"
+cmd current hide=#true help="Shows current active and installed runtime versions" {
+    long_help "Shows current active and installed runtime versions\n\nThis is similar to `mise ls --current`, but this only shows the runtime\nand/or version. It's designed to fit into scripts more easily."
+    after_long_help "Examples:\n\n    # outputs `.tool-versions` compatible format\n    $ mise current\n    python 3.11.0 3.10.0\n    shfmt 3.6.0\n    shellcheck 0.9.0\n    node 20.0.0\n\n    $ mise current node\n    20.0.0\n\n    # can output multiple versions\n    $ mise current python\n    3.11.0 3.10.0\n"
+    arg "[PLUGIN]" help="Plugin to show versions of e.g.: ruby, node, cargo:eza, npm:prettier, etc" required=#false
 }
-cmd "direnv" help="Output direnv function to use mise inside direnv" {
-    long_help r"Output direnv function to use mise inside direnv
-
-See https://mise.jdx.dev/direnv.html for more information
-
-Because this generates the legacy files based on currently installed plugins,
-you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change."
-    cmd "envrc" hide=true help="[internal] This is an internal command that writes an envrc file\nfor direnv to consume."
-    cmd "exec" hide=true help="[internal] This is an internal command that writes an envrc file\nfor direnv to consume."
-    cmd "activate" help="Output direnv function to use mise inside direnv" {
-        long_help r"Output direnv function to use mise inside direnv
-
-See https://mise.jdx.dev/direnv.html for more information
-
-Because this generates the legacy files based on currently installed plugins,
-you should run this command after installing new plugins. Otherwise
-direnv may not know to update environment variables when legacy file versions change."
-        after_long_help r"Examples:
-
-    $ mise direnv activate > ~/.config/direnv/lib/use_mise.sh
-    $ echo 'use mise' > .envrc
-    $ direnv allow
-"
+cmd deactivate help="Disable mise for current shell session" {
+    long_help "Disable mise for current shell session\n\nThis can be used to temporarily disable mise in a shell session."
+    after_long_help "Examples:\n\n    $ mise deactivate\n"
+}
+cmd direnv hide=#true help="Output direnv function to use mise inside direnv" {
+    long_help "Output direnv function to use mise inside direnv\n\nSee https://mise.jdx.dev/direnv.html for more information\n\nBecause this generates the idiomatic files based on currently installed plugins,\nyou should run this command after installing new plugins. Otherwise\ndirenv may not know to update environment variables when idiomatic file versions change."
+    cmd envrc hide=#true help="[internal] This is an internal command that writes an envrc file\nfor direnv to consume."
+    cmd exec hide=#true help="[internal] This is an internal command that writes an envrc file\nfor direnv to consume."
+    cmd activate hide=#true help="Output direnv function to use mise inside direnv" {
+        long_help "Output direnv function to use mise inside direnv\n\nSee https://mise.jdx.dev/direnv.html for more information\n\nBecause this generates the idiomatic files based on currently installed plugins,\nyou should run this command after installing new plugins. Otherwise\ndirenv may not know to update environment variables when idiomatic file versions change."
+        after_long_help "Examples:\n\n    $ mise direnv activate > ~/.config/direnv/lib/use_mise.sh\n    $ echo 'use mise' > .envrc\n    $ direnv allow\n"
     }
 }
-cmd "doctor" help="Check mise installation for possible problems" {
-    alias "dr"
-    after_long_help r"Examples:
-
-    $ mise doctor
-    [WARN] plugin node is not installed
-"
+cmd doctor help="Check mise installation for possible problems" {
+    alias dr
+    after_long_help "Examples:\n\n    $ mise doctor\n    [WARN] plugin node is not installed\n"
+    flag "-J --json"
+    cmd path help="Print the current PATH entries mise is providing" {
+        alias paths hide=#true
+        after_long_help "Examples:\n\n    Get the current PATH entries mise is providing\n    $ mise path\n    /home/user/.local/share/mise/installs/node/24.0.0/bin\n    /home/user/.local/share/mise/installs/rust/1.90.0/bin\n    /home/user/.local/share/mise/installs/python/3.10.0/bin\n"
+        flag "-f --full" help="Print all entries including those not provided by mise"
+    }
 }
-cmd "env" help="Exports env vars to activate mise a single time" {
-    alias "e"
-    long_help r"Exports env vars to activate mise a single time
-
-Use this if you don't want to permanently install mise. It's not necessary to
-use this if you have `mise activate` in your shell rc file."
-    after_long_help r#"Examples:
-
-    $ eval "$(mise env -s bash)"
-    $ eval "$(mise env -s zsh)"
-    $ mise env -s fish | source
-    $ execx($(mise env -s xonsh))
-"#
+cmd en help="[experimental] starts a new shell with the mise environment built from the current configuration" {
+    long_help "[experimental] starts a new shell with the mise environment built from the current configuration\n\nThis is an alternative to `mise activate` that allows you to explicitly start a mise session.\nIt will have the tools and environment variables in the configs loaded.\nNote that changing directories will not update the mise environment."
+    after_long_help "Examples:\n\n    $ mise en .\n    $ node -v\n    v20.0.0\n\n    Skip loading bashrc:\n    $ mise en -s \"bash --norc\"\n\n    Skip loading zshrc:\n    $ mise en -s \"zsh -f\"\n"
+    flag "-s --shell" help="Shell to start" {
+        long_help "Shell to start\n\nDefaults to $SHELL"
+        arg <SHELL>
+    }
+    arg "[DIR]" help="Directory to start the shell in" required=#false default=.
+}
+cmd env help="Exports env vars to activate mise a single time" {
+    alias e
+    long_help "Exports env vars to activate mise a single time\n\nUse this if you don't want to permanently install mise. It's not necessary to\nuse this if you have `mise activate` in your shell rc file."
+    after_long_help "Examples:\n\n    $ eval \"$(mise env -s bash)\"\n    $ eval \"$(mise env -s zsh)\"\n    $ mise env -s fish | source\n    $ execx($(mise env -s xonsh))\n"
     flag "-J --json" help="Output in JSON format"
+    flag --json-extended help="Output in JSON format with additional information (source, tool)"
+    flag "-D --dotenv" help="Output in dotenv format"
     flag "-s --shell" help="Shell type to generate environment variables for" {
-        arg "<SHELL>" {
-            choices "bash" "fish" "nu" "xonsh" "zsh"
+        arg <SHELL> {
+            choices bash elvish fish nu xonsh zsh pwsh
         }
     }
-    arg "[TOOL@VERSION]..." help="Tool(s) to use" var=true
+    arg "[TOOL@VERSION]..." help="Tool(s) to use" required=#false var=#true
 }
-cmd "exec" help="Execute a command with tool(s) set" {
-    alias "x"
-    long_help r#"Execute a command with tool(s) set
-
-use this to avoid modifying the shell session or running ad-hoc commands with mise tools set.
-
-Tools will be loaded from mise.toml, though they can be overridden with <RUNTIME> args
-Note that only the plugin specified will be overridden, so if a `mise.toml` file
-includes "node 20" but you run `mise exec python@3.11`; it will still load node@20.
-
-The "--" separates runtimes from the commands to pass along to the subprocess."#
-    after_long_help r#"Examples:
-
-    $ mise exec node@20 -- node ./app.js  # launch app.js using node-20.x
-    $ mise x node@20 -- node ./app.js     # shorter alias
-
-    # Specify command as a string:
-    $ mise exec node@20 python@3.11 --command "node -v && python -V"
-
-    # Run a command in a different directory:
-    $ mise x -C /path/to/project node@20 -- node ./app.js
-"#
+cmd exec help="Execute a command with tool(s) set" {
+    alias x
+    long_help "Execute a command with tool(s) set\n\nuse this to avoid modifying the shell session or running ad-hoc commands with mise tools set.\n\nTools will be loaded from mise.toml, though they can be overridden with <RUNTIME> args\nNote that only the plugin specified will be overridden, so if a `mise.toml` file\nincludes \"node 20\" but you run `mise exec python@3.11`; it will still load node@20.\n\nThe \"--\" separates runtimes from the commands to pass along to the subprocess."
+    after_long_help "Examples:\n\n    $ mise exec node@20 -- node ./app.js  # launch app.js using node-20.x\n    $ mise x node@20 -- node ./app.js     # shorter alias\n\n    # Specify command as a string:\n    $ mise exec node@20 python@3.11 --command \"node -v && python -V\"\n\n    # Run a command in a different directory:\n    $ mise x -C /path/to/project node@20 -- node ./app.js\n"
     flag "-c --command" help="Command string to execute" {
-        arg "<C>"
+        arg <C>
     }
     flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
-    flag "--raw" help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
-    arg "[TOOL@VERSION]..." help="Tool(s) to start e.g.: node@20 python@3.10" var=true
-    arg "[COMMAND]..." help="Command string to execute (same as --command)" var=true
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
+    arg "[TOOL@VERSION]..." help="Tool(s) to start e.g.: node@20 python@3.10" required=#false var=#true
+    arg "[-- COMMAND]..." help="Command string to execute (same as --command)" required=#false var=#true
 }
-cmd "generate" subcommand_required=true help="[experimental] Generate files for various tools/services" {
-    alias "g"
-    cmd "git-pre-commit" help="[experimental] Generate a git pre-commit hook" {
-        alias "pre-commit"
-        long_help r"[experimental] Generate a git pre-commit hook
-
-This command generates a git pre-commit hook that runs a mise task like `mise run pre-commit`
-when you commit changes to your repository."
-        after_long_help r#"Examples:
-
-    $ mise generate git-pre-commit --write --task=pre-commit
-    $ git commit -m "feat: add new feature" # runs `mise run pre-commit`
-"#
-        flag "--hook" help="Which hook to generate (saves to .git/hooks/$hook)" {
-            arg "<HOOK>"
+cmd fmt help="Formats mise.toml" {
+    long_help "Formats mise.toml\n\nSorts keys and cleans up whitespace in mise.toml"
+    after_long_help "Examples:\n\n    $ mise fmt\n"
+    flag "-a --all" help="Format all files from the current directory"
+}
+cmd generate subcommand_required=#true help="[experimental] Generate files for various tools/services" {
+    alias gen
+    alias g hide=#true
+    cmd bootstrap help="[experimental] Generate a script to download+execute mise" {
+        long_help "[experimental] Generate a script to download+execute mise\n\nThis is designed to be used in a project where contributors may not have mise installed."
+        after_long_help "Examples:\n\n    $ mise generate bootstrap >./bin/mise\n    $ chmod +x ./bin/mise\n    $ ./bin/mise install – automatically downloads mise to .mise if not already installed\n"
+        flag "-l --localize" help="Sandboxes mise internal directories like MISE_DATA_DIR and MISE_CACHE_DIR into a `.mise` directory in the project" {
+            long_help "Sandboxes mise internal directories like MISE_DATA_DIR and MISE_CACHE_DIR into a `.mise` directory in the project\n\nThis is necessary if users may use a different version of mise outside the project."
+        }
+        flag --localized-dir help="Directory to put localized data into" {
+            arg <LOCALIZED_DIR>
+        }
+        flag "-V --version" help="Specify mise version to fetch" {
+            arg <VERSION>
+        }
+        flag "-w --write" help="instead of outputting the script to stdout, write to a file and make it executable" {
+            arg <WRITE>
+        }
+    }
+    cmd config help="[experimental] Generate a mise.toml file" {
+        alias g
+        after_long_help "Examples:\n\n    $ mise cf generate > mise.toml\n    $ mise cf generate --output=mise.toml\n"
+        flag "-t --tool-versions" help="Path to a .tool-versions file to import tools from" {
+            arg <TOOL_VERSIONS>
+        }
+        flag "-o --output" help="Output to file instead of stdout" {
+            arg <OUTPUT>
+        }
+    }
+    cmd git-pre-commit help="[experimental] Generate a git pre-commit hook" {
+        alias pre-commit
+        long_help "[experimental] Generate a git pre-commit hook\n\nThis command generates a git pre-commit hook that runs a mise task like `mise run pre-commit`\nwhen you commit changes to your repository.\n\nStaged files are passed to the task as `STAGED`."
+        after_long_help "Examples:\n\n    $ mise generate git-pre-commit --write --task=pre-commit\n    $ git commit -m \"feat: add new feature\" # runs `mise run pre-commit`\n"
+        flag --hook help="Which hook to generate (saves to .git/hooks/$hook)" {
+            arg <HOOK>
         }
         flag "-t --task" help="The task to run when the pre-commit hook is triggered" {
-            arg "<TASK>"
+            arg <TASK>
         }
         flag "-w --write" help="write to .git/hooks/pre-commit and make it executable"
     }
-    cmd "github-action" help="[experimental] Generate a GitHub Action workflow file" {
-        long_help r"[experimental] Generate a GitHub Action workflow file
-
-This command generates a GitHub Action workflow file that runs a mise task like `mise run ci`
-when you push changes to your repository."
-        after_long_help r#"Examples:
-
-    $ mise generate github-action --write --task=ci
-    $ git commit -m "feat: add new feature"
-    $ git push # runs `mise run ci` on GitHub
-"#
-        flag "-n --name" help="the name of the workflow to generate" {
-            arg "<NAME>"
+    cmd github-action help="[experimental] Generate a GitHub Action workflow file" {
+        long_help "[experimental] Generate a GitHub Action workflow file\n\nThis command generates a GitHub Action workflow file that runs a mise task like `mise run ci`\nwhen you push changes to your repository."
+        after_long_help "Examples:\n\n    $ mise generate github-action --write --task=ci\n    $ git commit -m \"feat: add new feature\"\n    $ git push # runs `mise run ci` on GitHub\n"
+        flag --name help="the name of the workflow to generate" {
+            arg <NAME>
         }
         flag "-t --task" help="The task to run when the workflow is triggered" {
-            arg "<TASK>"
+            arg <TASK>
         }
         flag "-w --write" help="write to .github/workflows/$name.yml"
     }
-    cmd "task-docs" help="[experimental] Generate documentation for tasks in a project" {
-        after_long_help r"Examples:
-
-    $ mise generate task-docs
-"
+    cmd task-docs help="Generate documentation for tasks in a project" {
+        after_long_help "Examples:\n\n    $ mise generate task-docs\n"
         flag "-I --index" help="write only an index of tasks, intended for use with `--multi`"
         flag "-i --inject" help="inserts the documentation into an existing file" {
             long_help "inserts the documentation into an existing file\n\nThis will look for a special comment, <!-- mise-tasks -->, and replace it with the generated documentation.\nIt will replace everything between the comment and the next comment, <!-- /mise-tasks --> so it can be\nrun multiple times on the same file to update the documentation."
         }
         flag "-m --multi" help="render each task as a separate document, requires `--output` to be a directory"
         flag "-o --output" help="writes the generated docs to a file/directory" {
-            arg "<OUTPUT>"
+            arg <OUTPUT>
         }
         flag "-r --root" help="root directory to search for tasks" {
-            arg "<ROOT>"
+            arg <ROOT>
         }
         flag "-s --style" {
-            arg "<STYLE>" {
-                choices "simple" "detailed"
+            arg <STYLE> {
+                choices simple detailed
             }
         }
     }
+    cmd task-stubs help="[experimental] Generates shims to run mise tasks" {
+        long_help "[experimental] Generates shims to run mise tasks\n\nBy default, this will build shims like ./bin/<task>. These can be paired with `mise generate bootstrap`\nso contributors to a project can execute mise tasks without installing mise into their system."
+        after_long_help "Examples:\n\n    $ mise task add test -- echo 'running tests'\n    $ mise generate task-stubs\n    $ ./bin/test\n    running tests\n"
+        flag "-m --mise-bin" help="Path to a mise bin to use when running the task stub." {
+            long_help "Path to a mise bin to use when running the task stub.\n\nUse `--mise-bin=./bin/mise` to use a mise bin generated from `mise generate bootstrap`"
+            arg <MISE_BIN>
+        }
+        flag "-d --dir" help="Directory to create task stubs inside of" {
+            arg <DIR>
+        }
+    }
 }
-cmd "global" hide=true help="Sets/gets the global tool version(s)" {
-    long_help r"Sets/gets the global tool version(s)
-
-Displays the contents of global config after writing.
-The file is `$HOME/.config/mise/config.toml` by default. It can be changed with `$MISE_GLOBAL_CONFIG_FILE`.
-If `$MISE_GLOBAL_CONFIG_FILE` is set to anything that ends in `.toml`, it will be parsed as `mise.toml`.
-Otherwise, it will be parsed as a `.tool-versions` file.
-
-Use MISE_ASDF_COMPAT=1 to default the global config to ~/.tool-versions
-
-Use `mise local` to set a tool version locally in the current directory."
-    after_long_help r"Examples:
-    # set the current version of node to 20.x
-    # will use a fuzzy version (e.g.: 20) in .tool-versions file
-    $ mise global --fuzzy node@20
-
-    # set the current version of node to 20.x
-    # will use a precise version (e.g.: 20.0.0) in .tool-versions file
-    $ mise global --pin node@20
-
-    # show the current version of node in ~/.tool-versions
-    $ mise global node
-    20.0.0
-"
-    flag "--pin" help="Save exact version to `~/.tool-versions`\ne.g.: `mise global --pin node@20` will save `node 20.0.0` to ~/.tool-versions"
-    flag "--fuzzy" help="Save fuzzy version to `~/.tool-versions`\ne.g.: `mise global --fuzzy node@20` will save `node 20` to ~/.tool-versions\nthis is the default behavior unless MISE_ASDF_COMPAT=1"
-    flag "--remove" help="Remove the plugin(s) from ~/.tool-versions" var=true {
-        arg "<PLUGIN>"
-    }
-    flag "--path" help="Get the path of the global config file"
-    arg "[TOOL@VERSION]..." help="Tool(s) to add to .tool-versions\ne.g.: node@20\nIf this is a single tool with no version, the current value of the global\n.tool-versions will be displayed" var=true
-}
-cmd "hook-env" hide=true help="[internal] called by activate hook to update env vars directory change" {
+cmd global hide=#true help="Sets/gets the global tool version(s)" {
+    long_help "Sets/gets the global tool version(s)\n\nDisplays the contents of global config after writing.\nThe file is `$HOME/.config/mise/config.toml` by default. It can be changed with `$MISE_GLOBAL_CONFIG_FILE`.\nIf `$MISE_GLOBAL_CONFIG_FILE` is set to anything that ends in `.toml`, it will be parsed as `mise.toml`.\nOtherwise, it will be parsed as a `.tool-versions` file.\n\nUse MISE_ASDF_COMPAT=1 to default the global config to ~/.tool-versions\n\nUse `mise local` to set a tool version locally in the current directory."
+    after_long_help "Examples:\n    # set the current version of node to 20.x\n    # will use a fuzzy version (e.g.: 20) in .tool-versions file\n    $ mise global --fuzzy node@20\n\n    # set the current version of node to 20.x\n    # will use a precise version (e.g.: 20.0.0) in .tool-versions file\n    $ mise global --pin node@20\n\n    # show the current version of node in ~/.tool-versions\n    $ mise global node\n    20.0.0\n"
+    flag --pin help="Save exact version to `~/.tool-versions`\ne.g.: `mise global --pin node@20` will save `node 20.0.0` to ~/.tool-versions"
+    flag --fuzzy help="Save fuzzy version to `~/.tool-versions`\ne.g.: `mise global --fuzzy node@20` will save `node 20` to ~/.tool-versions\nthis is the default behavior unless MISE_ASDF_COMPAT=1"
+    flag --remove help="Remove the plugin(s) from ~/.tool-versions" var=#true {
+        arg <PLUGIN>
+    }
+    flag --path help="Get the path of the global config file"
+    arg "[TOOL@VERSION]..." help="Tool(s) to add to .tool-versions\ne.g.: node@20\nIf this is a single tool with no version, the current value of the global\n.tool-versions will be displayed" required=#false var=#true
+}
+cmd hook-env hide=#true help="[internal] called by activate hook to update env vars directory change" {
     flag "-s --shell" help="Shell type to generate script for" {
-        arg "<SHELL>" {
-            choices "bash" "fish" "nu" "xonsh" "zsh"
+        arg <SHELL> {
+            choices bash elvish fish nu xonsh zsh pwsh
         }
     }
-    flag "--status" help="Show \"mise: <PLUGIN>@<VERSION>\" message when changing directories" hide=true
+    flag "-f --force" help="Skip early exit check"
+    flag --status help="Show \"mise: <PLUGIN>@<VERSION>\" message when changing directories" hide=#true
     flag "-q --quiet" help="Hide warnings such as when a tool is not installed"
 }
-cmd "hook-not-found" hide=true help="[internal] called by shell when a command is not found" {
+cmd hook-not-found hide=#true help="[internal] called by shell when a command is not found" {
     flag "-s --shell" help="Shell type to generate script for" {
-        arg "<SHELL>" {
-            choices "bash" "fish" "nu" "xonsh" "zsh"
+        arg <SHELL> {
+            choices bash elvish fish nu xonsh zsh pwsh
         }
     }
-    arg "<BIN>" help="Attempted bin to run"
+    arg <BIN> help="Attempted bin to run"
 }
-cmd "implode" help="Removes mise CLI and all related data" {
-    long_help r"Removes mise CLI and all related data
-
-Skips config directory by default."
-    flag "--config" help="Also remove config directory"
+cmd implode help="Removes mise CLI and all related data" {
+    long_help "Removes mise CLI and all related data\n\nSkips config directory by default."
+    flag --config help="Also remove config directory"
     flag "-n --dry-run" help="List directories that would be removed without actually removing them"
 }
-cmd "install" help="Install a tool version" {
-    alias "i"
-    long_help r"Install a tool version
-
-Installs a tool version to `~/.local/share/mise/installs/<PLUGIN>/<VERSION>`
-Installing alone will not activate the tools so they won't be in PATH.
-To install and/or activate in one command, use `mise use` which will create a `mise.toml` file
-in the current directory to activate this tool when inside the directory.
-Alternatively, run `mise exec <TOOL>@<VERSION> -- <COMMAND>` to execute a tool without creating config files.
-
-Tools will be installed in parallel. To disable, set `--jobs=1` or `MISE_JOBS=1`"
-    after_long_help r"Examples:
-
-    $ mise install node@20.0.0  # install specific node version
-    $ mise install node@20      # install fuzzy node version
-    $ mise install node         # install version specified in mise.toml
-    $ mise install              # installs everything specified in mise.toml
-"
+cmd install help="Install a tool version" {
+    alias i
+    long_help "Install a tool version\n\nInstalls a tool version to `~/.local/share/mise/installs/<PLUGIN>/<VERSION>`\nInstalling alone will not activate the tools so they won't be in PATH.\nTo install and/or activate in one command, use `mise use` which will create a `mise.toml` file\nin the current directory to activate this tool when inside the directory.\nAlternatively, run `mise exec <TOOL>@<VERSION> -- <COMMAND>` to execute a tool without creating config files.\n\nTools will be installed in parallel. To disable, set `--jobs=1` or `MISE_JOBS=1`"
+    after_long_help "Examples:\n\n    $ mise install node@20.0.0  # install specific node version\n    $ mise install node@20      # install fuzzy node version\n    $ mise install node         # install version specified in mise.toml\n    $ mise install              # installs everything specified in mise.toml\n"
     flag "-f --force" help="Force reinstall even if already installed"
     flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
-    flag "--raw" help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
-    flag "-v --verbose" help="Show installation output" var=true count=true {
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
+    flag "-v --verbose" help="Show installation output" var=#true count=#true {
         long_help "Show installation output\n\nThis argument will print plugin output such as download, configuration, and compilation output."
     }
-    arg "[TOOL@VERSION]..." help="Tool(s) to install e.g.: node@20" var=true
+    arg "[TOOL@VERSION]..." help="Tool(s) to install e.g.: node@20" required=#false var=#true
 }
-cmd "latest" help="Gets the latest available version for a plugin" {
-    long_help r"Gets the latest available version for a plugin
-
-Supports prefixes such as `node@20` to get the latest version of node 20."
-    after_long_help r"Examples:
-
-    $ mise latest node@20  # get the latest version of node 20
-    20.0.0
-
-    $ mise latest node     # get the latest stable version of node
-    20.0.0
-"
+cmd install-into help="Install a tool version to a specific path" {
+    long_help "Install a tool version to a specific path\n\nUsed for building a tool to a directory for use outside of mise"
+    after_long_help "Examples:\n\n    # install node@20.0.0 into ./mynode\n    $ mise install-into node@20.0.0 ./mynode && ./mynode/bin/node -v\n    20.0.0\n"
+    arg <TOOL@VERSION> help="Tool to install e.g.: node@20"
+    arg <PATH> help="Path to install the tool into"
+}
+cmd latest help="Gets the latest available version for a plugin" {
+    long_help "Gets the latest available version for a plugin\n\nSupports prefixes such as `node@20` to get the latest version of node 20."
+    after_long_help "Examples:\n\n    $ mise latest node@20  # get the latest version of node 20\n    20.0.0\n\n    $ mise latest node     # get the latest stable version of node\n    20.0.0\n"
     flag "-i --installed" help="Show latest installed instead of available version"
-    arg "<TOOL@VERSION>" help="Tool to get the latest version of"
-    arg "[ASDF_VERSION]" help="The version prefix to use when querying the latest version same as the first argument after the \"@\" used for asdf compatibility" hide=true
+    arg <TOOL@VERSION> help="Tool to get the latest version of"
+    arg "[ASDF_VERSION]" help="The version prefix to use when querying the latest version same as the first argument after the \"@\" used for asdf compatibility" required=#false hide=#true
 }
-cmd "link" help="Symlinks a tool version into mise" {
-    alias "ln"
-    long_help r"Symlinks a tool version into mise
-
-Use this for adding installs either custom compiled outside mise or built with a different tool."
-    after_long_help r"Examples:
-    
-    # build node-20.0.0 with node-build and link it into mise
-    $ node-build 20.0.0 ~/.nodes/20.0.0
-    $ mise link node@20.0.0 ~/.nodes/20.0.0
-
-    # have mise use the python version provided by Homebrew
-    $ brew install node
-    $ mise link node@brew $(brew --prefix node)
-    $ mise use node@brew
-"
+cmd link help="Symlinks a tool version into mise" {
+    alias ln
+    long_help "Symlinks a tool version into mise\n\nUse this for adding installs either custom compiled outside mise or built with a different tool."
+    after_long_help "Examples:\n\n    # build node-20.0.0 with node-build and link it into mise\n    $ node-build 20.0.0 ~/.nodes/20.0.0\n    $ mise link node@20.0.0 ~/.nodes/20.0.0\n\n    # have mise use the python version provided by Homebrew\n    $ brew install node\n    $ mise link node@brew $(brew --prefix node)\n    $ mise use node@brew\n"
     flag "-f --force" help="Overwrite an existing tool version if it exists"
-    arg "<TOOL@VERSION>" help="Tool name and version to create a symlink for"
-    arg "<PATH>" help="The local path to the tool version\ne.g.: ~/.nvm/versions/node/v20.0.0"
+    arg <TOOL@VERSION> help="Tool name and version to create a symlink for"
+    arg <PATH> help="The local path to the tool version\ne.g.: ~/.nvm/versions/node/v20.0.0"
 }
-cmd "local" hide=true help="Sets/gets tool version in local .tool-versions or mise.toml" {
-    alias "l" hide=true
-    long_help r"Sets/gets tool version in local .tool-versions or mise.toml
-
-Use this to set a tool's version when within a directory
-Use `mise global` to set a tool version globally
-This uses `.tool-version` by default unless there is a `mise.toml` file or if `MISE_USE_TOML`
-is set. A future v2 release of mise will default to using `mise.toml`."
-    after_long_help r"Examples:
-    # set the current version of node to 20.x for the current directory
-    # will use a precise version (e.g.: 20.0.0) in .tool-versions file
-    $ mise local node@20
-
-    # set node to 20.x for the current project (recurses up to find .tool-versions)
-    $ mise local -p node@20
-
-    # set the current version of node to 20.x for the current directory
-    # will use a fuzzy version (e.g.: 20) in .tool-versions file
-    $ mise local --fuzzy node@20
-
-    # removes node from .tool-versions
-    $ mise local --remove=node
-
-    # show the current version of node in .tool-versions
-    $ mise local node
-    20.0.0
-"
+cmd local hide=#true help="Sets/gets tool version in local .tool-versions or mise.toml" {
+    alias l hide=#true
+    long_help "Sets/gets tool version in local .tool-versions or mise.toml\n\nUse this to set a tool's version when within a directory\nUse `mise global` to set a tool version globally\nThis uses `.tool-version` by default unless there is a `mise.toml` file or if `MISE_USE_TOML`\nis set. A future v2 release of mise will default to using `mise.toml`."
+    after_long_help "Examples:\n    # set the current version of node to 20.x for the current directory\n    # will use a precise version (e.g.: 20.0.0) in .tool-versions file\n    $ mise local node@20\n\n    # set node to 20.x for the current project (recurses up to find .tool-versions)\n    $ mise local -p node@20\n\n    # set the current version of node to 20.x for the current directory\n    # will use a fuzzy version (e.g.: 20) in .tool-versions file\n    $ mise local --fuzzy node@20\n\n    # removes node from .tool-versions\n    $ mise local --remove=node\n\n    # show the current version of node in .tool-versions\n    $ mise local node\n    20.0.0\n"
     flag "-p --parent" help="Recurse up to find a .tool-versions file rather than using the current directory only\nby default this command will only set the tool in the current directory (\"$PWD/.tool-versions\")"
-    flag "--pin" help="Save exact version to `.tool-versions`\ne.g.: `mise local --pin node@20` will save `node 20.0.0` to .tool-versions"
-    flag "--fuzzy" help="Save fuzzy version to `.tool-versions` e.g.: `mise local --fuzzy node@20` will save `node 20` to .tool-versions This is the default behavior unless MISE_ASDF_COMPAT=1"
-    flag "--remove" help="Remove the plugin(s) from .tool-versions" var=true {
-        arg "<PLUGIN>"
+    flag --pin help="Save exact version to `.tool-versions`\ne.g.: `mise local --pin node@20` will save `node 20.0.0` to .tool-versions"
+    flag --fuzzy help="Save fuzzy version to `.tool-versions` e.g.: `mise local --fuzzy node@20` will save `node 20` to .tool-versions This is the default behavior unless MISE_ASDF_COMPAT=1"
+    flag --remove help="Remove the plugin(s) from .tool-versions" var=#true {
+        arg <PLUGIN>
     }
-    flag "--path" help="Get the path of the config file"
-    arg "[TOOL@VERSION]..." help="Tool(s) to add to .tool-versions/mise.toml\ne.g.: node@20\nif this is a single tool with no version,\nthe current value of .tool-versions/mise.toml will be displayed" var=true
+    flag --path help="Get the path of the config file"
+    arg "[TOOL@VERSION]..." help="Tool(s) to add to .tool-versions/mise.toml\ne.g.: node@20\nif this is a single tool with no version,\nthe current value of .tool-versions/mise.toml will be displayed" required=#false var=#true
 }
-cmd "ls" help="List installed and active tool versions" {
-    alias "list"
-    long_help r#"List installed and active tool versions
-
-This command lists tools that mise "knows about".
-These may be tools that are currently installed, or those
-that are in a config file (active) but may or may not be installed.
-
-It's a useful command to get the current state of your tools."#
-    after_long_help r#"Examples:
-
-    $ mise ls
-    node    20.0.0 ~/src/myapp/.tool-versions latest
-    python  3.11.0 ~/.tool-versions           3.10
-    python  3.10.0
-
-    $ mise ls --current
-    node    20.0.0 ~/src/myapp/.tool-versions 20
-    python  3.11.0 ~/.tool-versions           3.11.0
-
-    $ mise ls --json
-    {
-      "node": [
-        {
-          "version": "20.0.0",
-          "install_path": "/Users/jdx/.mise/installs/node/20.0.0",
-          "source": {
-            "type": "mise.toml",
-            "path": "/Users/jdx/mise.toml"
-          }
-        }
-      ],
-      "python": [...]
-    }
-"#
-    flag "-p --plugin" hide=true {
-        arg "<PLUGIN_FLAG>"
+cmd ls help="List installed and active tool versions" {
+    alias list
+    long_help "List installed and active tool versions\n\nThis command lists tools that mise \"knows about\".\nThese may be tools that are currently installed, or those\nthat are in a config file (active) but may or may not be installed.\n\nIt's a useful command to get the current state of your tools."
+    after_long_help "Examples:\n\n    $ mise ls\n    node    20.0.0 ~/src/myapp/.tool-versions latest\n    python  3.11.0 ~/.tool-versions           3.10\n    python  3.10.0\n\n    $ mise ls --current\n    node    20.0.0 ~/src/myapp/.tool-versions 20\n    python  3.11.0 ~/.tool-versions           3.11.0\n\n    $ mise ls --json\n    {\n      \"node\": [\n        {\n          \"version\": \"20.0.0\",\n          \"install_path\": \"/Users/jdx/.mise/installs/node/20.0.0\",\n          \"source\": {\n            \"type\": \"mise.toml\",\n            \"path\": \"/Users/jdx/mise.toml\"\n          }\n        }\n      ],\n      \"python\": [...]\n    }\n"
+    flag "-p --plugin" hide=#true {
+        arg <TOOL_FLAG>
     }
     flag "-c --current" help="Only show tool versions currently specified in a mise.toml"
     flag "-g --global" help="Only show tool versions currently specified in the global mise.toml"
     flag "-i --installed" help="Only show tool versions that are installed (Hides tools defined in mise.toml but not installed)"
-    flag "--parseable" help="Output in an easily parseable format" hide=true
+    flag "-o --offline" help="Don't fetch information such as outdated versions"
+    flag --outdated help="Display whether a version is outdated"
     flag "-J --json" help="Output in JSON format"
     flag "-m --missing" help="Display missing tool versions"
-    flag "--prefix" help="Display versions matching this prefix" {
-        arg "<PREFIX>"
+    flag --prefix help="Display versions matching this prefix" {
+        arg <PREFIX>
     }
-    flag "--no-header" help="Don't display headers"
-    arg "[PLUGIN]..." help="Only show tool versions from [PLUGIN]" var=true
+    flag --no-header help="Don't display headers"
+    arg "[INSTALLED_TOOL]..." help="Only show tool versions from [TOOL]" required=#false var=#true
 }
-cmd "ls-remote" help="List runtime versions available for install." {
-    alias "list-all" "list-remote" hide=true
-    long_help r"List runtime versions available for install.
-
-Note that the results may be cached, run `mise cache clean` to clear the cache and get fresh results."
-    after_long_help r"Examples:
-
-    $ mise ls-remote node
-    18.0.0
-    20.0.0
-
-    $ mise ls-remote node@20
-    20.0.0
-    20.1.0
-
-    $ mise ls-remote node 20
-    20.0.0
-    20.1.0
-"
-    flag "--all" help="Show all installed plugins and versions"
-    arg "[TOOL@VERSION]" help="Plugin to get versions for"
-    arg "[PREFIX]" help="The version prefix to use when querying the latest version\nsame as the first argument after the \"@\""
-}
-cmd "outdated" help="Shows outdated tool versions" {
-    long_help r"Shows outdated tool versions
-
-See `mise upgrade` to upgrade these versions."
-    after_long_help r#"Examples:
-
-    $ mise outdated
-    Plugin  Requested  Current  Latest
-    python  3.11       3.11.0   3.11.1
-    node    20         20.0.0   20.1.0
-
-    $ mise outdated node
-    Plugin  Requested  Current  Latest
-    node    20         20.0.0   20.1.0
-
-    $ mise outdated --json
-    {"python": {"requested": "3.11", "current": "3.11.0", "latest": "3.11.1"}, ...}
-"#
+cmd ls-remote help="List runtime versions available for install." {
+    alias list-all list-remote hide=#true
+    long_help "List runtime versions available for install.\n\nNote that the results may be cached, run `mise cache clean` to clear the cache and get fresh results."
+    after_long_help "Examples:\n\n    $ mise ls-remote node\n    18.0.0\n    20.0.0\n\n    $ mise ls-remote node@20\n    20.0.0\n    20.1.0\n\n    $ mise ls-remote node 20\n    20.0.0\n    20.1.0\n"
+    flag --all help="Show all installed plugins and versions"
+    arg "[TOOL@VERSION]" help="Tool to get versions for" required=#false
+    arg "[PREFIX]" help="The version prefix to use when querying the latest version\nsame as the first argument after the \"@\"" required=#false
+}
+cmd outdated help="Shows outdated tool versions" {
+    long_help "Shows outdated tool versions\n\nSee `mise upgrade` to upgrade these versions."
+    after_long_help "Examples:\n\n    $ mise outdated\n    Plugin  Requested  Current  Latest\n    python  3.11       3.11.0   3.11.1\n    node    20         20.0.0   20.1.0\n\n    $ mise outdated node\n    Plugin  Requested  Current  Latest\n    node    20         20.0.0   20.1.0\n\n    $ mise outdated --json\n    {\"python\": {\"requested\": \"3.11\", \"current\": \"3.11.0\", \"latest\": \"3.11.1\"}, ...}\n"
     flag "-l --bump" help="Compares against the latest versions available, not what matches the current config" {
         long_help "Compares against the latest versions available, not what matches the current config\n\nFor example, if you have `node = \"20\"` in your config by default `mise outdated` will only\nshow other 20.x versions, not 21.x or 22.x versions.\n\nUsing this flag, if there are 21.x or newer versions it will display those instead of 20.x."
     }
     flag "-J --json" help="Output in JSON format"
-    flag "--no-header" help="Don't show table header"
-    arg "[TOOL@VERSION]..." help="Tool(s) to show outdated versions for\ne.g.: node@20 python@3.10\nIf not specified, all tools in global and local configs will be shown" var=true
+    flag --no-header help="Don't show table header"
+    arg "[TOOL@VERSION]..." help="Tool(s) to show outdated versions for\ne.g.: node@20 python@3.10\nIf not specified, all tools in global and local configs will be shown" required=#false var=#true
 }
-cmd "plugins" help="Manage plugins" {
-    alias "p"
-    alias "plugin" "plugin-list" hide=true
-    flag "-a --all" help="list all available remote plugins" hide=true {
+cmd plugins help="Manage plugins" {
+    alias p
+    alias plugin plugin-list hide=#true
+    flag "-a --all" help="list all available remote plugins" hide=#true {
         long_help "list all available remote plugins\n\nsame as `mise plugins ls-remote`"
     }
     flag "-c --core" help="The built-in plugins only\nNormally these are not shown"
-    flag "--user" help="List installed plugins" {
+    flag --user help="List installed plugins" {
         long_help "List installed plugins\n\nThis is the default behavior but can be used with --core\nto show core and user plugins"
     }
     flag "-u --urls" help="Show the git url for each plugin\ne.g.: https://github.com/asdf-vm/asdf-nodejs.git"
-    flag "--refs" help="Show the git refs for each plugin\ne.g.: main 1234abc" hide=true
-    cmd "install" help="Install a plugin" {
-        alias "i" "a" "add"
-        long_help r"Install a plugin
-
-note that mise automatically can install plugins when you install a tool
-e.g.: `mise install node@20` will autoinstall the node plugin
-
-This behavior can be modified in ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    # install the node via shorthand
-    $ mise plugins install node
-
-    # install the node plugin using a specific git url
-    $ mise plugins install node https://github.com/mise-plugins/rtx-nodejs.git
-
-    # install the node plugin using the git url only
-    # (node is inferred from the url)
-    $ mise plugins install https://github.com/mise-plugins/rtx-nodejs.git
-
-    # install the node plugin using a specific ref
-    $ mise plugins install node https://github.com/mise-plugins/rtx-nodejs.git#v1.0.0
-"
+    flag --refs help="Show the git refs for each plugin\ne.g.: main 1234abc" hide=#true
+    cmd install help="Install a plugin" {
+        alias i a add
+        long_help "Install a plugin\n\nnote that mise automatically can install plugins when you install a tool\ne.g.: `mise install node@20` will autoinstall the node plugin\n\nThis behavior can be modified in ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    # install the node via shorthand\n    $ mise plugins install node\n\n    # install the node plugin using a specific git url\n    $ mise plugins install node https://github.com/mise-plugins/rtx-nodejs.git\n\n    # install the node plugin using the git url only\n    # (node is inferred from the url)\n    $ mise plugins install https://github.com/mise-plugins/rtx-nodejs.git\n\n    # install the node plugin using a specific ref\n    $ mise plugins install node https://github.com/mise-plugins/rtx-nodejs.git#v1.0.0\n"
         flag "-f --force" help="Reinstall even if plugin exists"
         flag "-a --all" help="Install all missing plugins\nThis will only install plugins that have matching shorthands.\ni.e.: they don't need the full git repo url"
-        flag "-v --verbose" help="Show installation output" var=true count=true
-        arg "[NEW_PLUGIN]" help="The name of the plugin to install\ne.g.: node, ruby\nCan specify multiple plugins: `mise plugins install node ruby python`"
-        arg "[GIT_URL]" help="The git url of the plugin"
-        arg "[REST]..." var=true hide=true
-    }
-    cmd "link" help="Symlinks a plugin into mise" {
-        alias "ln"
-        long_help r"Symlinks a plugin into mise
-
-This is used for developing a plugin."
-        after_long_help r#"Examples:
-
-    # essentially just `ln -s ./mise-node ~/.local/share/mise/plugins/node`
-    $ mise plugins link node ./mise-node
-
-    # infer plugin name as "node"
-    $ mise plugins link ./mise-node
-"#
+        flag "-v --verbose" help="Show installation output" var=#true count=#true
+        arg "[NEW_PLUGIN]" help="The name of the plugin to install\ne.g.: node, ruby\nCan specify multiple plugins: `mise plugins install node ruby python`" required=#false
+        arg "[GIT_URL]" help="The git url of the plugin" required=#false
+        arg "[REST]..." required=#false var=#true hide=#true
+    }
+    cmd link help="Symlinks a plugin into mise" {
+        alias ln
+        long_help "Symlinks a plugin into mise\n\nThis is used for developing a plugin."
+        after_long_help "Examples:\n\n    # essentially just `ln -s ./mise-node ~/.local/share/mise/plugins/node`\n    $ mise plugins link node ./mise-node\n\n    # infer plugin name as \"node\"\n    $ mise plugins link ./mise-node\n"
         flag "-f --force" help="Overwrite existing plugin"
-        arg "<NAME>" help="The name of the plugin\ne.g.: node, ruby"
-        arg "[PATH]" help="The local path to the plugin\ne.g.: ./mise-node"
-    }
-    cmd "ls" help="List installed plugins" {
-        alias "list"
-        long_help r"List installed plugins
-
-Can also show remotely available plugins to install."
-        after_long_help r"Examples:
-
-    $ mise plugins ls
-    node
-    ruby
-
-    $ mise plugins ls --urls
-    node    https://github.com/asdf-vm/asdf-nodejs.git
-    ruby    https://github.com/asdf-vm/asdf-ruby.git
-"
-        flag "-a --all" help="List all available remote plugins\nSame as `mise plugins ls-remote`" hide=true
-        flag "-c --core" help="The built-in plugins only\nNormally these are not shown"
-        flag "--user" help="List installed plugins" {
-            long_help "List installed plugins\n\nThis is the default behavior but can be used with --core\nto show core and user plugins"
-        }
+        arg <NAME> help="The name of the plugin\ne.g.: node, ruby"
+        arg "[DIR]" help="The local path to the plugin\ne.g.: ./mise-node" required=#false
+    }
+    cmd ls help="List installed plugins" {
+        alias list
+        long_help "List installed plugins\n\nCan also show remotely available plugins to install."
+        after_long_help "Examples:\n\n    $ mise plugins ls\n    node\n    ruby\n\n    $ mise plugins ls --urls\n    node    https://github.com/asdf-vm/asdf-nodejs.git\n    ruby    https://github.com/asdf-vm/asdf-ruby.git\n"
+        flag "-a --all" help="List all available remote plugins\nSame as `mise plugins ls-remote`" hide=#true
+        flag "-c --core" help="The built-in plugins only\nNormally these are not shown" hide=#true
+        flag --user help="List installed plugins" hide=#true
         flag "-u --urls" help="Show the git url for each plugin\ne.g.: https://github.com/asdf-vm/asdf-nodejs.git"
-        flag "--refs" help="Show the git refs for each plugin\ne.g.: main 1234abc" hide=true
+        flag --refs help="Show the git refs for each plugin\ne.g.: main 1234abc" hide=#true
     }
-    cmd "ls-remote" help="List all available remote plugins" {
-        alias "list-remote" "list-all"
-        long_help r"
-List all available remote plugins
-
-The full list is here: https://github.com/jdx/mise/blob/main/registry.toml
-
-Examples:
-
-    $ mise plugins ls-remote
-"
+    cmd ls-remote help="List all available remote plugins" {
+        alias list-remote list-all
+        long_help "\nList all available remote plugins\n\nThe full list is here: https://github.com/jdx/mise/blob/main/registry.toml\n\nExamples:\n\n    $ mise plugins ls-remote\n"
         flag "-u --urls" help="Show the git url for each plugin e.g.: https://github.com/mise-plugins/mise-poetry.git"
-        flag "--only-names" help="Only show the name of each plugin by default it will show a \"*\" next to installed plugins"
+        flag --only-names help="Only show the name of each plugin by default it will show a \"*\" next to installed plugins"
     }
-    cmd "uninstall" help="Removes a plugin" {
-        alias "remove" "rm"
-        after_long_help r"Examples:
-
-    $ mise uninstall node
-"
+    cmd uninstall help="Removes a plugin" {
+        alias remove rm
+        after_long_help "Examples:\n\n    $ mise uninstall node\n"
         flag "-p --purge" help="Also remove the plugin's installs, downloads, and cache"
         flag "-a --all" help="Remove all plugins"
-        arg "[PLUGIN]..." help="Plugin(s) to remove" var=true
+        arg "[PLUGIN]..." help="Plugin(s) to remove" required=#false var=#true
     }
-    cmd "update" help="Updates a plugin to the latest version" {
-        alias "up" "upgrade"
-        long_help r"Updates a plugin to the latest version
-
-note: this updates the plugin itself, not the runtime versions"
-        after_long_help r"Examples:
-
-    $ mise plugins update            # update all plugins
-    $ mise plugins update node       # update only node
-    $ mise plugins update node#beta  # specify a ref
-"
+    cmd update help="Updates a plugin to the latest version" {
+        alias up upgrade
+        long_help "Updates a plugin to the latest version\n\nnote: this updates the plugin itself, not the runtime versions"
+        after_long_help "Examples:\n\n    $ mise plugins update            # update all plugins\n    $ mise plugins update node       # update only node\n    $ mise plugins update node#beta  # specify a ref\n"
         flag "-j --jobs" help="Number of jobs to run in parallel\nDefault: 4" {
-            arg "<JOBS>"
+            arg <JOBS>
         }
-        arg "[PLUGIN]..." help="Plugin(s) to update" var=true
+        arg "[PLUGIN]..." help="Plugin(s) to update" required=#false var=#true
     }
 }
-cmd "prune" help="Delete unused versions of tools" {
-    long_help r"Delete unused versions of tools
-
-mise tracks which config files have been used in ~/.local/share/mise/tracked_config_files
-Versions which are no longer the latest specified in any of those configs are deleted.
-Versions installed only with environment variables `MISE_<PLUGIN>_VERSION` will be deleted,
-as will versions only referenced on the command line `mise exec <PLUGIN>@<VERSION>`."
-    after_long_help r"Examples:
-
-    $ mise prune --dry-run
-    rm -rf ~/.local/share/mise/versions/node/20.0.0
-    rm -rf ~/.local/share/mise/versions/node/20.0.1
-"
+cmd prune help="Delete unused versions of tools" {
+    long_help "Delete unused versions of tools\n\nmise tracks which config files have been used in ~/.local/state/mise/tracked-configs\nVersions which are no longer the latest specified in any of those configs are deleted.\nVersions installed only with environment variables `MISE_<PLUGIN>_VERSION` will be deleted,\nas will versions only referenced on the command line `mise exec <PLUGIN>@<VERSION>`."
+    after_long_help "Examples:\n\n    $ mise prune --dry-run\n    rm -rf ~/.local/share/mise/versions/node/20.0.0\n    rm -rf ~/.local/share/mise/versions/node/20.0.1\n"
     flag "-n --dry-run" help="Do not actually delete anything"
-    flag "--configs" help="Prune only tracked and trusted configuration links that point to non-existent configurations"
-    flag "--tools" help="Prune only unused versions of tools"
-    arg "[PLUGIN]..." help="Prune only versions from this plugin(s)" var=true
+    flag --configs help="Prune only tracked and trusted configuration links that point to non-existent configurations"
+    flag --tools help="Prune only unused versions of tools"
+    arg "[INSTALLED_TOOL]..." help="Prune only these tools" required=#false var=#true
 }
-cmd "registry" help="[experimental] List available tools to install" {
-    long_help r"[experimental] List available tools to install
-
-This command lists the tools available in the registry as shorthand names.
-
-For example, `poetry` is shorthand for `asdf:mise-plugins/mise-poetry`."
-    after_long_help r"Examples:
-
-    $ mise registry
-    node    core:node
-    poetry  asdf:mise-plugins/mise-poetry
-    ubi     cargo:ubi-cli
-"
-}
-cmd "reshim" help="Creates new shims based on bin paths from currently installed tools." {
-    long_help r#"Creates new shims based on bin paths from currently installed tools.
-
-This creates new shims in ~/.local/share/mise/shims for CLIs that have been added.
-mise will try to do this automatically for commands like `npm i -g` but there are
-other ways to install things (like using yarn or pnpm for node) that mise does
-not know about and so it will be necessary to call this explicitly.
-
-If you think mise should automatically call this for a particular command, please
-open an issue on the mise repo. You can also setup a shell function to reshim
-automatically (it's really fast so you don't need to worry about overhead):
-
-npm() {
-  command npm "$@"
-  mise reshim
+cmd registry help="List available tools to install" {
+    long_help "List available tools to install\n\nThis command lists the tools available in the registry as shorthand names.\n\nFor example, `poetry` is shorthand for `asdf:mise-plugins/mise-poetry`."
+    after_long_help "Examples:\n\n    $ mise registry\n    node    core:node\n    poetry  asdf:mise-plugins/mise-poetry\n    ubi     cargo:ubi-cli\n\n    $ mise registry poetry\n    asdf:mise-plugins/mise-poetry\n"
+    flag "-b --backend" help="Show only tools for this backend" {
+        arg <BACKEND>
+    }
+    flag --complete help="Print all tools with descriptions for shell completions" hide=#true
+    flag --hide-aliased help="Hide aliased tools"
+    arg "[NAME]" help="Show only the specified tool's full name" required=#false
 }
-
-Note that this creates shims for _all_ installed tools, not just the ones that are
-currently active in mise.toml."#
-    after_long_help r"Examples:
-
-    $ mise reshim
-    $ ~/.local/share/mise/shims/node -v
-    v20.0.0
-"
+cmd reshim help="Creates new shims based on bin paths from currently installed tools." {
+    long_help "Creates new shims based on bin paths from currently installed tools.\n\nThis creates new shims in ~/.local/share/mise/shims for CLIs that have been added.\nmise will try to do this automatically for commands like `npm i -g` but there are\nother ways to install things (like using yarn or pnpm for node) that mise does\nnot know about and so it will be necessary to call this explicitly.\n\nIf you think mise should automatically call this for a particular command, please\nopen an issue on the mise repo. You can also setup a shell function to reshim\nautomatically (it's really fast so you don't need to worry about overhead):\n\n    npm() {\n      command npm \"$@\"\n      mise reshim\n    }\n\nNote that this creates shims for _all_ installed tools, not just the ones that are\ncurrently active in mise.toml."
+    after_long_help "Examples:\n\n    $ mise reshim\n    $ ~/.local/share/mise/shims/node -v\n    v20.0.0\n"
     flag "-f --force" help="Removes all shims before reshimming"
-    arg "[PLUGIN]" hide=true
-    arg "[VERSION]" hide=true
+    arg "[PLUGIN]" required=#false hide=#true
+    arg "[VERSION]" required=#false hide=#true
 }
-cmd "run" help="[experimental] Run task(s)" {
-    alias "r"
-    long_help r#"[experimental] Run task(s)
-
-This command will run a tasks, or multiple tasks in parallel.
-Tasks may have dependencies on other tasks or on source files.
-If source is configured on a tasks, it will only run if the source
-files have changed.
-
-Tasks can be defined in mise.toml or as standalone scripts.
-In mise.toml, tasks take this form:
-
-    [tasks.build]
-    run = "npm run build"
-    sources = ["src/**/*.ts"]
-    outputs = ["dist/**/*.js"]
-
-Alternatively, tasks can be defined as standalone scripts.
-These must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or
-`.config/mise/tasks`.
-The name of the script will be the name of the tasks.
-
-    $ cat .mise/tasks/build<<EOF
-    #!/usr/bin/env bash
-    npm run build
-    EOF
-    $ mise run build"#
-    after_long_help r#"Examples:
-
-    # Runs the "lint" tasks. This needs to either be defined in mise.toml
-    # or as a standalone script. See the project README for more information.
-    $ mise run lint
-
-    # Forces the "build" tasks to run even if its sources are up-to-date.
-    $ mise run build --force
-
-    # Run "test" with stdin/stdout/stderr all connected to the current terminal.
-    # This forces `--jobs=1` to prevent interleaving of output.
-    $ mise run test --raw
-
-    # Runs the "lint", "test", and "check" tasks in parallel.
-    $ mise run lint ::: test ::: check
-
-    # Execute multiple tasks each with their own arguments.
-    $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2
-"#
+cmd run help="Run task(s)" {
+    alias r
+    long_help "Run task(s)\n\nThis command will run a tasks, or multiple tasks in parallel.\nTasks may have dependencies on other tasks or on source files.\nIf source is configured on a tasks, it will only run if the source\nfiles have changed.\n\nTasks can be defined in mise.toml or as standalone scripts.\nIn mise.toml, tasks take this form:\n\n    [tasks.build]\n    run = \"npm run build\"\n    sources = [\"src/**/*.ts\"]\n    outputs = [\"dist/**/*.js\"]\n\nAlternatively, tasks can be defined as standalone scripts.\nThese must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or\n`.config/mise/tasks`.\nThe name of the script will be the name of the tasks.\n\n    $ cat .mise/tasks/build<<EOF\n    #!/usr/bin/env bash\n    npm run build\n    EOF\n    $ mise run build"
+    after_long_help "Examples:\n\n    # Runs the \"lint\" tasks. This needs to either be defined in mise.toml\n    # or as a standalone script. See the project README for more information.\n    $ mise run lint\n\n    # Forces the \"build\" tasks to run even if its sources are up-to-date.\n    $ mise run build --force\n\n    # Run \"test\" with stdin/stdout/stderr all connected to the current terminal.\n    # This forces `--jobs=1` to prevent interleaving of output.\n    $ mise run test --raw\n\n    # Runs the \"lint\", \"test\", and \"check\" tasks in parallel.\n    $ mise run lint ::: test ::: check\n\n    # Execute multiple tasks each with their own arguments.\n    $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2\n"
     flag "-C --cd" help="Change to this directory before executing the command" {
-        arg "<CD>"
+        arg <CD>
     }
+    flag "-c --continue-on-error" help="Continue running tasks even if one fails"
     flag "-n --dry-run" help="Don't actually run the tasks(s), just print them in order of execution"
     flag "-f --force" help="Force the tasks to run even if outputs are up to date"
-    flag "-p --prefix" help="Print stdout/stderr by line, prefixed with the tasks's label\nDefaults to true if --jobs > 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var"
-    flag "-i --interleave" help="Print directly to stdout/stderr instead of by line\nDefaults to true if --jobs == 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var"
-    flag "-t --tool" help="Tool(s) to also add e.g.: node@20 python@3.10" var=true {
-        arg "<TOOL@VERSION>"
+    flag "-p --prefix" help="Print stdout/stderr by line, prefixed with the task's label\nDefaults to true if --jobs > 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var" hide=#true
+    flag "-i --interleave" help="Print directly to stdout/stderr instead of by line\nDefaults to true if --jobs == 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var" hide=#true
+    flag "-s --shell" help="Shell to use to run toml tasks" {
+        long_help "Shell to use to run toml tasks\n\nDefaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows\nCan also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`\nOr it can be overridden with the `shell` property on a task."
+        arg <SHELL>
+    }
+    flag "-t --tool" help="Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10" var=#true {
+        arg <TOOL@VERSION>
     }
     flag "-j --jobs" help="Number of tasks to run in parallel\n[default: 4]\nConfigure with `jobs` config or `MISE_JOBS` env var" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
     flag "-r --raw" help="Read/write directly to stdin/stdout/stderr instead of by line\nConfigure with `raw` config or `MISE_RAW` env var"
-    flag "--timings" help="Shows elapsed time after each tasks"
+    flag --timings help="Shows elapsed time after each task completes" hide=#true {
+        long_help "Shows elapsed time after each task completes\n\nDefault to always show with `MISE_TASK_TIMINGS=1`"
+    }
+    flag --no-timings help="Hides elapsed time after each task completes" {
+        long_help "Hides elapsed time after each task completes\n\nDefault to always hide with `MISE_TASK_TIMINGS=0`"
+    }
+    flag "-q --quiet" help="Don't show extra output"
+    flag "-S --silent" help="Don't show any output except for errors"
+    flag "-o --output" help="Change how tasks information is output when running tasks" {
+        long_help "Change how tasks information is output when running tasks\n\n- `prefix` - Print stdout/stderr by line, prefixed with the task's label\n- `interleave` - Print directly to stdout/stderr instead of by line\n- `replacing` - Stdout is replaced each time, stderr is printed as is\n- `timed` - Only show stdout lines if they are displayed for more than 1 second\n- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output\n- `quiet` - Don't show extra output\n- `silent` - Don't show any output including stdout and stderr from the task except for errors"
+        arg <OUTPUT>
+    }
     mount run="mise tasks --usage"
 }
-cmd "self-update" help="Updates mise itself." {
-    long_help r"Updates mise itself.
-
-Uses the GitHub Releases API to find the latest release and binary.
-By default, this will also update any installed plugins.
-Uses the `GITHUB_API_TOKEN` environment variable if set for higher rate limits.
-
-This command is not available if mise is installed via a package manager."
+cmd self-update help="Updates mise itself." {
+    long_help "Updates mise itself.\n\nUses the GitHub Releases API to find the latest release and binary.\nBy default, this will also update any installed plugins.\nUses the `GITHUB_API_TOKEN` environment variable if set for higher rate limits.\n\nThis command is not available if mise is installed via a package manager."
     flag "-f --force" help="Update even if already up to date"
-    flag "--no-plugins" help="Disable auto-updating plugins"
+    flag --no-plugins help="Disable auto-updating plugins"
     flag "-y --yes" help="Skip confirmation prompt"
-    arg "[VERSION]" help="Update to a specific version"
+    arg "[VERSION]" help="Update to a specific version" required=#false
 }
-cmd "set" help="Set environment variables in mise.toml" {
-    alias "ev" "env-vars" hide=true
-    long_help r"Set environment variables in mise.toml
-
-By default, this command modifies `mise.toml` in the current directory."
-    after_long_help r"Examples:
-
-    $ mise set NODE_ENV=production
-
-    $ mise set NODE_ENV
-    production
-
-    $ mise set
-    key       value       source
-    NODE_ENV  production  ~/.config/mise/config.toml
-"
-    flag "--file" help="The TOML file to update" {
+cmd set help="Set environment variables in mise.toml" {
+    alias ev env-vars hide=#true
+    long_help "Set environment variables in mise.toml\n\nBy default, this command modifies `mise.toml` in the current directory."
+    after_long_help "Examples:\n\n    $ mise set NODE_ENV=production\n\n    $ mise set NODE_ENV\n    production\n\n    $ mise set\n    key       value       source\n    NODE_ENV  production  ~/.config/mise/config.toml\n"
+    flag --file help="The TOML file to update" {
         long_help "The TOML file to update\n\nDefaults to MISE_DEFAULT_CONFIG_FILENAME environment variable, or `mise.toml`."
-        arg "<FILE>"
+        arg <FILE>
     }
+    flag --complete help="Render completions" hide=#true
     flag "-g --global" help="Set the environment variable in the global config file"
-    flag "--remove" help="Remove the environment variable from config file" var=true hide=true {
+    flag "--remove --rm --unset" help="Remove the environment variable from config file" var=#true hide=#true {
         long_help "Remove the environment variable from config file\n\nCan be used multiple times."
-        arg "<ENV_VAR>"
+        arg <ENV_KEY>
     }
-    arg "[ENV_VARS]..." help="Environment variable(s) to set\ne.g.: NODE_ENV=production" var=true
+    arg "[ENV_VAR]..." help="Environment variable(s) to set\ne.g.: NODE_ENV=production" required=#false var=#true
 }
-cmd "settings" help="Manage settings" {
-    flag "--keys" help="Only display key names for each setting"
-    cmd "add" help="Adds a setting to the configuration file" {
-        long_help r"Adds a setting to the configuration file
-
-Used with an array setting, this will append the value to the array.
-This modifies the contents of ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    $ mise settings add disable_hints python_multi
-"
-        arg "<SETTING>" help="The setting to set"
-        arg "<VALUE>" help="The value to set"
-    }
-    cmd "get" help="Show a current setting" {
-        long_help r"Show a current setting
-
-This is the contents of a single entry in ~/.config/mise/config.toml
-
-Note that aliases are also stored in this file
-but managed separately with `mise aliases get`"
-        after_long_help r"Examples:
-
-    $ mise settings get legacy_version_file
-    true
-"
-        arg "<SETTING>" help="The setting to show"
-    }
-    cmd "ls" help="Show current settings" {
-        alias "list"
-        long_help r"Show current settings
-
-This is the contents of ~/.config/mise/config.toml
-
-Note that aliases are also stored in this file
-but managed separately with `mise aliases`"
-        after_long_help r"Examples:
-
-    $ mise settings
-    legacy_version_file = false
-"
-        flag "--keys" help="Only display key names for each setting"
-    }
-    cmd "set" help="Add/update a setting" {
-        alias "create"
-        long_help r"Add/update a setting
-
-This modifies the contents of ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    $ mise settings set legacy_version_file true
-"
-        arg "<SETTING>" help="The setting to set"
-        arg "<VALUE>" help="The value to set"
-    }
-    cmd "unset" help="Clears a setting" {
-        alias "rm" "remove" "delete" "del"
-        long_help r"Clears a setting
-
-This modifies the contents of ~/.config/mise/config.toml"
-        after_long_help r"Examples:
-
-    $ mise settings unset legacy_version_file
-"
-        arg "<SETTING>" help="The setting to remove"
+cmd settings help="Manage settings" {
+    long_help "Show current settings\n\nThis is the contents of ~/.config/mise/config.toml\n\nNote that aliases are also stored in this file\nbut managed separately with `mise aliases`"
+    after_long_help "Examples:\n    # list all settings\n    $ mise settings\n\n    # get the value of the setting \"always_keep_download\"\n    $ mise settings always_keep_download\n\n    # set the value of the setting \"always_keep_download\" to \"true\"\n    $ mise settings always_keep_download=true\n\n    # set the value of the setting \"node.mirror_url\" to \"https://npm.taobao.org/mirrors/node\"\n    $ mise settings node.mirror_url https://npm.taobao.org/mirrors/node\n"
+    flag "-a --all" help="List all settings"
+    flag --complete help="Print all settings with descriptions for shell completions" hide=#true
+    flag "-l --local" help="Use the local config file instead of the global one" global=#true
+    flag "-J --json" help="Output in JSON format"
+    flag --json-extended help="Output in JSON format with sources"
+    flag "-T --toml" help="Output in TOML format"
+    arg "[SETTING]" help="Name of setting" required=#false
+    arg "[VALUE]" help="Setting value to set" required=#false
+    cmd add help="Adds a setting to the configuration file" {
+        long_help "Adds a setting to the configuration file\n\nUsed with an array setting, this will append the value to the array.\nThis modifies the contents of ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise settings add disable_hints python_multi\n"
+        flag "-l --local" help="Use the local config file instead of the global one"
+        arg <SETTING> help="The setting to set"
+        arg <VALUE> help="The value to set"
+    }
+    cmd get help="Show a current setting" {
+        long_help "Show a current setting\n\nThis is the contents of a single entry in ~/.config/mise/config.toml\n\nNote that aliases are also stored in this file\nbut managed separately with `mise aliases get`"
+        after_long_help "Examples:\n\n    $ mise settings get idiomatic_version_file\n    true\n"
+        flag "-l --local" help="Use the local config file instead of the global one"
+        arg <SETTING> help="The setting to show"
+    }
+    cmd ls help="Show current settings" {
+        alias list
+        long_help "Show current settings\n\nThis is the contents of ~/.config/mise/config.toml\n\nNote that aliases are also stored in this file\nbut managed separately with `mise aliases`"
+        after_long_help "Examples:\n\n    $ mise settings ls\n    idiomatic_version_file = false\n    ...\n\n    $ mise settings ls python\n    default_packages_file = \"~/.default-python-packages\"\n    ...\n"
+        flag "-a --all" help="List all settings"
+        flag --complete help="Print all settings with descriptions for shell completions" hide=#true
+        flag "-l --local" help="Use the local config file instead of the global one" global=#true
+        flag "-J --json" help="Output in JSON format"
+        flag --json-extended help="Output in JSON format with sources"
+        flag "-T --toml" help="Output in TOML format"
+        arg "[SETTING]" help="Name of setting" required=#false
+    }
+    cmd set help="Add/update a setting" {
+        alias create
+        long_help "Add/update a setting\n\nThis modifies the contents of ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise settings idiomatic_version_file=true\n"
+        flag "-l --local" help="Use the local config file instead of the global one"
+        arg <SETTING> help="The setting to set"
+        arg <VALUE> help="The value to set"
+    }
+    cmd unset help="Clears a setting" {
+        alias rm remove delete del
+        long_help "Clears a setting\n\nThis modifies the contents of ~/.config/mise/config.toml"
+        after_long_help "Examples:\n\n    $ mise settings unset idiomatic_version_file\n"
+        flag "-l --local" help="Use the local config file instead of the global one"
+        arg <KEY> help="The setting to remove"
     }
 }
-cmd "shell" help="Sets a tool version for the current session." {
-    alias "sh"
-    long_help r#"Sets a tool version for the current session.
-
-Only works in a session where mise is already activated.
-
-This works by setting environment variables for the current shell session
-such as `MISE_NODE_VERSION=20` which is "eval"ed as a shell function created by `mise activate`."#
-    after_long_help r"Examples:
-
-    $ mise shell node@20
-    $ node -v
-    v20.0.0
-"
+cmd shell help="Sets a tool version for the current session." {
+    alias sh
+    long_help "Sets a tool version for the current session.\n\nOnly works in a session where mise is already activated.\n\nThis works by setting environment variables for the current shell session\nsuch as `MISE_NODE_VERSION=20` which is \"eval\"ed as a shell function created by `mise activate`."
+    after_long_help "Examples:\n\n    $ mise shell node@20\n    $ node -v\n    v20.0.0\n"
     flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
-    flag "--raw" help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
     flag "-u --unset" help="Removes a previously set version"
-    arg "[TOOL@VERSION]..." help="Tool(s) to use" var=true
+    arg <TOOL@VERSION>... help="Tool(s) to use" var=#true
 }
-cmd "sync" subcommand_required=true help="Add tool versions from external tools to mise" {
-    cmd "node" help="Symlinks all tool versions from an external tool into mise" {
-        long_help r"Symlinks all tool versions from an external tool into mise
-
-For example, use this to import all Homebrew node installs into mise"
-        after_long_help r"Examples:
-
-    $ brew install node@18 node@20
-    $ mise sync node --brew
-    $ mise use -g node@18 - uses Homebrew-provided node
-"
-        flag "--brew" help="Get tool versions from Homebrew"
-        flag "--nvm" help="Get tool versions from nvm"
-        flag "--nodenv" help="Get tool versions from nodenv"
-    }
-    cmd "python" help="Symlinks all tool versions from an external tool into mise" {
-        long_help r"Symlinks all tool versions from an external tool into mise
-
-For example, use this to import all pyenv installs into mise"
-        after_long_help r"Examples:
-
-    $ pyenv install 3.11.0
-    $ mise sync python --pyenv
-    $ mise use -g python@3.11.0 - uses pyenv-provided python
-"
-        flag "--pyenv" help="Get tool versions from pyenv" required=true
+cmd sync subcommand_required=#true help="Synchronize tools from other version managers with mise" {
+    cmd node help="Symlinks all tool versions from an external tool into mise" {
+        long_help "Symlinks all tool versions from an external tool into mise\n\nFor example, use this to import all Homebrew node installs into mise\n\nThis won't overwrite any existing installs but will overwrite any existing symlinks"
+        after_long_help "Examples:\n\n    $ brew install node@18 node@20\n    $ mise sync node --brew\n    $ mise use -g node@18 - uses Homebrew-provided node\n"
+        flag --brew help="Get tool versions from Homebrew"
+        flag --nvm help="Get tool versions from nvm"
+        flag --nodenv help="Get tool versions from nodenv"
+    }
+    cmd python help="Symlinks all tool versions from an external tool into mise" {
+        long_help "Symlinks all tool versions from an external tool into mise\n\nFor example, use this to import all pyenv installs into mise\n\nThis won't overwrite any existing installs but will overwrite any existing symlinks"
+        after_long_help "Examples:\n\n    $ pyenv install 3.11.0\n    $ mise sync python --pyenv\n    $ mise use -g python@3.11.0 - uses pyenv-provided python\n    \n    $ uv python install 3.11.0\n    $ mise install python@3.10.0\n    $ mise sync python --uv\n    $ mise x python@3.11.0 -- python -V - uses uv-provided python\n    $ uv run -p 3.10.0 -- python -V - uses mise-provided python\n"
+        flag --pyenv help="Get tool versions from pyenv"
+        flag --uv help="Sync tool versions with uv (2-way sync)"
+    }
+    cmd ruby help="Symlinks all ruby tool versions from an external tool into mise" {
+        after_long_help "Examples:\n\n    $ brew install ruby\n    $ mise sync ruby --brew\n    $ mise use -g ruby - Use the latest version of Ruby installed by Homebrew\n"
+        flag --brew help="Get tool versions from Homebrew"
     }
 }
-cmd "tasks" help="[experimental] Manage tasks" {
-    alias "t"
-    alias "task" hide=true
-    after_long_help r"Examples:
-
-    $ mise tasks ls
-"
-    flag "--no-header" help="Do not print table header"
-    flag "-x --extended" help="Show all columns"
-    flag "--hidden" help="Show hidden tasks"
-    flag "--sort" help="Sort by column. Default is name." {
-        arg "<COLUMN>" {
-            choices "name" "alias" "description" "source"
+cmd tasks help="Manage tasks" {
+    alias t
+    alias task hide=#true
+    after_long_help "Examples:\n\n    $ mise tasks ls\n"
+    flag --no-header help="Do not print table header" global=#true
+    flag --complete help="Display tasks for usage completion" hide=#true
+    flag "-x --extended" help="Show all columns" global=#true
+    flag --hidden help="Show hidden tasks" global=#true
+    flag --sort help="Sort by column. Default is name." global=#true {
+        arg <COLUMN> {
+            choices name alias description source
         }
     }
-    flag "--sort-order" help="Sort order. Default is asc." {
-        arg "<SORT_ORDER>" {
-            choices "asc" "desc"
+    flag --sort-order help="Sort order. Default is asc." global=#true {
+        arg <SORT_ORDER> {
+            choices asc desc
         }
     }
-    flag "-J --json" help="Output in JSON format"
-    flag "--usage" hide=true
-    cmd "deps" help="[experimental] Display a tree visualization of a dependency graph" {
-        after_long_help r#"Examples:
-
-    # Show dependencies for all tasks
-    $ mise tasks deps
-
-    # Show dependencies for the "lint", "test" and "check" tasks
-    $ mise tasks deps lint test check
-
-    # Show dependencies in DOT format
-    $ mise tasks deps --dot
-"#
-        flag "--hidden" help="Show hidden tasks"
-        flag "--dot" help="Display dependencies in DOT format"
-        arg "[TASKS]..." help="Tasks to show dependencies for\nCan specify multiple tasks by separating with spaces\ne.g.: mise tasks deps lint test check" var=true
-    }
-    cmd "edit" help="[experimental] Edit a tasks with $EDITOR" {
-        long_help r"[experimental] Edit a tasks with $EDITOR
-
-The tasks will be created as a standalone script if it does not already exist."
-        after_long_help r"Examples:
-
-    $ mise tasks edit build
-    $ mise tasks edit test
-"
+    flag "-J --json" help="Output in JSON format" global=#true
+    flag --usage hide=#true global=#true
+    arg "[TASK]" help="Task name to get info of" required=#false
+    cmd add help="Create a new task" {
+        after_long_help "Examples:\n\n    $ mise task add pre-commit --depends \"test\" --depends \"render\" -- echo pre-commit\n"
+        flag --description help="Description of the task" {
+            arg <DESCRIPTION>
+        }
+        flag "-a --alias" help="Other names for the task" var=#true {
+            arg <ALIAS>
+        }
+        flag --depends-post help="Dependencies to run after the task runs" var=#true {
+            arg <DEPENDS_POST>
+        }
+        flag "-w --wait-for" help="Wait for these tasks to complete if they are to run" var=#true {
+            arg <WAIT_FOR>
+        }
+        flag "-D --dir" help="Run the task in a specific directory" {
+            arg <DIR>
+        }
+        flag "-H --hide" help="Hide the task from `mise task` and completions"
+        flag "-r --raw" help="Directly connect stdin/stdout/stderr"
+        flag "-s --sources" help="Glob patterns of files this task uses as input" var=#true {
+            arg <SOURCES>
+        }
+        flag --outputs help="Glob patterns of files this task creates, to skip if they are not modified" var=#true {
+            arg <OUTPUTS>
+        }
+        flag --shell help="Run the task in a specific shell" {
+            arg <SHELL>
+        }
+        flag "-q --quiet" help="Do not print the command before running"
+        flag --silent help="Do not print the command or its output"
+        flag "-d --depends" help="Add dependencies to the task" var=#true {
+            arg <DEPENDS>
+        }
+        flag --run-windows help="Command to run on windows" {
+            arg <RUN_WINDOWS>
+        }
+        flag "-f --file" help="Create a file task instead of a toml task"
+        arg <TASK> help="Tasks name to add"
+        arg "[-- RUN]..." required=#false var=#true
+    }
+    cmd deps help="Display a tree visualization of a dependency graph" {
+        after_long_help "Examples:\n\n    # Show dependencies for all tasks\n    $ mise tasks deps\n\n    # Show dependencies for the \"lint\", \"test\" and \"check\" tasks\n    $ mise tasks deps lint test check\n\n    # Show dependencies in DOT format\n    $ mise tasks deps --dot\n"
+        flag --hidden help="Show hidden tasks"
+        flag --dot help="Display dependencies in DOT format"
+        arg "[TASKS]..." help="Tasks to show dependencies for\nCan specify multiple tasks by separating with spaces\ne.g.: mise tasks deps lint test check" required=#false var=#true
+    }
+    cmd edit help="Edit a tasks with $EDITOR" {
+        long_help "Edit a tasks with $EDITOR\n\nThe tasks will be created as a standalone script if it does not already exist."
+        after_long_help "Examples:\n\n    $ mise tasks edit build\n    $ mise tasks edit test\n"
         flag "-p --path" help="Display the path to the tasks instead of editing it"
-        arg "<TASK>" help="Tasks to edit"
-    }
-    cmd "info" help="[experimental] Get information about a task" {
-        after_long_help r#"Examples:
-
-    $ mise tasks info
-    Name: test
-    Aliases: t
-    Description: Test the application
-    Source: ~/src/myproj/mise.toml
-
-    $ mise tasks info test --json
-    {
-      "name": "test",
-      "aliases": "t",
-      "description": "Test the application",
-      "source": "~/src/myproj/mise.toml",
-      "depends": [],
-      "env": {},
-      "dir": null,
-      "hide": false,
-      "raw": false,
-      "sources": [],
-      "outputs": [],
-      "run": [
-        "echo \"testing!\""
-      ],
-      "file": null,
-      "usage_spec": {}
+        arg <TASK> help="Tasks to edit"
     }
-"#
+    cmd info help="Get information about a task" {
+        after_long_help "Examples:\n\n    $ mise tasks info\n    Name: test\n    Aliases: t\n    Description: Test the application\n    Source: ~/src/myproj/mise.toml\n\n    $ mise tasks info test --json\n    {\n      \"name\": \"test\",\n      \"aliases\": \"t\",\n      \"description\": \"Test the application\",\n      \"source\": \"~/src/myproj/mise.toml\",\n      \"depends\": [],\n      \"env\": {},\n      \"dir\": null,\n      \"hide\": false,\n      \"raw\": false,\n      \"sources\": [],\n      \"outputs\": [],\n      \"run\": [\n        \"echo \\\"testing!\\\"\"\n      ],\n      \"file\": null,\n      \"usage_spec\": {}\n    }\n"
         flag "-J --json" help="Output in JSON format"
-        arg "<TASK>" help="Name of the task to get information about"
-    }
-    cmd "ls" help="[experimental] List available tasks to execute\nThese may be included from the config file or from the project's .mise/tasks directory\nmise will merge all tasks from all parent directories into this list." {
-        long_help r"[experimental] List available tasks to execute
-These may be included from the config file or from the project's .mise/tasks directory
-mise will merge all tasks from all parent directories into this list.
-
-So if you have global tasks in `~/.config/mise/tasks/*` and project-specific tasks in
-~/myproject/.mise/tasks/*, then they'll both be available but the project-specific
-tasks will override the global ones if they have the same name."
-        after_long_help r"Examples:
-
-    $ mise tasks ls
-"
-        flag "--no-header" help="Do not print table header"
-        flag "-x --extended" help="Show all columns"
-        flag "--hidden" help="Show hidden tasks"
-        flag "--sort" help="Sort by column. Default is name." {
-            arg "<COLUMN>" {
-                choices "name" "alias" "description" "source"
+        arg <TASK> help="Name of the task to get information about"
+    }
+    cmd ls help="List available tasks to execute\nThese may be included from the config file or from the project's .mise/tasks directory\nmise will merge all tasks from all parent directories into this list." {
+        long_help "List available tasks to execute\nThese may be included from the config file or from the project's .mise/tasks directory\nmise will merge all tasks from all parent directories into this list.\n\nSo if you have global tasks in `~/.config/mise/tasks/*` and project-specific tasks in\n~/myproject/.mise/tasks/*, then they'll both be available but the project-specific\ntasks will override the global ones if they have the same name."
+        after_long_help "Examples:\n\n    $ mise tasks ls\n"
+        flag --no-header help="Do not print table header" global=#true
+        flag --complete help="Display tasks for usage completion" hide=#true
+        flag "-x --extended" help="Show all columns" global=#true
+        flag --hidden help="Show hidden tasks" global=#true
+        flag --sort help="Sort by column. Default is name." global=#true {
+            arg <COLUMN> {
+                choices name alias description source
             }
         }
-        flag "--sort-order" help="Sort order. Default is asc." {
-            arg "<SORT_ORDER>" {
-                choices "asc" "desc"
+        flag --sort-order help="Sort order. Default is asc." global=#true {
+            arg <SORT_ORDER> {
+                choices asc desc
             }
         }
-        flag "-J --json" help="Output in JSON format"
-        flag "--usage" hide=true
+        flag "-J --json" help="Output in JSON format" global=#true
+        flag --usage hide=#true global=#true
     }
-    cmd "run" help="[experimental] Run task(s)" {
-        alias "r"
-        long_help r#"[experimental] Run task(s)
-
-This command will run a tasks, or multiple tasks in parallel.
-Tasks may have dependencies on other tasks or on source files.
-If source is configured on a tasks, it will only run if the source
-files have changed.
-
-Tasks can be defined in mise.toml or as standalone scripts.
-In mise.toml, tasks take this form:
-
-    [tasks.build]
-    run = "npm run build"
-    sources = ["src/**/*.ts"]
-    outputs = ["dist/**/*.js"]
-
-Alternatively, tasks can be defined as standalone scripts.
-These must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or
-`.config/mise/tasks`.
-The name of the script will be the name of the tasks.
-
-    $ cat .mise/tasks/build<<EOF
-    #!/usr/bin/env bash
-    npm run build
-    EOF
-    $ mise run build"#
-        after_long_help r#"Examples:
-
-    # Runs the "lint" tasks. This needs to either be defined in mise.toml
-    # or as a standalone script. See the project README for more information.
-    $ mise run lint
-
-    # Forces the "build" tasks to run even if its sources are up-to-date.
-    $ mise run build --force
-
-    # Run "test" with stdin/stdout/stderr all connected to the current terminal.
-    # This forces `--jobs=1` to prevent interleaving of output.
-    $ mise run test --raw
-
-    # Runs the "lint", "test", and "check" tasks in parallel.
-    $ mise run lint ::: test ::: check
-
-    # Execute multiple tasks each with their own arguments.
-    $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2
-"#
+    cmd run help="Run task(s)" {
+        alias r
+        long_help "Run task(s)\n\nThis command will run a tasks, or multiple tasks in parallel.\nTasks may have dependencies on other tasks or on source files.\nIf source is configured on a tasks, it will only run if the source\nfiles have changed.\n\nTasks can be defined in mise.toml or as standalone scripts.\nIn mise.toml, tasks take this form:\n\n    [tasks.build]\n    run = \"npm run build\"\n    sources = [\"src/**/*.ts\"]\n    outputs = [\"dist/**/*.js\"]\n\nAlternatively, tasks can be defined as standalone scripts.\nThese must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or\n`.config/mise/tasks`.\nThe name of the script will be the name of the tasks.\n\n    $ cat .mise/tasks/build<<EOF\n    #!/usr/bin/env bash\n    npm run build\n    EOF\n    $ mise run build"
+        after_long_help "Examples:\n\n    # Runs the \"lint\" tasks. This needs to either be defined in mise.toml\n    # or as a standalone script. See the project README for more information.\n    $ mise run lint\n\n    # Forces the \"build\" tasks to run even if its sources are up-to-date.\n    $ mise run build --force\n\n    # Run \"test\" with stdin/stdout/stderr all connected to the current terminal.\n    # This forces `--jobs=1` to prevent interleaving of output.\n    $ mise run test --raw\n\n    # Runs the \"lint\", \"test\", and \"check\" tasks in parallel.\n    $ mise run lint ::: test ::: check\n\n    # Execute multiple tasks each with their own arguments.\n    $ mise tasks cmd1 arg1 arg2 ::: cmd2 arg1 arg2\n"
         flag "-C --cd" help="Change to this directory before executing the command" {
-            arg "<CD>"
+            arg <CD>
         }
+        flag "-c --continue-on-error" help="Continue running tasks even if one fails"
         flag "-n --dry-run" help="Don't actually run the tasks(s), just print them in order of execution"
         flag "-f --force" help="Force the tasks to run even if outputs are up to date"
-        flag "-p --prefix" help="Print stdout/stderr by line, prefixed with the tasks's label\nDefaults to true if --jobs > 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var"
-        flag "-i --interleave" help="Print directly to stdout/stderr instead of by line\nDefaults to true if --jobs == 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var"
-        flag "-t --tool" help="Tool(s) to also add e.g.: node@20 python@3.10" var=true {
-            arg "<TOOL@VERSION>"
+        flag "-p --prefix" help="Print stdout/stderr by line, prefixed with the task's label\nDefaults to true if --jobs > 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var" hide=#true
+        flag "-i --interleave" help="Print directly to stdout/stderr instead of by line\nDefaults to true if --jobs == 1\nConfigure with `task_output` config or `MISE_TASK_OUTPUT` env var" hide=#true
+        flag "-s --shell" help="Shell to use to run toml tasks" {
+            long_help "Shell to use to run toml tasks\n\nDefaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows\nCan also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS`\nOr it can be overridden with the `shell` property on a task."
+            arg <SHELL>
+        }
+        flag "-t --tool" help="Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10" var=#true {
+            arg <TOOL@VERSION>
         }
         flag "-j --jobs" help="Number of tasks to run in parallel\n[default: 4]\nConfigure with `jobs` config or `MISE_JOBS` env var" {
-            arg "<JOBS>"
+            arg <JOBS>
         }
         flag "-r --raw" help="Read/write directly to stdin/stdout/stderr instead of by line\nConfigure with `raw` config or `MISE_RAW` env var"
-        flag "--timings" help="Shows elapsed time after each tasks"
-        arg "[TASK]" help="Tasks to run\nCan specify multiple tasks by separating with `:::`\ne.g.: mise run task1 arg1 arg2 ::: task2 arg1 arg2" default="default"
-        arg "[ARGS]..." help="Arguments to pass to the tasks. Use \":::\" to separate tasks" var=true
+        flag --timings help="Shows elapsed time after each task completes" hide=#true {
+            long_help "Shows elapsed time after each task completes\n\nDefault to always show with `MISE_TASK_TIMINGS=1`"
+        }
+        flag --no-timings help="Hides elapsed time after each task completes" {
+            long_help "Hides elapsed time after each task completes\n\nDefault to always hide with `MISE_TASK_TIMINGS=0`"
+        }
+        flag "-q --quiet" help="Don't show extra output"
+        flag "-S --silent" help="Don't show any output except for errors"
+        flag "-o --output" help="Change how tasks information is output when running tasks" {
+            long_help "Change how tasks information is output when running tasks\n\n- `prefix` - Print stdout/stderr by line, prefixed with the task's label\n- `interleave` - Print directly to stdout/stderr instead of by line\n- `replacing` - Stdout is replaced each time, stderr is printed as is\n- `timed` - Only show stdout lines if they are displayed for more than 1 second\n- `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output\n- `quiet` - Don't show extra output\n- `silent` - Don't show any output including stdout and stderr from the task except for errors"
+            arg <OUTPUT>
+        }
+        arg "[TASK]" help="Tasks to run\nCan specify multiple tasks by separating with `:::`\ne.g.: mise run task1 arg1 arg2 ::: task2 arg1 arg2" required=#false default=default
+        arg "[ARGS]..." help="Arguments to pass to the tasks. Use \":::\" to separate tasks" required=#false var=#true
+        arg "[-- ARGS_LAST]..." help="Arguments to pass to the tasks. Use \":::\" to separate tasks" required=#false var=#true hide=#true
+        mount run="mise tasks --usage"
     }
 }
-cmd "trust" help="Marks a config file as trusted" {
-    long_help r"Marks a config file as trusted
-
-This means mise will parse the file with potentially dangerous
-features enabled.
-
-This includes:
-- environment variables
-- templates
-- `path:` plugin versions"
-    after_long_help r"Examples:
-
-    # trusts ~/some_dir/mise.toml
-    $ mise trust ~/some_dir/mise.toml
-
-    # trusts mise.toml in the current or parent directory
-    $ mise trust
-"
+cmd test-tool hide=#true help="Test a tool installs and executes" {
+    after_long_help "Examples:\n\n    $ mise test-tool ripgrep\n"
+    flag "-a --all"
+    flag --include-non-defined help="Also test tools not defined in registry.toml, guessing how to test it"
+    flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
+        arg <JOBS>
+    }
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
+    arg "[TOOL]" required=#false
+}
+cmd tool help="Gets information about a tool" {
+    after_long_help "Examples:\n\n    $ mise tool node\n    Backend:            core\n    Installed Versions: 20.0.0 22.0.0\n    Active Version:     20.0.0\n    Requested Version:  20\n    Config Source:      ~/.config/mise/mise.toml\n    Tool Options:       [none]\n"
+    flag "-J --json" help="Output in JSON format"
+    flag --backend help="Only show backend field"
+    flag --description help="Only show description field"
+    flag --installed help="Only show installed versions"
+    flag --active help="Only show active versions"
+    flag --requested help="Only show requested versions"
+    flag --config-source help="Only show config source"
+    flag --tool-options help="Only show tool options"
+    arg <TOOL> help="Tool name to get information about"
+}
+cmd trust help="Marks a config file as trusted" {
+    long_help "Marks a config file as trusted\n\nThis means mise will parse the file with potentially dangerous\nfeatures enabled.\n\nThis includes:\n- environment variables\n- templates\n- `path:` plugin versions"
+    after_long_help "Examples:\n\n    # trusts ~/some_dir/mise.toml\n    $ mise trust ~/some_dir/mise.toml\n\n    # trusts mise.toml in the current or parent directory\n    $ mise trust\n"
     flag "-a --all" help="Trust all config files in the current directory and its parents"
-    flag "--untrust" help="No longer trust this config"
-    flag "--show" help="Show the trusted status of config files from the current directory and its parents.\nDoes not trust or untrust any files."
-    arg "[CONFIG_FILE]" help="The config file to trust"
+    flag --ignore help="Do not trust this config and ignore it in the future"
+    flag --untrust help="No longer trust this config, will prompt in the future"
+    flag --show help="Show the trusted status of config files from the current directory and its parents.\nDoes not trust or untrust any files."
+    arg "[CONFIG_FILE]" help="The config file to trust" required=#false
 }
-cmd "uninstall" help="Removes installed tool versions" {
-    alias "remove" "rm"
-    long_help r"Removes installed tool versions
-
-This only removes the installed version, it does not modify mise.toml."
-    after_long_help r"Examples:
-
-    # will uninstall specific version
-    $ mise uninstall node@18.0.0
-
-    # will uninstall the current node version (if only one version is installed)
-    $ mise uninstall node
-
-    # will uninstall all installed versions of node
-    $ mise uninstall --all node@18.0.0 # will uninstall all node versions
-"
+cmd uninstall help="Removes installed tool versions" {
+    long_help "Removes installed tool versions\n\nThis only removes the installed version, it does not modify mise.toml."
+    after_long_help "Examples:\n\n    # will uninstall specific version\n    $ mise uninstall node@18.0.0\n\n    # will uninstall the current node version (if only one version is installed)\n    $ mise uninstall node\n\n    # will uninstall all installed versions of node\n    $ mise uninstall --all node@18.0.0 # will uninstall all node versions\n"
     flag "-a --all" help="Delete all installed versions"
     flag "-n --dry-run" help="Do not actually delete anything"
-    arg "[INSTALLED_TOOL@VERSION]..." help="Tool(s) to remove" var=true
+    arg "[INSTALLED_TOOL@VERSION]..." help="Tool(s) to remove" required=#false var=#true
 }
-cmd "unset" help="Remove environment variable(s) from the config file." {
-    long_help r"Remove environment variable(s) from the config file.
-
-By default, this command modifies `mise.toml` in the current directory."
-    after_long_help r"Examples:
-
-    # Remove NODE_ENV from the current directory's config
-    $ mise unset NODE_ENV
-
-    # Remove NODE_ENV from the global config
-    $ mise unset NODE_ENV -g
-"
+cmd unset help="Remove environment variable(s) from the config file." {
+    long_help "Remove environment variable(s) from the config file.\n\nBy default, this command modifies `mise.toml` in the current directory."
+    after_long_help "Examples:\n\n    # Remove NODE_ENV from the current directory's config\n    $ mise unset NODE_ENV\n\n    # Remove NODE_ENV from the global config\n    $ mise unset NODE_ENV -g\n"
     flag "-f --file" help="Specify a file to use instead of `mise.toml`" {
-        arg "<FILE>"
+        arg <FILE>
     }
     flag "-g --global" help="Use the global config file"
-    arg "[KEYS]..." help="Environment variable(s) to remove\ne.g.: NODE_ENV" var=true
+    arg "[ENV_KEY]..." help="Environment variable(s) to remove\ne.g.: NODE_ENV" required=#false var=#true
 }
-cmd "upgrade" help="Upgrades outdated tools" {
-    alias "up"
-    long_help r"Upgrades outdated tools
-
-By default, this keeps the range specified in mise.toml. So if you have node@20 set, it will
-upgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version
-and bump the version in mise.toml."
-    after_long_help r"Examples:
-
-    # Upgrades node to the latest version matching the range in mise.toml
-    $ mise upgrade node
-
-    # Upgrades node to the latest version and bumps the version in mise.toml
-    $ mise upgrade node --bump
-
-    # Upgrades all tools to the latest versions
-    $ mise upgrade
-
-    # Upgrades all tools to the latest versions and bumps the version in mise.toml
-    $ mise upgrade --bump
-
-    # Just print what would be done, don't actually do it
-    $ mise upgrade --dry-run
-
-    # Upgrades node and python to the latest versions
-    $ mise upgrade node python
-
-    # Show a multiselect menu to choose which tools to upgrade
-    $ mise upgrade --interactive
-"
+cmd unuse help="Removes installed tool versions from mise.toml" {
+    alias rm remove
+    long_help "Removes installed tool versions from mise.toml\n\nWill also prune the installed version if no other configurations are using it."
+    after_long_help "Examples:\n\n    # will uninstall specific version\n    $ mise remove node@18.0.0\n"
+    flag --no-prune help="Do not also prune the installed version"
+    flag --global help="Remove tool from global config"
+    arg <INSTALLED_TOOL@VERSION>... help="Tool(s) to remove" var=#true
+}
+cmd upgrade help="Upgrades outdated tools" {
+    alias up
+    long_help "Upgrades outdated tools\n\nBy default, this keeps the range specified in mise.toml. So if you have node@20 set, it will\nupgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version\nand bump the version in mise.toml.\n\nThis will update mise.lock if it is enabled, see https://mise.jdx.dev/configuration/settings.html#lockfile"
+    after_long_help "Examples:\n\n    # Upgrades node to the latest version matching the range in mise.toml\n    $ mise upgrade node\n\n    # Upgrades node to the latest version and bumps the version in mise.toml\n    $ mise upgrade node --bump\n\n    # Upgrades all tools to the latest versions\n    $ mise upgrade\n\n    # Upgrades all tools to the latest versions and bumps the version in mise.toml\n    $ mise upgrade --bump\n\n    # Just print what would be done, don't actually do it\n    $ mise upgrade --dry-run\n\n    # Upgrades node and python to the latest versions\n    $ mise upgrade node python\n\n    # Show a multiselect menu to choose which tools to upgrade\n    $ mise upgrade --interactive\n"
     flag "-n --dry-run" help="Just print what would be done, don't actually do it"
     flag "-i --interactive" help="Display multiselect menu to choose which tools to upgrade"
     flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
     flag "-l --bump" help="Upgrades to the latest version available, bumping the version in mise.toml" {
         long_help "Upgrades to the latest version available, bumping the version in mise.toml\n\nFor example, if you have `node = \"20.0.0\"` in your mise.toml but 22.1.0 is the latest available,\nthis will install 22.1.0 and set `node = \"22.1.0\"` in your config.\n\nIt keeps the same precision as what was there before, so if you instead had `node = \"20\"`, it\nwould change your config to `node = \"22\"`."
     }
-    flag "--raw" help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
-    arg "[TOOL@VERSION]..." help="Tool(s) to upgrade\ne.g.: node@20 python@3.10\nIf not specified, all current tools will be upgraded" var=true
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets --jobs=1"
+    arg "[TOOL@VERSION]..." help="Tool(s) to upgrade\ne.g.: node@20 python@3.10\nIf not specified, all current tools will be upgraded" required=#false var=#true
 }
-cmd "usage" hide=true help="Generate a usage CLI spec" {
-    long_help r"Generate a usage CLI spec
-
-See https://usage.jdx.dev for more information on this specification."
+cmd usage hide=#true help="Generate a usage CLI spec" {
+    long_help "Generate a usage CLI spec\n\nSee https://usage.jdx.dev for more information on this specification."
 }
-cmd "use" help="Installs a tool and adds the version it to mise.toml." {
-    alias "u"
-    long_help r"Installs a tool and adds the version it to mise.toml.
-
-This will install the tool version if it is not already installed.
-By default, this will use a `mise.toml` file in the current directory.
-
-Use the `--global` flag to use the global config file instead."
-    after_long_help r"Examples:
-
-    # set the current version of node to 20.x in mise.toml of current directory
-    # will write the fuzzy version (e.g.: 20)
-    $ mise use node@20
-
-    # set the current version of node to 20.x in ~/.config/mise/config.toml
-    # will write the precise version (e.g.: 20.0.0)
-    $ mise use -g --pin node@20
-
-    # sets .mise.local.toml (which is intended not to be committed to a project)
-    $ mise use --env local node@20
-
-    # sets .mise.staging.toml (which is used if MISE_ENV=staging)
-    $ mise use --env staging node@20
-"
+cmd use help="Installs a tool and adds the version to mise.toml." {
+    alias u
+    long_help "Installs a tool and adds the version to mise.toml.\n\nThis will install the tool version if it is not already installed.\nBy default, this will use a `mise.toml` file in the current directory.\n\nIn the following order:\n  - If `MISE_DEFAULT_CONFIG_FILENAME` is set, it will use that instead.\n  - If `MISE_OVERRIDE_CONFIG_FILENAMES` is set, it will the first from that list.\n  - If `MISE_ENV` is set, it will use a `mise.<env>.toml` instead.\n  - Otherwise just \"mise.toml\"\n\nUse the `--global` flag to use the global config file instead."
+    after_long_help "Examples:\n    \n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n    $ mise use node@20\n\n    # set the current version of node to 20.x in ~/.config/mise/config.toml\n    # will write the precise version (e.g.: 20.0.0)\n    $ mise use -g --pin node@20\n\n    # sets .mise.local.toml (which is intended not to be committed to a project)\n    $ mise use --env local node@20\n\n    # sets .mise.staging.toml (which is used if MISE_ENV=staging)\n    $ mise use --env staging node@20\n"
     flag "-f --force" help="Force reinstall even if already installed"
-    flag "--fuzzy" help="Save fuzzy version to config file" {
-        long_help "Save fuzzy version to config file\n\ne.g.: `mise use --fuzzy node@20` will save 20 as the version\nthis is the default behavior unless `MISE_PIN=1` or `MISE_ASDF_COMPAT=1`"
+    flag --fuzzy help="Save fuzzy version to config file" {
+        long_help "Save fuzzy version to config file\n\ne.g.: `mise use --fuzzy node@20` will save 20 as the version\nthis is the default behavior unless `MISE_PIN=1`"
     }
     flag "-g --global" help="Use the global config file (`~/.config/mise/config.toml`) instead of the local one"
-    flag "-e --env" help="Modify an environment-specific config file like .mise.<env>.toml" {
-        arg "<ENV>"
+    flag "-e --env" help="Create/modify an environment-specific config file like .mise.<env>.toml" {
+        arg <ENV>
     }
     flag "-j --jobs" help="Number of jobs to run in parallel\n[default: 4]" {
-        arg "<JOBS>"
+        arg <JOBS>
     }
-    flag "--raw" help="Directly pipe stdin/stdout/stderr from plugin to user Sets `--jobs=1`"
-    flag "--remove" help="Remove the plugin(s) from config file" var=true {
-        arg "<PLUGIN>"
+    flag --raw help="Directly pipe stdin/stdout/stderr from plugin to user Sets `--jobs=1`"
+    flag --remove help="Remove the plugin(s) from config file" var=#true {
+        arg <PLUGIN>
     }
     flag "-p --path" help="Specify a path to a config file or directory" {
-        long_help "Specify a path to a config file or directory\n\nIf a directory is specified, it will look for `mise.toml` (default) or `.tool-versions` if `MISE_ASDF_COMPAT=1`"
-        arg "<PATH>"
+        long_help "Specify a path to a config file or directory\n\nIf a directory is specified, it will look for a config file in that directory following the rules above."
+        arg <PATH>
     }
-    flag "--pin" help="Save exact version to config file\ne.g.: `mise use --pin node@20` will save 20.0.0 as the version\nSet `MISE_PIN=1` or `MISE_ASDF_COMPAT=1` to make this the default behavior"
-    arg "[TOOL@VERSION]..." help="Tool(s) to add to config file" help_long="Tool(s) to add to config file\n\ne.g.: node@20, cargo:ripgrep@latest npm:prettier@3\nIf no version is specified, it will default to @latest" var=true
+    flag --pin help="Save exact version to config file\ne.g.: `mise use --pin node@20` will save 20.0.0 as the version\nSet `MISE_PIN=1` to make this the default behavior" {
+        long_help "Save exact version to config file\ne.g.: `mise use --pin node@20` will save 20.0.0 as the version\nSet `MISE_PIN=1` to make this the default behavior\n\nConsider using mise.lock as a better alternative to pinning in mise.toml:\nhttps://mise.jdx.dev/configuration/settings.html#lockfile"
+    }
+    arg "[TOOL@VERSION]..." help="Tool(s) to add to config file" help_long="Tool(s) to add to config file\n\ne.g.: node@20, cargo:ripgrep@latest npm:prettier@3\nIf no version is specified, it will default to @latest\n\nTool options can be set with this syntax:\n\n    mise use ubi:BurntSushi/ripgrep[exe=rg]" required=#false var=#true
 }
-cmd "version" help="Display the version of mise" {
-    alias "v"
-    long_help r"Display the version of mise
-
-Displays the version, os, architecture, and the date of the build.
-
-If the version is out of date, it will display a warning."
-    after_long_help r"Examples:
-
-    $ mise version
-    $ mise --version
-    $ mise -v
-    $ mise -V
-"
-}
-cmd "watch" help="[experimental] Run task(s) and watch for changes to rerun it" {
-    alias "w"
-    long_help r"[experimental] Run task(s) and watch for changes to rerun it
-
-This command uses the `watchexec` tool to watch for changes to files and rerun the specified task(s).
-It must be installed for this command to work, but you can install it with `mise use -g watchexec@latest`."
-    after_long_help r#"Examples:
-    
-    $ mise watch -t build
-    Runs the "build" tasks. Will re-run the tasks when any of its sources change.
-    Uses "sources" from the tasks definition to determine which files to watch.
-
-    $ mise watch -t build --glob src/**/*.rs
-    Runs the "build" tasks but specify the files to watch with a glob pattern.
-    This overrides the "sources" from the tasks definition.
-
-    $ mise run -t build --clear
-    Extra arguments are passed to watchexec. See `watchexec --help` for details.
-"#
-    flag "-t --task" help="Tasks to run" var=true {
-        arg "<TASK>"
+cmd version help="Display the version of mise" {
+    alias v
+    long_help "Display the version of mise\n\nDisplays the version, os, architecture, and the date of the build.\n\nIf the version is out of date, it will display a warning."
+    after_long_help "Examples:\n\n    $ mise version\n    $ mise --version\n    $ mise -v\n    $ mise -V\n"
+}
+cmd watch help="Run task(s) and watch for changes to rerun it" {
+    alias w
+    long_help "Run task(s) and watch for changes to rerun it\n\nThis command uses the `watchexec` tool to watch for changes to files and rerun the specified task(s).\nIt must be installed for this command to work, but you can install it with `mise use -g watchexec@latest`."
+    after_long_help "Examples:\n\n    $ mise watch build\n    Runs the \"build\" tasks. Will re-run the tasks when any of its sources change.\n    Uses \"sources\" from the tasks definition to determine which files to watch.\n\n    $ mise watch build --glob src/**/*.rs\n    Runs the \"build\" tasks but specify the files to watch with a glob pattern.\n    This overrides the \"sources\" from the tasks definition.\n\n    $ mise watch build --clear\n    Extra arguments are passed to watchexec. See `watchexec --help` for details.\n\n    $ mise watch serve --watch src --exts rs --restart\n    Starts an api server, watching for changes to \"*.rs\" files in \"./src\" and kills/restarts the server when they change.\n"
+    flag "-t --task-flag" help="Tasks to run" var=#true hide=#true {
+        arg <TASK_FLAG>
+    }
+    flag "-g --glob" help="Files to watch\nDefaults to sources from the tasks(s)" var=#true hide=#true {
+        arg <GLOB>
+    }
+    flag "-w --watch" help="Watch a specific file or directory" var=#true {
+        long_help "Watch a specific file or directory\n\nBy default, Watchexec watches the current directory.\n\nWhen watching a single file, it's often better to watch the containing directory instead, and filter on the filename. Some editors may replace the file with a new one when saving, and some platforms may not detect that or further changes.\n\nUpon starting, Watchexec resolves a \"project origin\" from the watched paths. See the help for '--project-origin' for more information.\n\nThis option can be specified multiple times to watch multiple files or directories.\n\nThe special value '/dev/null', provided as the only path watched, will cause Watchexec to not watch any paths. Other event sources (like signals or key events) may still be used."
+        arg <PATH>
+    }
+    flag "-W --watch-non-recursive" help="Watch a specific directory, non-recursively" var=#true {
+        long_help "Watch a specific directory, non-recursively\n\nUnlike '-w', folders watched with this option are not recursed into.\n\nThis option can be specified multiple times to watch multiple directories non-recursively."
+        arg <PATH>
+    }
+    flag "-F --watch-file" help="Watch files and directories from a file" {
+        long_help "Watch files and directories from a file\n\nEach line in the file will be interpreted as if given to '-w'.\n\nFor more complex uses (like watching non-recursively), use the argfile capability: build a file containing command-line options and pass it to watchexec with `@path/to/argfile`.\n\nThe special value '-' will read from STDIN; this in incompatible with '--stdin-quit'."
+        arg <PATH>
+    }
+    flag "-c --clear" help="Clear screen before running command" {
+        long_help "Clear screen before running command\n\nIf this doesn't completely clear the screen, try '--clear=reset'."
+        arg <MODE> {
+            choices clear reset
+        }
+    }
+    flag "-o --on-busy-update" help="What to do when receiving events while the command is running" {
+        long_help "What to do when receiving events while the command is running\n\nDefault is to 'do-nothing', which ignores events while the command is running, so that changes that occur due to the command are ignored, like compilation outputs. You can also use 'queue' which will run the command once again when the current run has finished if any events occur while it's running, or 'restart', which terminates the running command and starts a new one. Finally, there's 'signal', which only sends a signal; this can be useful with programs that can reload their configuration without a full restart.\n\nThe signal can be specified with the '--signal' option."
+        arg <MODE> {
+            choices queue do-nothing restart signal
+        }
+    }
+    flag "-r --restart" help="Restart the process if it's still running" {
+        long_help "Restart the process if it's still running\n\nThis is a shorthand for '--on-busy-update=restart'."
+    }
+    flag "-s --signal" help="Send a signal to the process when it's still running" {
+        long_help "Send a signal to the process when it's still running\n\nSpecify a signal to send to the process when it's still running. This implies '--on-busy-update=signal'; otherwise the signal used when that mode is 'restart' is controlled by '--stop-signal'.\n\nSee the long documentation for '--stop-signal' for syntax.\n\nSignals are not supported on Windows at the moment, and will always be overridden to 'kill'. See '--stop-signal' for more on Windows \"signals\"."
+        arg <SIGNAL>
+    }
+    flag --stop-signal help="Signal to send to stop the command" {
+        long_help "Signal to send to stop the command\n\nThis is used by 'restart' and 'signal' modes of '--on-busy-update' (unless '--signal' is provided). The restart behaviour is to send the signal, wait for the command to exit, and if it hasn't exited after some time (see '--timeout-stop'), forcefully terminate it.\n\nThe default on unix is \"SIGTERM\".\n\nInput is parsed as a full signal name (like \"SIGTERM\"), a short signal name (like \"TERM\"), or a signal number (like \"15\"). All input is case-insensitive.\n\nOn Windows this option is technically supported but only supports the \"KILL\" event, as Watchexec cannot yet deliver other events. Windows doesn't have signals as such; instead it has termination (here called \"KILL\" or \"STOP\") and \"CTRL+C\", \"CTRL+BREAK\", and \"CTRL+CLOSE\" events. For portability the unix signals \"SIGKILL\", \"SIGINT\", \"SIGTERM\", and \"SIGHUP\" are respectively mapped to these."
+        arg <SIGNAL>
+    }
+    flag --stop-timeout help="Time to wait for the command to exit gracefully" {
+        long_help "Time to wait for the command to exit gracefully\n\nThis is used by the 'restart' mode of '--on-busy-update'. After the graceful stop signal is sent, Watchexec will wait for the command to exit. If it hasn't exited after this time, it is forcefully terminated.\n\nTakes a unit-less value in seconds, or a time span value such as \"5min 20s\". Providing a unit-less value is deprecated and will warn; it will be an error in the future.\n\nThe default is 10 seconds. Set to 0 to immediately force-kill the command.\n\nThis has no practical effect on Windows as the command is always forcefully terminated; see '--stop-signal' for why."
+        arg <TIMEOUT>
+    }
+    flag --map-signal help="Translate signals from the OS to signals to send to the command" var=#true {
+        long_help "Translate signals from the OS to signals to send to the command\n\nTakes a pair of signal names, separated by a colon, such as \"TERM:INT\" to map SIGTERM to SIGINT. The first signal is the one received by watchexec, and the second is the one sent to the command. The second can be omitted to discard the first signal, such as \"TERM:\" to not do anything on SIGTERM.\n\nIf SIGINT or SIGTERM are mapped, then they no longer quit Watchexec. Besides making it hard to quit Watchexec itself, this is useful to send pass a Ctrl-C to the command without also terminating Watchexec and the underlying program with it, e.g. with \"INT:INT\".\n\nThis option can be specified multiple times to map multiple signals.\n\nSignal syntax is case-insensitive for short names (like \"TERM\", \"USR2\") and long names (like \"SIGKILL\", \"SIGHUP\"). Signal numbers are also supported (like \"15\", \"31\"). On Windows, the forms \"STOP\", \"CTRL+C\", and \"CTRL+BREAK\" are also supported to receive, but Watchexec cannot yet deliver other \"signals\" than a STOP."
+        arg <SIGNAL:SIGNAL>
+    }
+    flag "-d --debounce" help="Time to wait for new events before taking action" {
+        long_help "Time to wait for new events before taking action\n\nWhen an event is received, Watchexec will wait for up to this amount of time before handling it (such as running the command). This is essential as what you might perceive as a single change may actually emit many events, and without this behaviour, Watchexec would run much too often. Additionally, it's not infrequent that file writes are not atomic, and each write may emit an event, so this is a good way to avoid running a command while a file is partially written.\n\nAn alternative use is to set a high value (like \"30min\" or longer), to save power or bandwidth on intensive tasks, like an ad-hoc backup script. In those use cases, note that every accumulated event will build up in memory.\n\nTakes a unit-less value in milliseconds, or a time span value such as \"5sec 20ms\". Providing a unit-less value is deprecated and will warn; it will be an error in the future.\n\nThe default is 50 milliseconds. Setting to 0 is highly discouraged."
+        arg <TIMEOUT>
+    }
+    flag --stdin-quit help="Exit when stdin closes" {
+        long_help "Exit when stdin closes\n\nThis watches the stdin file descriptor for EOF, and exits Watchexec gracefully when it is closed. This is used by some process managers to avoid leaving zombie processes around."
+    }
+    flag --no-vcs-ignore help="Don't load gitignores" {
+        long_help "Don't load gitignores\n\nAmong other VCS exclude files, like for Mercurial, Subversion, Bazaar, DARCS, Fossil. Note that Watchexec will detect which of these is in use, if any, and only load the relevant files. Both global (like '~/.gitignore') and local (like '.gitignore') files are considered.\n\nThis option is useful if you want to watch files that are ignored by Git."
+    }
+    flag --no-project-ignore help="Don't load project-local ignores" {
+        long_help "Don't load project-local ignores\n\nThis disables loading of project-local ignore files, like '.gitignore' or '.ignore' in the\nwatched project. This is contrasted with '--no-vcs-ignore', which disables loading of Git\nand other VCS ignore files, and with '--no-global-ignore', which disables loading of global\nor user ignore files, like '~/.gitignore' or '~/.config/watchexec/ignore'.\n\nSupported project ignore files:\n\n  - Git: .gitignore at project root and child directories, .git/info/exclude, and the file pointed to by `core.excludesFile` in .git/config.\n  - Mercurial: .hgignore at project root and child directories.\n  - Bazaar: .bzrignore at project root.\n  - Darcs: _darcs/prefs/boring\n  - Fossil: .fossil-settings/ignore-glob\n  - Ripgrep/Watchexec/generic: .ignore at project root and child directories.\n\nVCS ignore files (Git, Mercurial, Bazaar, Darcs, Fossil) are only used if the corresponding\nVCS is discovered to be in use for the project/origin. For example, a .bzrignore in a Git\nrepository will be discarded."
     }
-    flag "-g --glob" help="Files to watch\nDefaults to sources from the tasks(s)" var=true {
-        arg "<GLOB>"
+    flag --no-global-ignore help="Don't load global ignores" {
+        long_help "Don't load global ignores\n\nThis disables loading of global or user ignore files, like '~/.gitignore',\n'~/.config/watchexec/ignore', or '%APPDATA%\\Bazzar\\2.0\\ignore'. Contrast with\n'--no-vcs-ignore' and '--no-project-ignore'.\n\nSupported global ignore files\n\n  - Git (if core.excludesFile is set): the file at that path\n  - Git (otherwise): the first found of $XDG_CONFIG_HOME/git/ignore, %APPDATA%/.gitignore, %USERPROFILE%/.gitignore, $HOME/.config/git/ignore, $HOME/.gitignore.\n  - Bazaar: the first found of %APPDATA%/Bazzar/2.0/ignore, $HOME/.bazaar/ignore.\n  - Watchexec: the first found of $XDG_CONFIG_HOME/watchexec/ignore, %APPDATA%/watchexec/ignore, %USERPROFILE%/.watchexec/ignore, $HOME/.watchexec/ignore.\n\nLike for project files, Git and Bazaar global files will only be used for the corresponding\nVCS as used in the project."
     }
-    arg "[ARGS]..." help="Extra arguments" var=true
+    flag --no-default-ignore help="Don't use internal default ignores" {
+        long_help "Don't use internal default ignores\n\nWatchexec has a set of default ignore patterns, such as editor swap files, `*.pyc`, `*.pyo`, `.DS_Store`, `.bzr`, `_darcs`, `.fossil-settings`, `.git`, `.hg`, `.pijul`, `.svn`, and Watchexec log files."
+    }
+    flag --no-discover-ignore help="Don't discover ignore files at all" {
+        long_help "Don't discover ignore files at all\n\nThis is a shorthand for '--no-global-ignore', '--no-vcs-ignore', '--no-project-ignore', but even more efficient as it will skip all the ignore discovery mechanisms from the get go.\n\nNote that default ignores are still loaded, see '--no-default-ignore'."
+    }
+    flag --ignore-nothing help="Don't ignore anything at all" {
+        long_help "Don't ignore anything at all\n\nThis is a shorthand for '--no-discover-ignore', '--no-default-ignore'.\n\nNote that ignores explicitly loaded via other command line options, such as '--ignore' or '--ignore-file', will still be used."
+    }
+    flag "-p --postpone" help="Wait until first change before running command" {
+        long_help "Wait until first change before running command\n\nBy default, Watchexec will run the command once immediately. With this option, it will instead wait until an event is detected before running the command as normal."
+    }
+    flag --delay-run help="Sleep before running the command" {
+        long_help "Sleep before running the command\n\nThis option will cause Watchexec to sleep for the specified amount of time before running the command, after an event is detected. This is like using \"sleep 5 && command\" in a shell, but portable and slightly more efficient.\n\nTakes a unit-less value in seconds, or a time span value such as \"2min 5s\". Providing a unit-less value is deprecated and will warn; it will be an error in the future."
+        arg <DURATION>
+    }
+    flag --poll help="Poll for filesystem changes" {
+        long_help "Poll for filesystem changes\n\nBy default, and where available, Watchexec uses the operating system's native file system watching capabilities. This option disables that and instead uses a polling mechanism, which is less efficient but can work around issues with some file systems (like network shares) or edge cases.\n\nOptionally takes a unit-less value in milliseconds, or a time span value such as \"2s 500ms\", to use as the polling interval. If not specified, the default is 30 seconds. Providing a unit-less value is deprecated and will warn; it will be an error in the future.\n\nAliased as '--force-poll'."
+        arg <INTERVAL>
+    }
+    flag --shell help="Use a different shell" {
+        long_help "Use a different shell\n\nBy default, Watchexec will use '$SHELL' if it's defined or a default of 'sh' on Unix-likes, and either 'pwsh', 'powershell', or 'cmd' (CMD.EXE) on Windows, depending on what Watchexec detects is the running shell.\n\nWith this option, you can override that and use a different shell, for example one with more features or one which has your custom aliases and functions.\n\nIf the value has spaces, it is parsed as a command line, and the first word used as the shell program, with the rest as arguments to the shell.\n\nThe command is run with the '-c' flag (except for 'cmd' on Windows, where it's '/C').\n\nThe special value 'none' can be used to disable shell use entirely. In that case, the command provided to Watchexec will be parsed, with the first word being the executable and the rest being the arguments, and executed directly. Note that this parsing is rudimentary, and may not work as expected in all cases.\n\nUsing 'none' is a little more efficient and can enable a stricter interpretation of the input, but it also means that you can't use shell features like globbing, redirection, control flow, logic, or pipes.\n\nExamples:\n\nUse without shell:\n\n$ watchexec -n -- zsh -x -o shwordsplit scr\n\nUse with powershell core:\n\n$ watchexec --shell=pwsh -- Test-Connection localhost\n\nUse with CMD.exe:\n\n$ watchexec --shell=cmd -- dir\n\nUse with a different unix shell:\n\n$ watchexec --shell=bash -- 'echo $BASH_VERSION'\n\nUse with a unix shell and options:\n\n$ watchexec --shell='zsh -x -o shwordsplit' -- scr"
+        arg <SHELL>
+    }
+    flag -n help="Shorthand for '--shell=none'"
+    flag --emit-events-to help="Configure event emission" {
+        long_help "Configure event emission\n\nWatchexec can emit event information when running a command, which can be used by the child\nprocess to target specific changed files.\n\nOne thing to take care with is assuming inherent behaviour where there is only chance.\nNotably, it could appear as if the `RENAMED` variable contains both the original and the new\npath being renamed. In previous versions, it would even appear on some platforms as if the\noriginal always came before the new. However, none of this was true. It's impossible to\nreliably and portably know which changed path is the old or new, \"half\" renames may appear\n(only the original, only the new), \"unknown\" renames may appear (change was a rename, but\nwhether it was the old or new isn't known), rename events might split across two debouncing\nboundaries, and so on.\n\nThis option controls where that information is emitted. It defaults to 'none', which doesn't\nemit event information at all. The other options are 'environment' (deprecated), 'stdio',\n'file', 'json-stdio', and 'json-file'.\n\nThe 'stdio' and 'file' modes are text-based: 'stdio' writes absolute paths to the stdin of\nthe command, one per line, each prefixed with `create:`, `remove:`, `rename:`, `modify:`,\nor `other:`, then closes the handle; 'file' writes the same thing to a temporary file, and\nits path is given with the $WATCHEXEC_EVENTS_FILE environment variable.\n\nThere are also two JSON modes, which are based on JSON objects and can represent the full\nset of events Watchexec handles. Here's an example of a folder being created on Linux:\n\n```json\n  {\n    \"tags\": [\n      {\n        \"kind\": \"path\",\n        \"absolute\": \"/home/user/your/new-folder\",\n        \"filetype\": \"dir\"\n      },\n      {\n        \"kind\": \"fs\",\n        \"simple\": \"create\",\n        \"full\": \"Create(Folder)\"\n      },\n      {\n        \"kind\": \"source\",\n        \"source\": \"filesystem\",\n      }\n    ],\n    \"metadata\": {\n      \"notify-backend\": \"inotify\"\n    }\n  }\n```\n\nThe fields are as follows:\n\n  - `tags`, structured event data.\n  - `tags[].kind`, which can be:\n    * 'path', along with:\n      + `absolute`, an absolute path.\n      + `filetype`, a file type if known ('dir', 'file', 'symlink', 'other').\n    * 'fs':\n      + `simple`, the \"simple\" event type ('access', 'create', 'modify', 'remove', or 'other').\n      + `full`, the \"full\" event type, which is too complex to fully describe here, but looks like 'General(Precise(Specific))'.\n    * 'source', along with:\n      + `source`, the source of the event ('filesystem', 'keyboard', 'mouse', 'os', 'time', 'internal').\n    * 'keyboard', along with:\n      + `keycode`. Currently only the value 'eof' is supported.\n    * 'process', for events caused by processes:\n      + `pid`, the process ID.\n    * 'signal', for signals sent to Watchexec:\n      + `signal`, the normalised signal name ('hangup', 'interrupt', 'quit', 'terminate', 'user1', 'user2').\n    * 'completion', for when a command ends:\n      + `disposition`, the exit disposition ('success', 'error', 'signal', 'stop', 'exception', 'continued').\n      + `code`, the exit, signal, stop, or exception code.\n  - `metadata`, additional information about the event.\n\nThe 'json-stdio' mode will emit JSON events to the standard input of the command, one per\nline, then close stdin. The 'json-file' mode will create a temporary file, write the\nevents to it, and provide the path to the file with the $WATCHEXEC_EVENTS_FILE\nenvironment variable.\n\nFinally, the 'environment' mode was the default until 2.0. It sets environment variables\nwith the paths of the affected files, for filesystem events:\n\n$WATCHEXEC_COMMON_PATH is set to the longest common path of all of the below variables,\nand so should be prepended to each path to obtain the full/real path. Then:\n\n  - $WATCHEXEC_CREATED_PATH is set when files/folders were created\n  - $WATCHEXEC_REMOVED_PATH is set when files/folders were removed\n  - $WATCHEXEC_RENAMED_PATH is set when files/folders were renamed\n  - $WATCHEXEC_WRITTEN_PATH is set when files/folders were modified\n  - $WATCHEXEC_META_CHANGED_PATH is set when files/folders' metadata were modified\n  - $WATCHEXEC_OTHERWISE_CHANGED_PATH is set for every other kind of pathed event\n\nMultiple paths are separated by the system path separator, ';' on Windows and ':' on unix.\nWithin each variable, paths are deduplicated and sorted in binary order (i.e. neither\nUnicode nor locale aware).\n\nThis is the legacy mode, is deprecated, and will be removed in the future. The environment\nis a very restricted space, while also limited in what it can usefully represent. Large\nnumbers of files will either cause the environment to be truncated, or may error or crash\nthe process entirely. The $WATCHEXEC_COMMON_PATH is also unintuitive, as demonstrated by the\nmultiple confused queries that have landed in my inbox over the years."
+        arg <MODE> {
+            choices environment stdio file json-stdio json-file none
+        }
+    }
+    flag --only-emit-events help="Only emit events to stdout, run no commands" {
+        long_help "Only emit events to stdout, run no commands.\n\nThis is a convenience option for using Watchexec as a file watcher, without running any commands. It is almost equivalent to using `cat` as the command, except that it will not spawn a new process for each event.\n\nThis option requires `--emit-events-to` to be set, and restricts the available modes to `stdio` and `json-stdio`, modifying their behaviour to write to stdout instead of the stdin of the command."
+    }
+    flag "-E --env" help="Add env vars to the command" var=#true {
+        long_help "Add env vars to the command\n\nThis is a convenience option for setting environment variables for the command, without setting them for the Watchexec process itself.\n\nUse key=value syntax. Multiple variables can be set by repeating the option."
+        arg "<KEY=VALUE>"
+    }
+    flag --wrap-process help="Configure how the process is wrapped" {
+        long_help "Configure how the process is wrapped\n\nBy default, Watchexec will run the command in a process group in Unix, and in a Job Object in Windows.\n\nSome Unix programs prefer running in a session, while others do not work in a process group.\n\nUse 'group' to use a process group, 'session' to use a process session, and 'none' to run the command directly. On Windows, either of 'group' or 'session' will use a Job Object."
+        arg <MODE> {
+            choices group session none
+        }
+    }
+    flag "-N --notify" help="Alert when commands start and end" {
+        long_help "Alert when commands start and end\n\nWith this, Watchexec will emit a desktop notification when a command starts and ends, on supported platforms. On unsupported platforms, it may silently do nothing, or log a warning."
+    }
+    flag --color help="When to use terminal colours" {
+        long_help "When to use terminal colours\n\nSetting the environment variable `NO_COLOR` to any value is equivalent to `--color=never`."
+        arg <MODE> {
+            choices auto always never
+        }
+    }
+    flag --timings help="Print how long the command took to run" {
+        long_help "Print how long the command took to run\n\nThis may not be exactly accurate, as it includes some overhead from Watchexec itself. Use the `time` utility, high-precision timers, or benchmarking tools for more accurate results."
+    }
+    flag "-q --quiet" help="Don't print starting and stopping messages" {
+        long_help "Don't print starting and stopping messages\n\nBy default Watchexec will print a message when the command starts and stops. This option disables this behaviour, so only the command's output, warnings, and errors will be printed."
+    }
+    flag --bell help="Ring the terminal bell on command completion"
+    flag --project-origin help="Set the project origin" {
+        long_help "Set the project origin\n\nWatchexec will attempt to discover the project's \"origin\" (or \"root\") by searching for a variety of markers, like files or directory patterns. It does its best but sometimes gets it it wrong, and you can override that with this option.\n\nThe project origin is used to determine the path of certain ignore files, which VCS is being used, the meaning of a leading '/' in filtering patterns, and maybe more in the future.\n\nWhen set, Watchexec will also not bother searching, which can be significantly faster."
+        arg <DIRECTORY>
+    }
+    flag --workdir help="Set the working directory" {
+        long_help "Set the working directory\n\nBy default, the working directory of the command is the working directory of Watchexec. You can change that with this option. Note that paths may be less intuitive to use with this."
+        arg <DIRECTORY>
+    }
+    flag "-e --exts" help="Filename extensions to filter to" var=#true {
+        long_help "Filename extensions to filter to\n\nThis is a quick filter to only emit events for files with the given extensions. Extensions can be given with or without the leading dot (e.g. 'js' or '.js'). Multiple extensions can be given by repeating the option or by separating them with commas."
+        arg <EXTENSIONS>
+    }
+    flag "-f --filter" help="Filename patterns to filter to" var=#true {
+        long_help "Filename patterns to filter to\n\nProvide a glob-like filter pattern, and only events for files matching the pattern will be emitted. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched."
+        arg <PATTERN>
+    }
+    flag --filter-file help="Files to load filters from" var=#true {
+        long_help "Files to load filters from\n\nProvide a path to a file containing filters, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--filter' option.\n\nThis can also be used via the $WATCHEXEC_FILTER_FILES environment variable."
+        arg <PATH>
+    }
+    flag "-J --filter-prog" help="[experimental] Filter programs" var=#true {
+        long_help "[experimental] Filter programs.\n\n/!\\ This option is EXPERIMENTAL and may change and/or vanish without notice.\n\nProvide your own custom filter programs in jaq (similar to jq) syntax. Programs are given an event in the same format as described in '--emit-events-to' and must return a boolean. Invalid programs will make watchexec fail to start; use '-v' to see program runtime errors.\n\nIn addition to the jaq stdlib, watchexec adds some custom filter definitions:\n\n- 'path | file_meta' returns file metadata or null if the file does not exist.\n\n- 'path | file_size' returns the size of the file at path, or null if it does not exist.\n\n- 'path | file_read(bytes)' returns a string with the first n bytes of the file at path. If the file is smaller than n bytes, the whole file is returned. There is no filter to read the whole file at once to encourage limiting the amount of data read and processed.\n\n- 'string | hash', and 'path | file_hash' return the hash of the string or file at path. No guarantee is made about the algorithm used: treat it as an opaque value.\n\n- 'any | kv_store(key)', 'kv_fetch(key)', and 'kv_clear' provide a simple key-value store. Data is kept in memory only, there is no persistence. Consistency is not guaranteed.\n\n- 'any | printout', 'any | printerr', and 'any | log(level)' will print or log any given value to stdout, stderr, or the log (levels = error, warn, info, debug, trace), and pass the value through (so '[1] | log(\"debug\") | .[]' will produce a '1' and log '[1]').\n\nAll filtering done with such programs, and especially those using kv or filesystem access, is much slower than the other filtering methods. If filtering is too slow, events will back up and stall watchexec. Take care when designing your filters.\n\nIf the argument to this option starts with an '@', the rest of the argument is taken to be the path to a file containing a jaq program.\n\nJaq programs are run in order, after all other filters, and short-circuit: if a filter (jaq or not) rejects an event, execution stops there, and no other filters are run. Additionally, they stop after outputting the first value, so you'll want to use 'any' or 'all' when iterating, otherwise only the first item will be processed, which can be quite confusing!\n\nFind user-contributed programs or submit your own useful ones at <https://github.com/watchexec/watchexec/discussions/592>.\n\n## Examples:\n\nRegexp ignore filter on paths:\n\n'all(.tags[] | select(.kind == \"path\"); .absolute | test(\"[.]test[.]js$\")) | not'\n\nPass any event that creates a file:\n\n'any(.tags[] | select(.kind == \"fs\"); .simple == \"create\")'\n\nPass events that touch executable files:\n\n'any(.tags[] | select(.kind == \"path\" && .filetype == \"file\"); .absolute | metadata | .executable)'\n\nIgnore files that start with shebangs:\n\n'any(.tags[] | select(.kind == \"path\" && .filetype == \"file\"); .absolute | read(2) == \"#!\") | not'"
+        arg <EXPRESSION>
+    }
+    flag "-i --ignore" help="Filename patterns to filter out" var=#true {
+        long_help "Filename patterns to filter out\n\nProvide a glob-like filter pattern, and events for files matching the pattern will be excluded. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched."
+        arg <PATTERN>
+    }
+    flag --ignore-file help="Files to load ignores from" var=#true {
+        long_help "Files to load ignores from\n\nProvide a path to a file containing ignores, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--ignore' option.\n\nThis can also be used via the $WATCHEXEC_IGNORE_FILES environment variable."
+        arg <PATH>
+    }
+    flag --fs-events help="Filesystem events to filter to" var=#true {
+        long_help "Filesystem events to filter to\n\nThis is a quick filter to only emit events for the given types of filesystem changes. Choose from 'access', 'create', 'remove', 'rename', 'modify', 'metadata'. Multiple types can be given by repeating the option or by separating them with commas. By default, this is all types except for 'access'.\n\nThis may apply filtering at the kernel level when possible, which can be more efficient, but may be more confusing when reading the logs."
+        arg <EVENTS> {
+            choices access create remove rename modify metadata
+        }
+    }
+    flag --no-meta help="Don't emit fs events for metadata changes" {
+        long_help "Don't emit fs events for metadata changes\n\nThis is a shorthand for '--fs-events create,remove,rename,modify'. Using it alongside the '--fs-events' option is non-sensical and not allowed."
+    }
+    flag --print-events help="Print events that trigger actions" {
+        long_help "Print events that trigger actions\n\nThis prints the events that triggered the action when handling it (after debouncing), in a human readable form. This is useful for debugging filters.\n\nUse '-vvv' instead when you need more diagnostic information."
+    }
+    flag --manual help="Show the manual page" {
+        long_help "Show the manual page\n\nThis shows the manual page for Watchexec, if the output is a terminal and the 'man' program is available. If not, the manual page is printed to stdout in ROFF format (suitable for writing to a watchexec.1 file)."
+    }
+    arg "[TASK]" help="Tasks to run\nCan specify multiple tasks by separating with `:::`\ne.g.: `mise run task1 arg1 arg2 ::: task2 arg1 arg2`" required=#false
+    arg "[ARGS]..." help="Task and arguments to run" required=#false double_dash=automatic var=#true
 }
-cmd "where" help="Display the installation path for a tool" {
-    long_help r"Display the installation path for a tool
-
-The tool must be installed for this to work."
-    after_long_help r"Examples:
-
-    # Show the latest installed version of node
-    # If it is is not installed, errors
-    $ mise where node@20
-    /home/jdx/.local/share/mise/installs/node/20.0.0
-
-    # Show the current, active install directory of node
-    # Errors if node is not referenced in any .tool-version file
-    $ mise where node
-    /home/jdx/.local/share/mise/installs/node/20.0.0
-"
-    arg "<TOOL@VERSION>" help="Tool(s) to look up\ne.g.: ruby@3\nif \"@<PREFIX>\" is specified, it will show the latest installed version\nthat matches the prefix\notherwise, it will show the current, active installed version"
-    arg "[ASDF_VERSION]" help="the version prefix to use when querying the latest version\nsame as the first argument after the \"@\"\nused for asdf compatibility" hide=true
-}
-cmd "which" help="Shows the path that a tool's bin points to." {
-    long_help r"Shows the path that a tool's bin points to.
-
-Use this to figure out what version of a tool is currently active."
-    after_long_help r"Examples:
-
-    $ mise which node
-    /home/username/.local/share/mise/installs/node/20.0.0/bin/node
-
-    $ mise which node --plugin
-    node
-
-    $ mise which node --version
-    20.0.0
-"
-    flag "--plugin" help="Show the plugin name instead of the path"
-    flag "--version" help="Show the version instead of the path"
+cmd where help="Display the installation path for a tool" {
+    long_help "Display the installation path for a tool\n\nThe tool must be installed for this to work."
+    after_long_help "Examples:\n\n    # Show the latest installed version of node\n    # If it is is not installed, errors\n    $ mise where node@20\n    /home/jdx/.local/share/mise/installs/node/20.0.0\n\n    # Show the current, active install directory of node\n    # Errors if node is not referenced in any .tool-version file\n    $ mise where node\n    /home/jdx/.local/share/mise/installs/node/20.0.0\n"
+    arg <TOOL@VERSION> help="Tool(s) to look up\ne.g.: ruby@3\nif \"@<PREFIX>\" is specified, it will show the latest installed version\nthat matches the prefix\notherwise, it will show the current, active installed version"
+    arg "[ASDF_VERSION]" help="the version prefix to use when querying the latest version\nsame as the first argument after the \"@\"\nused for asdf compatibility" required=#false hide=#true
+}
+cmd which help="Shows the path that a tool's bin points to." {
+    long_help "Shows the path that a tool's bin points to.\n\nUse this to figure out what version of a tool is currently active."
+    after_long_help "Examples:\n\n    $ mise which node\n    /home/username/.local/share/mise/installs/node/20.0.0/bin/node\n\n    $ mise which node --plugin\n    node\n\n    $ mise which node --version\n    20.0.0\n"
+    flag --complete hide=#true
+    flag --plugin help="Show the plugin name instead of the path"
+    flag --version help="Show the version instead of the path"
     flag "-t --tool" help="Use a specific tool@version\ne.g.: `mise which npm --tool=node@20`" {
-        arg "<TOOL@VERSION>"
+        arg <TOOL@VERSION>
     }
-    arg "<BIN_NAME>" help="The bin to look up"
+    arg "[BIN_NAME]" help="The bin to look up" required=#false
 }
-cmd "render-help" hide=true help="internal command to generate markdown from help"
-cmd "render-mangen" hide=true help="internal command to generate markdown from help"
+cmd render-help hide=#true help="internal command to generate markdown from help"
+cmd render-mangen hide=#true help="internal command to generate markdown from help"
+source_code_link_template #"""
+{%- set path = path | replace(from='-', to='_') -%}
+{%- if cmd.subcommands | length > 0 -%}
+{%- set path = path | split(pat="/") | slice(end=1) | concat(with="mod.rs") | join(sep="/") -%}
+{%- else -%}
+{%- set path = path ~ ".rs" -%}
+{%- endif -%}
+https://github.com/jdx/mise/blob/main/src/cli/{{path}}
+"""#
 
 complete "alias" run="mise alias ls {{words[PREV]}} | awk '{print $2}'"
 complete "config_file" type="file"
 complete "new_plugin" run="mise plugins --all"
+complete "installed_tool" run="mise plugins --core --user"
 complete "plugin" run="mise plugins --core --user"
 complete "prefix" run="mise ls-remote {{words[PREV]}}"
-complete "setting" run="mise settings --keys"
-complete "task" run="mise tasks | awk '{print $1}'"
-
-complete "tool@version" run=r#"
+complete "setting" run="mise settings --complete" descriptions=#true
+complete "task" run="mise tasks ls --complete" descriptions=#true
+complete "tool" run="mise registry --complete" descriptions=#true
+complete "env_var" run=#"mise set --complete | awk '{print $1"="}'"#
+complete "env_key" run="mise set --complete"
+complete "backend" run="mise backends"
+complete "bin_name" run="mise which --complete"
+
+complete "tool@version" run=#"""
 cur="{{words[CURRENT]}}"
 case $cur in
   *@*)
@@ -1548,11 +1213,10 @@ case $cur in
     done
     ;;
   *)
-    plugins=$(mise plugins --core --user)
+    plugins=$(mise ls --installed | awk '{print $1}' | sed '1!G;h;$!d')
     for plugin in $plugins; do
       echo "$plugin@"
     done
     ;;
 esac
-"#
-
+"""#
diff --git a/lib/Cargo.toml b/lib/Cargo.toml
index 7aea3e41..272bbc87 100644
--- a/lib/Cargo.toml
+++ b/lib/Cargo.toml
@@ -26,7 +26,7 @@ clap = { version = "4", features = ["derive", "string"], optional = true }
 heck = "0.5"
 indexmap = { version = "2", features = ["serde"] }
 itertools = "0.14"
-kdl = "= 4.7.0"
+kdl = "6"
 log = "0.4"
 miette = "7"
 once_cell = "1"
diff --git a/lib/src/complete/snapshots/usage__complete__bash__tests__complete_bash-3.snap b/lib/src/complete/snapshots/usage__complete__bash__tests__complete_bash-3.snap
index f0421e3a..33cd3d23 100644
--- a/lib/src/complete/snapshots/usage__complete__bash__tests__complete_bash-3.snap
+++ b/lib/src/complete/snapshots/usage__complete__bash__tests__complete_bash-3.snap
@@ -12,38 +12,38 @@ _mycli() {
     fi
 
     read -r -d '' _usage_spec_mycli <<'__USAGE_EOF__'
-name "mycli"
-bin "mycli"
+name mycli
+bin mycli
 source_code_link_template "https://github.com/jdx/mise/blob/main/src/cli/{{path}}.rs"
-flag "--flag1" help="flag1 description"
-flag "--flag2" help="flag2 description" {
-    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world\n"
+flag --flag1 help="flag1 description"
+flag --flag2 help="flag2 description" {
+    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world"
 }
-flag "--flag3" help="flag3 description" negate="--no-flag3"
-flag "--with-default"
-flag "--shell" {
-    arg "<shell>" {
-        choices "bash" "zsh" "fish"
+flag --flag3 help="flag3 description" negate=--no-flag3
+flag --with-default
+flag --shell {
+    arg <shell> {
+        choices bash zsh fish
     }
 }
-arg "<arg1>" help="arg1 description"
-arg "[arg2]" help="arg2 description" required=false default="default value" {
-    choices "choice1" "choice2" "choice3"
+arg <arg1> help="arg1 description"
+arg "[arg2]" help="arg2 description" required=#false default="default value" {
+    choices choice1 choice2 choice3
 }
-arg "<arg3>" help="arg3 description" help_long="arg3 long description"
-arg "<argrest>..." var=true
-arg "[with-default]" required=false default="default value"
-complete "plugin" run="echo \"plugin-1\nplugin-2\nplugin-3\""
-cmd "plugin" {
-    cmd "install" {
-        long_help r"install a plugin"
-        flag "-g --global" global=true
+arg <arg3> help="arg3 description" help_long="arg3 long description"
+arg <argrest>... var=#true
+arg "[with-default]" required=#false default="default value"
+complete plugin run="echo \"plugin-1\nplugin-2\nplugin-3\""
+cmd plugin {
+    cmd install {
+        long_help "install a plugin"
+        flag "-g --global" global=#true
         flag "-d --dir" {
-            arg "<dir>"
+            arg <dir>
         }
-        flag "-f --force" negate="--no-force"
-        arg "<plugin>"
-        arg "<version>"
+        flag "-f --force" negate=--no-force
+        arg <plugin>
+        arg <version>
     }
 }
 __USAGE_EOF__
diff --git a/lib/src/complete/snapshots/usage__complete__fish__tests__complete_fish-3.snap b/lib/src/complete/snapshots/usage__complete__fish__tests__complete_fish-3.snap
index 959177bc..e7c8b4e4 100644
--- a/lib/src/complete/snapshots/usage__complete__fish__tests__complete_fish-3.snap
+++ b/lib/src/complete/snapshots/usage__complete__fish__tests__complete_fish-3.snap
@@ -11,38 +11,38 @@ if ! command -v usage &> /dev/null
     return 1
 end
 
-set _usage_spec_mycli 'name "mycli"
-bin "mycli"
+set _usage_spec_mycli 'name mycli
+bin mycli
 source_code_link_template "https://github.com/jdx/mise/blob/main/src/cli/{{path}}.rs"
-flag "--flag1" help="flag1 description"
-flag "--flag2" help="flag2 description" {
-    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world\n"
+flag --flag1 help="flag1 description"
+flag --flag2 help="flag2 description" {
+    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world"
 }
-flag "--flag3" help="flag3 description" negate="--no-flag3"
-flag "--with-default"
-flag "--shell" {
-    arg "<shell>" {
-        choices "bash" "zsh" "fish"
+flag --flag3 help="flag3 description" negate=--no-flag3
+flag --with-default
+flag --shell {
+    arg <shell> {
+        choices bash zsh fish
     }
 }
-arg "<arg1>" help="arg1 description"
-arg "[arg2]" help="arg2 description" required=false default="default value" {
-    choices "choice1" "choice2" "choice3"
+arg <arg1> help="arg1 description"
+arg "[arg2]" help="arg2 description" required=#false default="default value" {
+    choices choice1 choice2 choice3
 }
-arg "<arg3>" help="arg3 description" help_long="arg3 long description"
-arg "<argrest>..." var=true
-arg "[with-default]" required=false default="default value"
-complete "plugin" run="echo \"plugin-1\nplugin-2\nplugin-3\""
-cmd "plugin" {
-    cmd "install" {
-        long_help r"install a plugin"
-        flag "-g --global" global=true
+arg <arg3> help="arg3 description" help_long="arg3 long description"
+arg <argrest>... var=#true
+arg "[with-default]" required=#false default="default value"
+complete plugin run="echo \"plugin-1\nplugin-2\nplugin-3\""
+cmd plugin {
+    cmd install {
+        long_help "install a plugin"
+        flag "-g --global" global=#true
         flag "-d --dir" {
-            arg "<dir>"
+            arg <dir>
         }
-        flag "-f --force" negate="--no-force"
-        arg "<plugin>"
-        arg "<version>"
+        flag "-f --force" negate=--no-force
+        arg <plugin>
+        arg <version>
     }
 }
 '
diff --git a/lib/src/complete/snapshots/usage__complete__zsh__tests__complete_zsh-3.snap b/lib/src/complete/snapshots/usage__complete__zsh__tests__complete_zsh-3.snap
index c3ec73ae..c76c82e8 100644
--- a/lib/src/complete/snapshots/usage__complete__zsh__tests__complete_zsh-3.snap
+++ b/lib/src/complete/snapshots/usage__complete__zsh__tests__complete_zsh-3.snap
@@ -17,38 +17,38 @@ _mycli() {
       return 1
   fi
 read -r -d '' spec <<'__USAGE_EOF__'
-name "mycli"
-bin "mycli"
+name mycli
+bin mycli
 source_code_link_template "https://github.com/jdx/mise/blob/main/src/cli/{{path}}.rs"
-flag "--flag1" help="flag1 description"
-flag "--flag2" help="flag2 description" {
-    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world\n"
+flag --flag1 help="flag1 description"
+flag --flag2 help="flag2 description" {
+    long_help "flag2 long description\n\nincludes a code block:\n\n    $ echo hello world\n    hello world\n\n    more code\n\nExamples:\n\n    # run with no arguments to use the interactive selector\n    $ mise use\n\n    # set the current version of node to 20.x in mise.toml of current directory\n    # will write the fuzzy version (e.g.: 20)\n\nsome docs\n\n    $ echo hello world\n    hello world"
 }
-flag "--flag3" help="flag3 description" negate="--no-flag3"
-flag "--with-default"
-flag "--shell" {
-    arg "<shell>" {
-        choices "bash" "zsh" "fish"
+flag --flag3 help="flag3 description" negate=--no-flag3
+flag --with-default
+flag --shell {
+    arg <shell> {
+        choices bash zsh fish
     }
 }
-arg "<arg1>" help="arg1 description"
-arg "[arg2]" help="arg2 description" required=false default="default value" {
-    choices "choice1" "choice2" "choice3"
+arg <arg1> help="arg1 description"
+arg "[arg2]" help="arg2 description" required=#false default="default value" {
+    choices choice1 choice2 choice3
 }
-arg "<arg3>" help="arg3 description" help_long="arg3 long description"
-arg "<argrest>..." var=true
-arg "[with-default]" required=false default="default value"
-complete "plugin" run="echo \"plugin-1\nplugin-2\nplugin-3\""
-cmd "plugin" {
-    cmd "install" {
-        long_help r"install a plugin"
-        flag "-g --global" global=true
+arg <arg3> help="arg3 description" help_long="arg3 long description"
+arg <argrest>... var=#true
+arg "[with-default]" required=#false default="default value"
+complete plugin run="echo \"plugin-1\nplugin-2\nplugin-3\""
+cmd plugin {
+    cmd install {
+        long_help "install a plugin"
+        flag "-g --global" global=#true
         flag "-d --dir" {
-            arg "<dir>"
+            arg <dir>
         }
-        flag "-f --force" negate="--no-force"
-        arg "<plugin>"
-        arg "<version>"
+        flag "-f --force" negate=--no-force
+        arg <plugin>
+        arg <version>
     }
 }
 __USAGE_EOF__
diff --git a/lib/src/spec/arg.rs b/lib/src/spec/arg.rs
index 1f79b98c..a1cbb687 100644
--- a/lib/src/spec/arg.rs
+++ b/lib/src/spec/arg.rs
@@ -67,7 +67,7 @@ impl SpecArg {
                 "var_min" => arg.var_min = v.ensure_usize().map(Some)?,
                 "var_max" => arg.var_max = v.ensure_usize().map(Some)?,
                 "default" => arg.default = v.ensure_string().map(Some)?,
-                k => bail_parse!(ctx, *v.entry.span(), "unsupported arg key {k}"),
+                k => bail_parse!(ctx, v.entry.span(), "unsupported arg key {k}"),
             }
         }
         if arg.default.is_some() {
@@ -76,7 +76,7 @@ impl SpecArg {
         for child in node.children() {
             match child.name() {
                 "choices" => arg.choices = Some(SpecChoices::parse(ctx, &child)?),
-                k => bail_parse!(ctx, *child.node.name().span(), "unsupported arg child {k}"),
+                k => bail_parse!(ctx, child.node.name().span(), "unsupported arg child {k}"),
             }
         }
         arg.usage = arg.usage();
@@ -132,10 +132,10 @@ impl From<&SpecArg> for KdlNode {
             node.push(KdlEntry::new_prop("var", true));
         }
         if let Some(min) = arg.var_min {
-            node.push(KdlEntry::new_prop("var_min", min as i64));
+            node.push(KdlEntry::new_prop("var_min", min as i128));
         }
         if let Some(max) = arg.var_max {
-            node.push(KdlEntry::new_prop("var_max", max as i64));
+            node.push(KdlEntry::new_prop("var_max", max as i128));
         }
         if arg.hide {
             node.push(KdlEntry::new_prop("hide", true));
diff --git a/lib/src/spec/cmd.rs b/lib/src/spec/cmd.rs
index 17036f5b..da3b3d43 100644
--- a/lib/src/spec/cmd.rs
+++ b/lib/src/spec/cmd.rs
@@ -138,7 +138,7 @@ impl SpecCommand {
                         None => Some(v.ensure_string()?),
                     }
                 }
-                k => bail_parse!(ctx, *v.entry.span(), "unsupported cmd prop {k}"),
+                k => bail_parse!(ctx, v.entry.span(), "unsupported cmd prop {k}"),
             }
         }
         for child in node.children() {
@@ -174,7 +174,7 @@ impl SpecCommand {
                             "header" => example.header = Some(v.ensure_string()?),
                             "help" => example.help = Some(v.ensure_string()?),
                             "lang" => example.lang = v.ensure_string()?,
-                            k => bail_parse!(ctx, *v.entry.span(), "unsupported example key {k}"),
+                            k => bail_parse!(ctx, v.entry.span(), "unsupported example key {k}"),
                         }
                     }
                     cmd.examples.push(example);
@@ -214,7 +214,7 @@ impl SpecCommand {
                     let complete = SpecComplete::parse(ctx, &child)?;
                     cmd.complete.insert(complete.name.clone(), complete);
                 }
-                k => bail_parse!(ctx, *child.node.name().span(), "unsupported cmd key {k}"),
+                k => bail_parse!(ctx, child.node.name().span(), "unsupported cmd key {k}"),
             }
         }
         Ok(cmd)
@@ -398,13 +398,13 @@ impl From<&SpecCommand> for KdlNode {
         if let Some(help) = &cmd.help_long {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("long_help");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         if let Some(help) = &cmd.help_md {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("help_md");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         if let Some(help) = &cmd.before_help {
@@ -414,13 +414,13 @@ impl From<&SpecCommand> for KdlNode {
         if let Some(help) = &cmd.before_help_long {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("before_long_help");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         if let Some(help) = &cmd.before_help_md {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("before_help_md");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         if let Some(help) = &cmd.after_help {
@@ -430,13 +430,13 @@ impl From<&SpecCommand> for KdlNode {
         if let Some(help) = &cmd.after_help_long {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("after_long_help");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         if let Some(help) = &cmd.after_help_md {
             let children = node.children_mut().get_or_insert_with(KdlDocument::new);
             let mut node = KdlNode::new("after_help_md");
-            node.insert(0, KdlValue::RawString(help.clone()));
+            node.insert(0, KdlValue::String(help.clone()));
             children.nodes_mut().push(node);
         }
         for flag in &cmd.flags {
diff --git a/lib/src/spec/complete.rs b/lib/src/spec/complete.rs
index af421a09..8ded9744 100644
--- a/lib/src/spec/complete.rs
+++ b/lib/src/spec/complete.rs
@@ -26,18 +26,18 @@ impl SpecComplete {
             match k {
                 "run" => {
                     if config.type_.is_some() {
-                        bail_parse!(ctx, *v.entry.span(), "can set run or type, not both")
+                        bail_parse!(ctx, v.entry.span(), "can set run or type, not both")
                     }
                     config.run = Some(v.ensure_string()?.to_string())
                 }
                 "descriptions" => config.descriptions = v.ensure_bool()?,
                 "type" => {
                     if config.run.is_some() {
-                        bail_parse!(ctx, *v.entry.span(), "can set run or type, not both")
+                        bail_parse!(ctx, v.entry.span(), "can set run or type, not both")
                     }
                     config.type_ = Some(v.ensure_string()?.to_string())
                 }
-                k => bail_parse!(ctx, *v.entry.span(), "unsupported complete key {k}"),
+                k => bail_parse!(ctx, v.entry.span(), "unsupported complete key {k}"),
             }
         }
         Ok(config)
diff --git a/lib/src/spec/config.rs b/lib/src/spec/config.rs
index c4dd4af5..05861319 100644
--- a/lib/src/spec/config.rs
+++ b/lib/src/spec/config.rs
@@ -36,7 +36,7 @@ impl SpecConfig {
                     }
                     config.props.insert(key, prop);
                 }
-                k => bail_parse!(ctx, *node.node.name().span(), "unsupported config key {k}"),
+                k => bail_parse!(ctx, node.node.name().span(), "unsupported config key {k}"),
             }
         }
         Ok(config)
@@ -125,7 +125,7 @@ mod tests {
             &Default::default(),
             r#"
 config {
-    prop "color" default=true env="COLOR" help="Enable color output"
+    prop "color" default=#true env="COLOR" help="Enable color output"
     prop "user" default="admin" env="USER" help="User to run as"
     prop "jobs" default=4 env="JOBS" help="Number of jobs to run"
     prop "timeout" default=1.5 env="TIMEOUT" help="Timeout in seconds" \
@@ -135,13 +135,13 @@ config {
         )
         .unwrap();
 
-        assert_snapshot!(spec, @r###"
+        assert_snapshot!(spec, @r##"
         config {
-            prop "color" default="true" env="COLOR" help="Enable color output"
-            prop "jobs" default="4" env="JOBS" help="Number of jobs to run"
-            prop "timeout" default="1.5" env="TIMEOUT" help="Timeout in seconds" long_help="Timeout in seconds, can be fractional"
-            prop "user" default="\"admin\"" env="USER" help="User to run as"
+            prop color default="#true" env=COLOR help="Enable color output"
+            prop jobs default="4" env=JOBS help="Number of jobs to run"
+            prop timeout default="1.5" env=TIMEOUT help="Timeout in seconds" long_help="Timeout in seconds, can be fractional"
+            prop user default=admin env=USER help="User to run as"
         }
-        "###);
+        "##);
     }
 }
diff --git a/lib/src/spec/flag.rs b/lib/src/spec/flag.rs
index 6bad6017..b1a75eea 100644
--- a/lib/src/spec/flag.rs
+++ b/lib/src/spec/flag.rs
@@ -67,7 +67,7 @@ impl SpecFlag {
                 "count" => flag.count = v.ensure_bool()?,
                 "default" => flag.default = v.ensure_string().map(Some)?,
                 "negate" => flag.negate = v.ensure_string().map(Some)?,
-                k => bail_parse!(ctx, *v.entry.span(), "unsupported flag key {k}"),
+                k => bail_parse!(ctx, v.entry.span(), "unsupported flag key {k}"),
             }
         }
         if flag.default.is_some() {
@@ -99,12 +99,12 @@ impl SpecFlag {
                     } else {
                         bail_parse!(
                             ctx,
-                            *child.node.name().span(),
+                            child.node.name().span(),
                             "flag must have value to have choices"
                         )
                     }
                 }
-                k => bail_parse!(ctx, *child.node.name().span(), "unsupported flag child {k}"),
+                k => bail_parse!(ctx, child.node.name().span(), "unsupported flag child {k}"),
             }
         }
         flag.usage = flag.usage();
diff --git a/lib/src/spec/helpers.rs b/lib/src/spec/helpers.rs
index 818f2da6..37c0ac67 100644
--- a/lib/src/spec/helpers.rs
+++ b/lib/src/spec/helpers.rs
@@ -37,7 +37,7 @@ impl<'a> NodeHelper<'a> {
         Ok(self)
     }
     pub(crate) fn get(&self, key: &str) -> Option<ParseEntry> {
-        self.node.get(key).map(|e| ParseEntry::new(self.ctx, e))
+        self.node.entry(key).map(|e| ParseEntry::new(self.ctx, e))
     }
     pub(crate) fn arg(&self, i: usize) -> Result<ParseEntry, UsageErr> {
         if let Some(entry) = self.args().nth(i) {
@@ -98,14 +98,14 @@ impl<'a> ParseEntry<'a> {
 
 impl ParseEntry<'_> {
     pub fn ensure_usize(&self) -> Result<usize, UsageErr> {
-        match self.value.as_i64() {
+        match self.value.as_integer() {
             Some(i) => Ok(i as usize),
             None => bail_parse!(self.ctx, self.span(), "expected usize"),
         }
     }
     #[allow(dead_code)]
     pub fn ensure_f64(&self) -> Result<f64, UsageErr> {
-        match self.value.as_f64() {
+        match self.value.as_float() {
             Some(f) => Ok(f),
             None => bail_parse!(self.ctx, self.span(), "expected float"),
         }
diff --git a/lib/src/spec/mod.rs b/lib/src/spec/mod.rs
index cd621dfd..6107c820 100644
--- a/lib/src/spec/mod.rs
+++ b/lib/src/spec/mod.rs
@@ -152,7 +152,7 @@ impl Spec {
                     let (other, _) = Self::parse_file(&file)?;
                     schema.merge(other);
                 }
-                k => bail_parse!(ctx, *node.node.name().span(), "unsupported spec key {k}"),
+                k => bail_parse!(ctx, node.node.name().span(), "unsupported spec key {k}"),
             }
         }
         schema.cmd.name = if schema.bin.is_empty() {
@@ -314,12 +314,12 @@ impl Display for Spec {
         }
         if let Some(about_md) = &self.about_md {
             let mut node = KdlNode::new("about_md");
-            node.push(KdlEntry::new(KdlValue::RawString(about_md.clone())));
+            node.push(KdlEntry::new(KdlValue::String(about_md.clone())));
             nodes.push(node);
         }
         if let Some(long_about) = &self.about_long {
             let mut node = KdlNode::new("long_about");
-            node.push(KdlEntry::new(KdlValue::RawString(long_about.clone())));
+            node.push(KdlEntry::new(KdlValue::String(long_about.clone())));
             nodes.push(node);
         }
         if let Some(disable_help) = self.disable_help {
@@ -355,6 +355,7 @@ impl Display for Spec {
         if !self.config.is_empty() {
             nodes.push((&self.config).into());
         }
+        doc.autoformat_config(&kdl::FormatConfigBuilder::new().build());
         write!(f, "{}", doc)
     }
 }
@@ -406,7 +407,7 @@ mod tests {
 name "Usage CLI"
 bin "usage"
 arg "arg1"
-flag "-f --force" global=true
+flag "-f --force" global=#true
 cmd "config" {
   cmd "set" {
     arg "key" help="Key to set"
@@ -417,29 +418,29 @@ complete "file" run="ls"
         "#,
         )
         .unwrap();
-        assert_snapshot!(spec, @r###"
+        assert_snapshot!(spec, @r#"
         name "Usage CLI"
-        bin "usage"
-        flag "-f --force" global=true
-        arg "<arg1>"
-        complete "file" run="ls"
-        cmd "config" {
-            cmd "set" {
-                arg "<key>" help="Key to set"
-                arg "<value>"
+        bin usage
+        flag "-f --force" global=#true
+        arg <arg1>
+        complete file run=ls
+        cmd config {
+            cmd set {
+                arg <key> help="Key to set"
+                arg <value>
             }
         }
-        "###);
+        "#);
     }
 
     #[test]
     #[cfg(feature = "clap")]
     fn test_clap() {
         let cmd = clap::Command::new("test");
-        assert_snapshot!(Spec::from(&cmd), @r###"
-        name "test"
-        bin "test"
+        assert_snapshot!(Spec::from(&cmd), @r#"
+        name test
+        bin test
         usage "Usage: test"
-        "###);
+        "#);
     }
 }
diff --git a/lib/src/spec/mount.rs b/lib/src/spec/mount.rs
index c28a2c37..8dfa542e 100644
--- a/lib/src/spec/mount.rs
+++ b/lib/src/spec/mount.rs
@@ -18,7 +18,7 @@ impl SpecMount {
         for (k, v) in node.props() {
             match k {
                 "run" => mount.run = v.ensure_string()?,
-                k => bail_parse!(ctx, *v.entry.span(), "unsupported mount key {k}"),
+                k => bail_parse!(ctx, v.entry.span(), "unsupported mount key {k}"),
             }
         }
         for child in node.children() {
@@ -26,7 +26,7 @@ impl SpecMount {
                 "run" => mount.run = child.arg(0)?.ensure_string()?,
                 k => bail_parse!(
                     ctx,
-                    *child.node.name().span(),
+                    child.node.name().span(),
                     "unsupported mount value key {k}"
                 ),
             }
diff --git a/lib/src/test.rs b/lib/src/test.rs
index 571d0a37..4b70c1fa 100644
--- a/lib/src/test.rs
+++ b/lib/src/test.rs
@@ -16,12 +16,13 @@ arg "arg1" help="arg1 description"
 arg "arg2" help="arg2 description" default="default value" {
     choices "choice1" "choice2" "choice3"
 }
-arg "arg3" help="arg3 description" required=true long_help="arg3 long description"
-arg "argrest" var=true
+arg "arg3" help="arg3 description" required=#true long_help="arg3 long description"
+arg "argrest" var=#true
 arg "with-default" default="default value"
 
 flag "--flag1" help="flag1 description"
-flag "--flag2" help="flag2 description" long_help=r#"flag2 long description
+flag "--flag2" help="flag2 description" long_help=#"""
+flag2 long description
 
 includes a code block:
 
@@ -42,9 +43,9 @@ some docs
 
     $ echo hello world
     hello world
-"#
+"""#
 flag "--flag3" help="flag3 description" negate="--no-flag3"
-flag "--with-default" required=true default="default value"
+flag "--with-default" required=#true default="default value"
 
 flag "--shell <shell>" {
   choices "bash" "zsh" "fish"
@@ -54,7 +55,7 @@ cmd "plugin" {
   cmd "install" long_help="install a plugin" {
     arg "plugin"
     arg "version"
-    flag "-g --global" global=true
+    flag "-g --global" global=#true
     flag "-d --dir <dir>"
     flag "-f --force" negate="--no-force"
   }
diff --git a/lib/tests/dump.rs b/lib/tests/dump.rs
index 62e1d8b4..c6c6ab95 100644
--- a/lib/tests/dump.rs
+++ b/lib/tests/dump.rs
@@ -14,16 +14,16 @@ macro_rules! tests_same {
 }
 
 tests_same! {
-    negate: r#"flag "--force" negate="--no-force""#,
+    negate: r#"flag --force negate=--no-force"#,
 
-    flag_choices: r#"flag "--shell" {
-    arg "<shell>" {
-        choices "bash" "fish" "zsh"
+    flag_choices: r#"flag --shell {
+    arg <shell> {
+        choices bash fish zsh
     }
 }"#,
 
-    arg_choices: r#"arg "<shell>" {
-    choices "bash" "fish" "zsh"
+    arg_choices: r#"arg <shell> {
+    choices bash fish zsh
 }"#,
 
     double_dash: r#"arg "<-- shell...>""#,
diff --git a/lib/tests/parse.rs b/lib/tests/parse.rs
index b14f3fa6..2a8418fb 100644
--- a/lib/tests/parse.rs
+++ b/lib/tests/parse.rs
@@ -26,7 +26,7 @@ required_arg:
     expected=r#"Missing required arg: <name>"#,
 
 required_flag:
-    spec=r#"flag "--name <name>" required=true"#,
+    spec=r#"flag "--name <name>" required=#true"#,
     args="",
     expected=r#"Missing required flag: --name <name>"#,
 
@@ -180,21 +180,21 @@ arg_default:
 
 multi_arg:
     spec=r#"
-    arg "<vars>" var=true
+    arg "<vars>" var=#true
     "#,
     args="a b c",
     expected=r#"{"usage_vars": "a b c"}"#,
 
 multi_arg_spaces:
     spec=r#"
-    arg "<vars>" var=true
+    arg "<vars>" var=#true
     "#,
     args=r#"a "b c""#,
     expected=r#"{"usage_vars": "a 'b c'"}"#,
 
 //shell_escape_arg:
 //    spec=r#"
-//    arg "<vars>" shell_escape=true
+//    arg "<vars>" shell_escape=#true
 //    "#,
 //    args=r#"a "b c""#,
 //    expected=r#"{"usage_vars": "a 'b c'"}"#,