feat: only provide snippets in files mise support

Author: hverlin

README.md

@@ -104,7 +104,9 @@ The mise-vscode extension integrates mise's core functionality into VS Code, hel
 
 ### Snippets
 
-- 📝 Snippets to create tasks in `mise.toml` and task files
+- 📝 `mise-task` snippets to create tasks in `mise.toml` and task files. They
+  are only suggested in the files mise loads, and only where a task can be
+  inserted. Set `mise.enableSnippets` to `false` to turn them off.
 
 ### Integration with VSCode tasks (`launch.json`)
 

docs/src/content/docs/reference/Settings.md

@@ -275,7 +275,7 @@ Show the tools and environment variables of each [monorepo](https://mise.jdx.dev
 
 Show a code lens on each `[bootstrap.*]` section reporting how many of its entries are not in their desired state.
 
-Requires `#mise.enableCodeLens#` and mise 2026.7.16+. Reading the status runs `mise bootstrap status`, which inspects the machine (installed packages, cloned repos, macOS defaults, Docker Compose projects); the result is cached and only read for files that declare a bootstrap section.
+Requires `mise.enableCodeLens` and mise 2026.7.16+. Reading the status runs `mise bootstrap status`, which inspects the machine (installed packages, cloned repos, macOS defaults, Docker Compose projects); the result is cached and only read for files that declare a bootstrap section.
 
 ---
 
@@ -319,6 +319,16 @@ Enable Tera auto-completion in `mise.toml` files.
 
 ---
 
+##### `mise.enableSnippets`
+- **Type:** `boolean`
+- **Default:** `true`
+
+Suggest task snippets (`mise-task`, `mise-task-script`, ...) in mise configuration files and in file tasks.
+
+They are also hidden by `editor.snippetSuggestions` set to `none` and by `editor.suggest.showSnippets` set to `false`, which apply to every extension.
+
+---
+
 ##### `mise.automaticallyTrustMiseConfigFiles`
 - **Type:** `boolean`
 - **Default:** `true`

docs/src/content/docs/reference/Tasks.md

@@ -114,6 +114,21 @@ New file tasks are created with a working example of
 flag, argument with a default value, custom completion, and the corresponding
 `$usage_*` variables in the script).
 
