Skip to content

Extension Settings

You can configure the extension behavior through Visual Studio Code settings. To access the settings:

  1. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
  2. Type “Settings: Open Settings (UI)”
  3. Search for “Mise”

You can also click on the mise extension indicator in the status bar to quickly access the extension settings.

picture showing mise extension settings

  • Type: boolean
  • Default: true

Enable/disable mise extension.


  • Type: string
  • Default: "mise"

Path to the mise binary (automatically detected on startup).

If set to mise (default), it will use mise available in PATH.

See https://mise.jdx.dev/getting-started.html to install mise.



  • Type: boolean
  • Default: false

Automatically configure extensions for the current workspace. (list of supported extensions).

This will modify your workspace settings (.vscode/settings.json). You can use the ignore/include lists settings to customize which extensions are configured.


mise.configureExtensionsAutomaticallyIgnoreList
Section titled “mise.configureExtensionsAutomaticallyIgnoreList”
  • Type: array (array of string)
  • Default: []

List of extensions that should not be configured automatically.

Available options:

  • ms-python.python
  • denoland.vscode-deno
  • charliermarsh.ruff
  • golang.go
  • oven.bun-vscode
  • oracle.oracle-java
  • redhat.java
  • vscjava.vscode-gradle
  • salesforce.salesforcedx-vscode-apex
  • timonwong.shellcheck
  • ms-vscode.js-debug
  • vscode.php-language-features
  • xdebug.php-debug
  • julialang.language-julia
  • pgourlain.erlang
  • Dart-Code.dart-code
  • dart-code.flutter
  • ziglang.vscode-zig
  • signageos.signageos-vscode-sops
  • joselitofilho.ginkgotestexplorer
  • bufbuild.vscode-buf
  • biomejs.biome
  • bazelbuild.vscode-bazel

mise.configureExtensionsAutomaticallyIncludeList
Section titled “mise.configureExtensionsAutomaticallyIncludeList”
  • Type: array (array of string)
  • Default: []

List of extensions that should be configured automatically. If both include and ignore lists are set, the ignore list takes precedence. If the include list includes ‘all’ (default), all supported extensions are considered except those in the ignore list.

Available options:

  • all
  • ms-python.python
  • denoland.vscode-deno
  • charliermarsh.ruff
  • golang.go
  • oven.bun-vscode
  • oracle.oracle-java
  • redhat.java
  • vscjava.vscode-gradle
  • salesforce.salesforcedx-vscode-apex
  • timonwong.shellcheck
  • ms-vscode.js-debug
  • vscode.php-language-features
  • xdebug.php-debug
  • julialang.language-julia
  • pgourlain.erlang
  • Dart-Code.dart-code
  • dart-code.flutter
  • ziglang.vscode-zig
  • signageos.signageos-vscode-sops
  • joselitofilho.ginkgotestexplorer
  • bufbuild.vscode-buf
  • biomejs.biome
  • bazelbuild.vscode-bazel

  • Type: boolean
  • Default: true

Use shims when configuring extensions. When shims are not used, note that you will have to configure environment variables manually.


  • Type: boolean
  • Default: false

Create symlinks in your .vscode folder that links to the mise bin.

This is useful if you share the .vscode/settings.json file with others. When the project is version controlled:

  • every user must have the extension installed
  • the directory .vscode/mise-tools must be excluded from version control.

mise.configureExtensionsIncludeGlobalTools
Section titled “mise.configureExtensionsIncludeGlobalTools”
  • Type: boolean
  • Default: true

When enabled, tools from the global mise configuration (~/.config/mise/config.toml) will be included when automatically configuring VS Code extensions.

When disabled (recommended), only tools from the local project configuration (mise.toml) are used. This prevents settings.json from being polluted with extensions for tools that are not part of the current project.


  • Type: boolean
  • Default: true

Check if a new mise version is available on startup.


  • Type: boolean
  • Default: true

Show tool versions in the editor. (requires reload)


  • Type: boolean
  • Default: true

Show environment variables contributed by each tool in the editor inline decorations (e.g. GOBIN, GOROOT for Go).


  • Type: boolean
  • Default: true

Show run/add tool code lens indicators in the editor.


  • Type: boolean
  • Default: true

Enable document links for tools in mise configuration files.


  • Type: boolean
  • Default: false

Enable document symbol provider for mise TOML files. Provides an outline of tasks, tools, env, and settings sections. This is always enabled on the web. On desktop, you can use Tombi for better TOML support.


  • Type: boolean
  • Default: true

Show notification if tools are not installed.


  • Type: boolean
  • Default: true

Update VSCode and terminal environment variables automatically based on the mise configuration. Note that depending on the extensions loading order, other extensions might not see all mise environment variables.


  • Type: boolean
  • Default: false

Include the PATH variable when updating VSCode and terminal environment variables. Disable this if you want to keep your original PATH.


  • Type: boolean
  • Default: false

Update terminal environment variables automatically based on the mise configuration. This will send unset and eval $(mise env) commands to the terminal. If you don’t enable this, you will need to restart the integrated terminals to get the new environment variables.


  • Type: boolean
  • Default: true

Enable Tera auto-completion in mise.toml files.


  • Type: boolean
  • Default: true

Automatically trust mise config files when opening them in a trusted worskspace.


  • Type: number
  • Default: 2

Time to live in seconds for the mise command cache. Only changed it if some commands are expensive to run.


  • Type: boolean
  • Default: true

Show outdated tool gutter decorations in the editor.


  • Type: boolean
  • Default: true

Auto-detect mise bin path on startup.


  • Type: array (array of object)
  • Default: []

Custom binary extensions to automatically configure VSCode extensions with mise tool binaries.

Each entry requires:

  • extensionId: VSCode extension ID
  • toolSources: Array of mise tool registry sources to match
  • vscodeSetting.key: VSCode setting key to write

Optional:

  • binName: Binary name (defaults to first tool name)
  • vscodeSetting.subdirs: Subdirectories to append to the path
  • supportsShims: Whether extension supports shims (default: true)
  • supportsSymlinks: Whether extension supports symlinks (default: true)

  • Type: array (array of object)
  • Default: []

Custom folder extensions to automatically configure VSCode extensions with mise tool folders.

Each entry requires:

  • extensionId: VSCode extension ID
  • toolSources: Array of mise tool registry sources to match
  • vscodeSetting.key: VSCode setting key to write
  • folderName: Name for the symlink folder

Optional:

  • vscodeSetting.subdirs: Subdirectories to append to the path written to VSCode setting
  • sourceSubdirs: Additional subdirs to find the tool source folder
  • supportsSymlinks: Whether extension supports symlinks (default: true)