mise-pathing-and-shims

Guide selection of mise activation modes for shells, IDEs, and scripts.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-pathing-and-shims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise-pathing-and-shims
Source: https://github.com/ray-manaloto/claude-code-marketplace/tree/main/mise-toolkit/skills/mise-pathing-and-shims
Command: npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-pathing-and-shims

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Selecting the right activation mode for mise can be confusing, especially when env vars, hooks, and PATH changes differ across modes.

Core Features & Use Cases

  • Clarifies six activation modalities: mise activate, mise activate --shims, mise exec, mise env, mise en, and mise run.
  • Explains which loads env, which runs hooks, and when watch_files or other side effects occur.
  • Provides guidance for interactive shells, IDEs, and scripts to pick the appropriate mode.

Quick Start

Identify your environment (interactive shell vs IDE/script) and apply the appropriate mise activation method accordingly.

Frequently Asked Questions about mise-pathing-and-shims

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between mise activate and mise shims?

Choose mise activate for interactive shells to get fast env var loading and hook execution. Use mise exec for one-off commands without changing global state, and mise env when you only need to output variables without running hooks or triggering side effects.

How do I configure mise activation for my IDE?

Configure mise activation for your IDE by using shims mode, which intercepts command execution through proxy scripts. This approach reliably loads the correct env vars and PATH changes in non-interactive environments like VS Code or IntelliJ without requiring shell hooks.

Does mise env run hooks or watch_files like activate does?

mise env does not run hooks or trigger watch_files side effects. It strictly outputs environment variables for the current configuration, making it suitable for scripts or scenarios where you need env var values without the overhead of hook execution.

What's the best way to run a single command with mise without activating the shell?

Use mise exec to run a single command with the correct tool versions and env vars without permanently activating your shell. It applies the configuration only for that specific command execution, leaving your global shell environment untouched.

Why does mise activate load environment variables differently than shims in scripts?

mise activate relies on shell hooks to dynamically load env vars during directory changes, which scripts lack. Shims bypass this by intercepting command calls directly, ensuring the correct env vars and PATH apply even without an interactive shell session.