Merge branch 'master' into dependabot/npm_and_yarn/gatsby-5.16.1

Author: saurabhraghuvanshii

src/collections/blog/2026/03-09-why-claude-code-cant-find-your-tools/index.mdx

@@ -16,6 +16,7 @@ featured: false
 published: true
 resource: true
 ---
+
 import { BlogWrapper } from "../../Blog.style.js";
 import { Link } from "gatsby";
 import Blockquote from "../../../../reusecore/Blockquote";
@@ -111,30 +112,30 @@ import KanvasCTA from "../../../../sections/Kanvas/kanvas-cta";
   You can observe this yourself. Run these two commands and compare the output:
 </p>
 
-<pre>
-  <code>{`# What a non-interactive shell sees
+```bash
+# What a non-interactive shell sees
 zsh -c 'echo $PATH'
 
 # What your interactive shell sees
-echo $PATH`}</code>
-</pre>
+echo $PATH
+```
 
 <p>
   On a typical macOS developer machine, the non-interactive shell might produce something like:
 </p>
 
-<pre>
-  <code>{`/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin`}</code>
-</pre>
+```text
+/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
+```
 
 <p>
   While your interactive shell shows something far richer:
 </p>
 
-<pre>
-  <code>{`/opt/homebrew/bin:/opt/homebrew/sbin:/Users/you/.nvm/versions/node/v20.11.0/bin:
-/Users/you/go/bin:/Users/you/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin`}</code>
-</pre>
+```text
+/opt/homebrew/bin:/opt/homebrew/sbin:/Users/you/.nvm/versions/node/v20.11.0/bin:
+/Users/you/go/bin:/Users/you/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
+```
 
 <p>
   All those extra paths — Homebrew, nvm, Go binaries — live in <code>{"~/.zshrc"}</code>, <code>{"~/.zprofile"}</code>, or in scripts those files source. A non-interactive shell never reads any of them.
@@ -146,17 +147,17 @@ echo $PATH`}</code>
   Before changing anything, confirm the symptom. Use <code>zsh -c</code> to simulate what Claude Code sees:
 </p>
 
-<pre>
-  <code>{`# Does Claude Code's shell see the tool?
+```bash
+# Does Claude Code's shell see the tool?
 zsh -c 'which gh'
 zsh -c 'which go'
 zsh -c 'which node'
 
 # Does your interactive shell see it?
 zsh -i -c 'which gh'
 zsh -i -c 'which go'
-zsh -i -c 'which node'`}</code>
-</pre>
+zsh -i -c 'which node'
+```
 
 <p>
   The <code>-i</code> flag forces an interactive shell, which sources <code>{"~/.zshrc"}</code>. If <code>zsh -c 'which gh'</code> prints <code>gh not found</code> but <code>zsh -i -c 'which gh'</code> prints the correct path, your PATH export is in <code>{"~/.zshrc"}</code> and you have confirmed the root cause.
@@ -178,8 +179,8 @@ zsh -i -c 'which node'`}</code>
   Open (or create) <code>{"~/.zshenv"}</code> and add your PATH exports there:
 </p>
 
-<pre>
-  <code>{`# ~/.zshenv
+```bash
+# ~/.zshenv
 # Sourced for every zsh invocation — interactive, login, and non-interactive alike
 
 # Homebrew (Apple Silicon)
@@ -190,23 +191,23 @@ export GOPATH="$HOME/go"
 export PATH="$GOPATH/bin:$PATH"
 
 # Local binaries
-export PATH="$HOME/.local/bin:$PATH"`}</code>
-</pre>
+export PATH="$HOME/.local/bin:$PATH"
+```
 
 <p>
   For tools that inject themselves via an eval expression in <code>{"~/.zshrc"}</code> — such as <code>nvm</code>, <code>pyenv</code>, or <code>rbenv</code> — you need to move or duplicate that initialization into <code>{"~/.zshenv"}</code> as well:
 </p>
 
-<pre>
-  <code>{`# ~/.zshenv — nvm initialization for non-interactive shells
+```bash
+# ~/.zshenv — nvm initialization for non-interactive shells
 export NVM_DIR="$HOME/.nvm"
 [ -s "$NVM_DIR/nvm.sh" ] && source "$NVM_DIR/nvm.sh" --no-use
 
 # pyenv
 export PYENV_ROOT="$HOME/.pyenv"
 export PATH="$PYENV_ROOT/bin:$PATH"
-eval "$(pyenv init --path)"`}</code>
-</pre>
+eval "$(pyenv init --path)"
+```
 
 <p>
   Note the <code>--no-use</code> flag for nvm: it initializes nvm without switching to the default Node.js version, which speeds up shell startup for non-interactive contexts. Remove it if you want the default version active everywhere.
@@ -216,15 +217,15 @@ eval "$(pyenv init --path)"`}</code>
   After saving <code>{"~/.zshenv"}</code>, verify without restarting your terminal:
 </p>
 
-<pre>
-  <code>{`# Reload .zshenv in your current shell
+```bash
+# Reload .zshenv in your current shell
 source ~/.zshenv
 
 # Confirm Claude Code's shell type now finds the tool
 zsh -c 'which gh'
 zsh -c 'which go'
-zsh -c 'which node'`}</code>
-</pre>
+zsh -c 'which node'
+```
 
 <h2>What to Keep in <code>{"~/.zshrc"}</code> vs <code>{"~/.zshenv"}</code></h2>
 
@@ -288,8 +289,8 @@ zsh -c 'which node'`}</code>
   Here is a starting point for a <code>{"~/.zshenv"}</code> that covers the most common developer tools on macOS. Adjust paths to match your actual installations:
 </p>
 
-<pre>
-  <code>{`# ~/.zshenv
+```bash
+# ~/.zshenv
 # Sourced for ALL zsh shells — interactive, login, and non-interactive.
 # Keep this file fast and free of output-producing commands.
 
@@ -322,16 +323,16 @@ fi
 # Editor and locale
 export EDITOR="vim"
 export LANG="en_US.UTF-8"
-export LC_ALL="en_US.UTF-8"`}</code>
-</pre>
+export LC_ALL="en_US.UTF-8"
+```
 
 <p>
   With this in place, restart Claude Code (or any tool that spawns subshells) and run your verification:
 </p>
 
-<pre>
-  <code>{`zsh -c 'which gh && which go && which node'`}</code>
-</pre>
+```bash
+zsh -c 'which gh && which go && which node'
+```
 
 <p>
   All three should now resolve to their correct paths.