- Rust 82.5%
- Shell 15.6%
- PowerShell 0.7%
- Lua 0.4%
- Ruby 0.4%
- Other 0.2%
## Summary
- host the generic CAS agent inside the top-level `mise run` process,
with no daemon, buddy executable, or additional release artifact
- install a session-local hardlink to the exact running mise binary
(copy fallback) and dispatch its Rust-wrapper argv0 path before Tokio,
clap, logging, or config discovery
- use an exact protocol/version handshake, permission-restricted Unix
sockets or Windows named pipes, per-digest write deduplication,
lifecycle shutdown, and session statistics
- inject `RUSTC_WRAPPER` and `CARGO_INCREMENTAL=0` only for tasks with
enabled `rust_cache`, chain an existing wrapper, and preserve access
through task sandboxes
- gate the shipped-profile warm wrapper overhead at 2 ms; the measured
overhead on this branch is 1.771 ms
This PR establishes the final in-process session and shim shape.
Compiler-specific keying, cache-hit materialization, remote
prefetch/upload, and Go `GOCACHEPROG` support remain adapter follow-ups.
The Go adapter will introduce its own `go_cache` field when it is
functional.
## Validation
- `cargo test -p mise-cache-core`
- `cargo test --quiet
session_environment_is_scoped_to_selected_adapters`
- `mise run test:e2e e2e/tasks/test_task_action_cache_session`
- `cargo clippy -p mise-cache-core --all-features --all-targets -- -D
warnings`
- `cargo clippy -p mise --all-features --bin mise -- -D warnings`
- `mise run perf:cache-shim` (1.771 ms median overhead, 2 ms budget)
*AI-assisted — Tool: Codex; model: openai/gpt-5; version: unavailable.*
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Medium Risk**
> Touches task execution env, sandbox allowances, and Windows security
descriptors for named pipes; behavior is gated experimental but the shim
runs on every Cargo compile when enabled.
>
> **Overview**
> Adds an **in-process action-cache session** for `mise run` when any
task enables `rust_cache`, without a separate daemon or binary.
>
> **`mise-cache-core`** gains a local CAS (`LocalCas`), a JSON-line
**`CacheAgent`** (handshake, find/store blobs, per-digest locks, stats),
and public digest helpers.
>
> **`src/cache/session.rs`** starts the agent on a session Unix socket
or a **current-user-only** Windows named pipe, installs a session-local
**`mise-cache-rustc`** hardlink to the running binary, and injects
`MISE_CACHE_SOCKET`, `RUSTC_WRAPPER`, `CARGO_INCREMENTAL=0` (chaining
any prior wrapper). **`main`** dispatches that argv0 path before
Tokio/config; the shim handshakes then transparently runs rustc.
>
> **`mise run`** brackets the scheduler with `CacheSession`, passes
session env into the executor, allows sandbox access to shim/socket,
gates **`rust_cache`** behind experimental, and prints action-cache
stats after tasks. Adds **`perf:cache-shim`** (2ms warm overhead budget)
and an e2e session test.
>
> Compiler cache hits/materialization are not implemented yet—the shim
only establishes session shape and benchmarks wrapper cost.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
|
||
|---|---|---|
| .cargo | ||
| .claude/agents | ||
| .codex | ||
| .config | ||
| .cursor | ||
| .entire | ||
| .github | ||
| .idea | ||
| benchmarks | ||
| cloudflare/workers | ||
| completions | ||
| crates | ||
| docs | ||
| e2e | ||
| e2e-win | ||
| licenses | ||
| man/man1 | ||
| packaging | ||
| registry | ||
| schema | ||
| scripts | ||
| share/fish/vendor_conf.d | ||
| src | ||
| test | ||
| vendor/aqua-registry | ||
| xtasks | ||
| .cliffignore | ||
| .coderabbit.yaml | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .markdown-link-check.json | ||
| .markdownlint.json | ||
| .markdownlintignore | ||
| .prettierignore | ||
| .prettierrc.toml | ||
| .release-skip-e2e | ||
| .shellcheckrc | ||
| .taplo.toml | ||
| .yamllint.yml | ||
| age.pub | ||
| AGENTS.md | ||
| build.rs | ||
| bun.lock | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| cliff.toml | ||
| clippy.toml | ||
| communique.toml | ||
| CONTRIBUTING.md | ||
| Cross.toml | ||
| default.nix | ||
| deny.toml | ||
| Dockerfile | ||
| eslint.config.mjs | ||
| flake.lock | ||
| flake.nix | ||
| greptile.json | ||
| hk.pkl | ||
| LICENSE | ||
| llms.txt | ||
| minisign.key.age | ||
| minisign.pub | ||
| mise.code-workspace | ||
| mise.lock | ||
| mise.toml | ||
| mise.usage.kdl | ||
| package.json | ||
| pitchfork.toml | ||
| README.md | ||
| SECURITY.md | ||
| settings.toml | ||
| snapcraft.yaml | ||
| tak.toml | ||
| tasks.md | ||
| tasks.toml | ||
| tsconfig.json | ||
| zipsign.pub | ||
mise-en-place
Dev tools, env vars, and tasks in one CLI
Getting Started • Documentation • Dev Tools • Environments • Tasks
Sponsored by entire.io and 37signals.
View all sponsors.
Tip
My latest project, aube just hit stable! It's the fastest Node.js package manager with strong security defaults and is compatible with npm/pnpm/yarn lockfiles!
What is it?
mise prepares your development environment before each command runs. It keeps
project tools, environment variables, and tasks in one mise.toml file so new
shells, checkouts, and CI jobs all start from the same setup.
- Install and switch between dev tools like node, python, cmake, terraform, and hundreds more.
- Load environment variables per project directory, including values from
.envfiles and other sources. - Define and run tasks for building, testing, linting, and deploying projects.
Demo
The following demo shows how to install and use mise to manage multiple versions of node on the same system.
Note that calling which node gives us a real path to node, not a shim.
It also shows that you can use mise to install and many other tools such as jq, terraform, or go.
See demo transcript.
Quickstart
Install mise
See Getting started for more options.
$ curl https://mise.run | sh
$ ~/.local/bin/mise --version
_ __
____ ___ (_)_______ ___ ____ ____ / /___ _________
/ __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
/ / / / / / (__ ) __/_____/ __/ / / /_____/ /_/ / / /_/ / /__/ __/
/_/ /_/ /_/_/____/\___/ \___/_/ /_/ / .___/_/\__,_/\___/\___/
/_/ by @jdx
2026.8.3 macos-arm64 (2026-08-07)
Hook mise into your shell (pick the right one for your shell):
# note this assumes mise is located at ~/.local/bin/mise
# which is what https://mise.run does by default
echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
echo '~/.local/bin/mise activate fish | source' >> ~/.config/fish/config.fish
echo '~/.local/bin/mise activate pwsh | Out-String | Invoke-Expression' >> ~/.config/powershell/Microsoft.PowerShell_profile.ps1
Execute commands with specific tools
$ mise exec node@26 -- node -v
mise node@26.x.x ✓ installed
v26.x.x
Install tools
$ mise use --global node@26 go@1
$ node -v
v26.x.x
$ go version
go version go1.x.x macos/arm64
See dev tools for more examples.
Manage environment variables
# mise.toml
[env]
SOME_VAR = "foo"
$ mise set SOME_VAR=bar
$ echo $SOME_VAR
bar
Note that mise can also load .env files.
Run tasks
# mise.toml
[tasks.build]
description = "build the project"
run = "echo building..."
$ mise run build
building...
See tasks for more information.
Example mise project
Here is a combined example to give you an idea of how you can use mise to manage your a project's tools, environment, and tasks.
# mise.toml
[tools]
terraform = "1"
aws-cli = "2"
[env]
TF_WORKSPACE = "development"
AWS_REGION = "us-west-2"
AWS_PROFILE = "dev"
[tasks.plan]
description = "Run terraform plan with configured workspace"
run = """
terraform init
terraform workspace select $TF_WORKSPACE
terraform plan
"""
[tasks.validate]
description = "Validate AWS credentials and terraform config"
run = """
aws sts get-caller-identity
terraform validate
"""
[tasks.deploy]
description = "Deploy infrastructure after validation"
depends = ["validate", "plan"]
run = "terraform apply -auto-approve"
Run it with:
mise install # install tools specified in mise.toml
mise run deploy
Find more examples in the mise cookbook.
Full Documentation
See mise.jdx.dev
GitHub Issues & Discussions
Due to the volume of issue submissions mise received, using GitHub Issues became unsustainable for the project. Instead, mise uses GitHub Discussions which provide a more community-centric platform for communication and require less management on the part of the maintainers.
Please note the following discussion categories, which match how issues are often used:
- Announcements
- Ideas: for feature requests, etc.
- Troubleshooting & Bug Reports
Special Thanks
Thanks to Namespace for providing CI services for mise.