+### Using snippets
+
+Type `mise-task` in a mise configuration file to get snippets for the different
+shapes a task can take: `mise-task`, `mise-task-array`, `mise-task-script`,
+`mise-task-usage`, `mise-task-template`, `mise-task-full`, and one per language
+(`mise-task-node`, `mise-task-python`, `mise-task-uv`, `mise-task-deno`,
+`mise-task-bun`, `mise-task-ruby`). In a file task, `mise-task` inserts a
+`#MISE` configuration block and `mise-task-usage` a `#USAGE` argument block.
+
+The snippets are only suggested in the files mise loads, which are the
+[configuration files](https://mise.jdx.dev/configuration.html) and the scripts
+in a [task directory](https://mise.jdx.dev/tasks/file-tasks.html), and only
+where a task can be inserted: at the start of a line, outside of strings,
+arrays and comments. Set `mise.enableSnippets` to `false` to turn them off.
+
 ## Task dependencies
 
 You can visualize the dependencies of a task by using the `Mise: Visualize Tasks Dependencies` command.
@@ -178,8 +193,7 @@ particularly useful in a [monorepo](#monorepo-tasks). It provides:
   entry, in the same file or in a parent config file
 - **Find references** from a template declaration to every task extending it,
   anywhere in the workspace
-- Task templates in the outline view, and `task_template` / `task_extends`
-  snippets
+- Task templates in the outline view, and a `mise-task-template` snippet
 
 Task hovers show the template a task extends. The fields shown for the task
 itself are the ones mise resolved, i.e. after the template has been merged in.

docs/src/extract-settings.mjs

@@ -29,6 +29,15 @@ access the extension settings.
 
 ## Settings`;
 
+/**
+ * `#editor.snippetSuggestions#` links to another setting in the VS Code
+ * settings UI, the docs show the setting name instead. The markers are dropped
+ * whether or not they are already inside a code span.
+ */
+function renderSettingLinks(description) {
+	return description.replace(/`?#([\w.-]+)#`?/g, "`$1`");
+}
+
 function generateWikiContent(packageJson) {
 	const settings = packageJson.contributes.configuration.properties;
 	const settingsEntries = Object.entries(settings).sort(
@@ -56,7 +65,7 @@ function generateWikiContent(packageJson) {
 			content += `- **Default:** \`${defaultValue}\`\n\n`;
 		}
 
-		content += `${setting.markdownDescription}\n\n`;
+		content += `${renderSettingLinks(setting.markdownDescription)}\n\n`;
 
 		if (setting.items?.enum) {
 			content += "**Available options:**\n\n";

package.json

@@ -178,16 +178,6 @@
         ]
       }
     ],
-    "snippets": [
-      {
-        "language": "toml",
-        "path": "./snippets/toml-tasks-snippets.json"
-      },
-      {
-        "language": "shellscript",
-        "path": "./snippets/file-tasks-snippets.json"
-      }
-    ],
     "configurationDefaults": {
       "[toml]": {
         "editor.quickSuggestions": {
@@ -447,6 +437,13 @@
           "default": true,
           "markdownDescription": "Enable Tera auto-completion in `mise.toml` files."
         },
+        "mise.enableSnippets": {
+          "order": 14.1,
+          "type": "boolean",
+          "title": "Enable snippets",
+          "default": true,
+          "markdownDescription": "Suggest task snippets (`mise-task`, `mise-task-script`, ...) in mise configuration files and in file tasks.\n\nThey are also hidden by `#editor.snippetSuggestions#` set to `none` and by `#editor.suggest.showSnippets#` set to `false`, which apply to every extension."
+        },
         "mise.automaticallyTrustMiseConfigFiles": {
           "order": 15,
           "type": "boolean",

src/browser.ts

@@ -1,7 +1,15 @@
 import * as vscode from "vscode";
 import { MiseTomlTaskSymbolProvider } from "./providers/MiseTomlTaskSymbolProvider";
+import { MiseSnippetProvider } from "./providers/miseSnippetProvider";
 import { logger } from "./utils/logger";
 
+/**
+ * The settings are read directly here: `configuration.ts` reaches for node-only
+ * helpers, which the web bundle cannot pull in.
+ */
+const isEnabled = (flag: string) =>
+	vscode.workspace.getConfiguration("mise").get<boolean>(flag) ?? true;
+
 /**
  * Browser/web extension entry point.
  */
@@ -17,6 +25,22 @@ export async function activate(context: vscode.ExtensionContext) {
 				new MiseTomlTaskSymbolProvider(vscode),
 			),
 		);
+
+		// no mise binary on the web: the files are recognised by their name only
+		const snippetProvider = new MiseSnippetProvider({
+			isEnabled: () => isEnabled("enable") && isEnabled("enableSnippets"),
+		});
+
+		context.subscriptions.push(
+			vscode.languages.registerCompletionItemProvider(
+				{ language: "toml" },
+				snippetProvider,
+			),
+			vscode.languages.registerCompletionItemProvider(
+				{ language: "shellscript" },
+				snippetProvider,
+			),
+		);
 	} catch (error) {
 		logger.error("Error while activating Mise extension (browser mode)", error);
 		throw error;

src/configuration.ts

@@ -30,6 +30,7 @@ export const CONFIGURATION_FLAGS = {
 	updateEnvAutomaticallyIncludePath: "updateEnvAutomaticallyIncludePath",
 	updateOpenTerminalsEnvAutomatically: "updateOpenTerminalsEnvAutomatically",
 	teraAutoCompletion: "teraAutoCompletion",
+	enableSnippets: "enableSnippets",
 	resolveMonorepoProjectConfigs: "resolveMonorepoProjectConfigs",
 	automaticallyTrustMiseConfigFiles: "automaticallyTrustMiseConfigFiles",
 	commandTTLCacheSeconds: "commandTTLCacheSeconds",
@@ -280,6 +281,10 @@ export const isTeraAutoCompletionEnabled = () => {
 	return getConfOrElse(CONFIGURATION_FLAGS.teraAutoCompletion, true);
 };
 
+export const areSnippetsEnabled = () => {
+	return getConfOrElse(CONFIGURATION_FLAGS.enableSnippets, true);
+};
+
 export const getCommandTTLCacheSeconds = () => {
 	return getConfOrElse(CONFIGURATION_FLAGS.commandTTLCacheSeconds, 2);
 };

src/e2e-tests/fixtures/task-execution-workspace/mise-tasks/new-task.sh

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+
+# Fixture for the snippet suite: a file task in a directory mise loads tasks
+# from. Deliberately left non-executable, so mise does not list it as a task and
+# the task lists the other suites assert on stay unchanged.
+echo "file task fixture for snippets"

src/e2e-tests/fixtures/task-execution-workspace/mise.snippets.toml

@@ -0,0 +1,13 @@
+# Fixture for the snippet suite. `mise.<env>.toml` files are only loaded with
+# MISE_ENV=<env>, so this one is a mise config file by name without changing the
+# tasks of the workspace.
+
+[tasks.example]
+run = '''
+echo "inside a multiline string"
+
+'''
+depends = [
+  "echo-hello",
+
+]

src/e2e-tests/fixtures/task-execution-workspace/not-a-task.sh

@@ -0,0 +1,5 @@
+#!/usr/bin/env bash
+
+# Fixture for the snippet suite: a shell script that is not a mise file task,
+# so no `#MISE`/`#USAGE` snippet should be offered in it.
+echo "not a task"