# JD CLI updated: now creates filesystem folders

> Typing `jd 12.34` now creates that folder if it doesn't exist.

The [JD CLI](https://johnnydecimal.com/jdhq/jd-cli) has been updated.

It's migrated from using environment variables to the new [configuration file](https://johnnydecimal.com/jdhq/configuration).

Now if you try to `jd 11.11` to a folder, and that folder doesn't exist, _and_ your JDex is readable by the CLI – i.e. Markdown files on disk, i.e. Obsidian - then it'll create the folder for you.

The [MCP server](https://johnnydecimal.com/jdhq/mcp-server) has been updated to understand this tool and the configuration file. Just ask it to `help me install the jd cli`.

Here's a short video walkthrough.

<div style="padding:56.25% 0 0 0;position:relative;">
  <iframe
    src="https://player.vimeo.com/video/1225173783?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479"
    frameborder="0"
    allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share"
    referrerpolicy="strict-origin-when-cross-origin"
    style="position:absolute;top:0;left:0;width:100%;height:100%;"
    title="W0213 Navigate your filesystem faster with the JD CLI"
  ></iframe>
</div>
<script src="https://player.vimeo.com/api/player.js"></script>

## If you installed the CLI before today

1. Pull:

   ```sh
   git -C ~/.jd/cli pull
   ```

2. In your `.zshrc` or `.bashrc`, find these lines. You might only have the first.

   ```sh
   source ~/.jd/cli/jd-nav/jd-nav.sh
   source ~/.jd/cli/jd-prompt/jd-prompt.zsh
   ```

3. Replace them both with this line.

   ```sh
   source ~/.jd/cli/jd.sh
   ```

4. Start a new shell.