jdx.dev valid

mise-en-place

Dev tools, env vars, and tasks in one CLI

For agents: mise-en-place docs: a CLI that manages dev tool versions such as Node.js, Python and Go per project, plus environment variables and tasks via mise.toml.

misedev toolsenvironment variablestask runnernode.js versioncli

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T02:41:09.715Z. Cached copy · Source on jdx.dev

# mise-en-place

> Dev tools, env vars, and tasks in one CLI

## Start here

- [Getting started](https://mise.jdx.dev/getting-started.html): Install mise, then give a project its own Node.js version, an environment variable and a task. Steps 1 to 3 work without changing your shell configuration; step 4 adds optional shell activation.
- [Installing mise](https://mise.jdx.dev/installing-mise.html): Pick an installation method for your platform, check the executable, then set up your shell. For a guided first project, see Getting started.
- [Shell setup](https://mise.jdx.dev/shell-setup.html): Shell activation hooks your interactive shell so that the current project's tools are on PATH and its environment variables are set each time you change directories or a prompt appears.
- [Existing projects](https://mise.jdx.dev/walkthrough.html): Bring mise into a project you already work on: declare its tools, keep personal settings out of the shared config, share the setup with your team, and run the project's commands through mise.
- [Editors and IDEs](https://mise.jdx.dev/ide-integration.html): An editor's integrated terminal, language servers, debugger and extensions can each run with a different environment. Find out which process needs the tool or variable, then pick an integration.
- [Continuous integration](https://mise.jdx.dev/continuous-integration.html): Use the same mise.toml in CI and development so both environments select the same tools. Run commands with mise exec or mise run to load those tools and the project's environment variables.
- [Docker](https://mise.jdx.dev/mise-cookbook/docker.html): Run mise in a container in one of two ways: build on the -debian image, which has mise, curl and git ready for CI jobs and development containers, or copy the static binary from the scratch image into…
- [AI assistants (MCP)](https://mise.jdx.dev/mcp.html): mise mcp runs a Model Context Protocol server that lets an AI assistant read a project's tools, tasks, environment variables and config files, and run its tasks.

## Dev tools

- [Overview](https://mise.jdx.dev/dev-tools/): mise installs tools such as Node.js, Python, and Go, and selects their versions for each project. Declare the versions a project uses in mise.toml, and mise puts them on PATH while you work in that…
- [Version requests and version files](https://mise.jdx.dev/dev-tools/versions.html): A version request is the value you give a tool in mise.toml, such as "24" in node = "24". mise resolves each request to a concrete version when it runs; record the resolved versions in a lockfile when…
- [Registry](https://mise.jdx.dev/registry.html): The registry maps short tool names such as jq or aws-cli to the backends that install them, so mise use jq works without a full backend identifier.
- [Backends](https://mise.jdx.dev/dev-tools/backends/): A backend is the source mise installs a tool from. It lists the tool's versions, downloads or builds the version you ask for, and tells mise where the
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=jdx.dev · GET /v1/domain/jdx.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for jdx.dev:
1. POST https://agentwebmap.com/v1/sites/jdx.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://jdx.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/jdx.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/jdx.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.