Add Windows install notes for Claude Code

[dem-extra1]

What

Adds a Windows-specific install guide for Claude Code to the AI tools chapter,
as a new subsection under Coding Agents.

Why

Installing Claude Code on Windows has several non-obvious pitfalls that can cost hours.
These notes capture a working setup and the gotchas, based on a real install session:

• Claude Code self-migrates out of npm to ~/.local/bin on first run (paths "disappear").
• MSYS2 doesn't inherit the Windows PATH by default.
• You must rehash (zsh) / hash -r (bash) after changing PATH — especially with oh-my-zsh.
• Don't edit dotfiles with PowerShell >/>> (UTF-16 BOM breaks bash/zsh).
• gh auth login in Git Bash needs winpty.

Changes

• New partial: ai-tools/installing-claude-code-windows.qmd
• New subsection "Installing Claude Code on Windows" wired into ai-tools.qmd

🤖 Generated with Claude Code

[d-morrison]

Claude Code CLI (local session) is working on this — paws off until I'm done.

[d-morrison]

@claude review

[claude]

Claude finished @d-morrison's task in 2m 4s —— View job

---

PR Review

• Load tools
• Read changed files and diff
• Review ai-tools/installing-claude-code-windows.qmd
• Review ai-tools.qmd integration
• Post review findings

---

Overall: This is a well-written, practically useful guide. The prose style is consistent with the rest of the lab manual (short-wrapped lines, callout boxes for warnings), and the technical content accurately captures real Windows gotchas. A few items below worth addressing before merge, ranging from a factual concern down to minor nits.

---

Issues

1. Verify the native installer URL (Medium)

ai-tools/installing-claude-code-windows.qmd, lines 21–25:

curl -fsSL https://claude.ai/install.sh | bash

This URL is presented as the recommended route, above npm. Before merging, please confirm this URL actually exists and serves the Claude Code installer — it's not in the official Claude Code documentation I can verify, and a broken or wrong curl | bash URL is a meaningful hazard. If it's real, a brief link to inspect the script (e.g. "You can view the install script before running it") would address the curl | bash security concern that security-conscious readers often have.

If the URL is uncertain, swapping the order so npm is listed first (with a note that the binary will self-migrate on first run) would be safer. Fix this →

2. WSL is mentioned but not covered (Low)

ai-tools/installing-claude-code-windows.qmd, lines 16–19:

- **WSL** (Windows Subsystem for Linux), the most Unix-faithful option.

If you use WSL,
install Claude Code *inside* WSL…

WSL is introduced as the "most Unix-faithful option" and then the guide says nothing more about it — all the subsequent PATH, rehash, dotfile, and winpty guidance applies to Git Bash / MSYS2, not WSL. A WSL user following this guide would get a recommendation to use the best option, then instructions that don't apply to them.

Suggest either: (a) add a brief WSL note ("In WSL, standard Linux install instructions apply — the sections below cover Git Bash and MSYS2 only"), or (b) remove WSL from the terminal-options list so the scope is clear up front. Fix this →

---

Minor / Nits

3. $HOME variability in MSYS2

ai-tools/installing-claude-code-windows.qmd, lines 67–73:

The note that $HOME in MSYS2 is /home/<you> (not C:\Users\<you>) is accurate for the default MSYS2 setup, but MSYS2 can be configured to inherit the Windows home directory (via MSYS2_PATH_TYPE=inherit or a custom nsswitch.conf). The existing advice — use the absolute Windows path to be safe — is the right call regardless, so no change is strictly needed, but acknowledging "depending on your MSYS2 configuration" would prevent confusion for users who've configured MSYS2 otherwise.

4. Section placement

The new ### Installing Claude Code on Windows section is appended after a run of GitHub Copilot-specific sections. This works for now, but as Claude Code coverage grows, it may feel orphaned. This is not a blocker — just something to keep in mind for chapter organization as the AI tools chapter evolves.

5. "Written in June 2026" callout

The callout at the top says "written in June 2026." This is fine, and the existing chapter already uses "as of early 2026" phrasing. No change needed — just noting that the existing chapter-level callout already covers this.

---

ai-tools.qmd integration

The four-line addition (+4/-0) looks correct: the heading level (###) matches the surrounding sections, the section ID {#sec-claude-code-windows} follows the project's convention, and the {{< include >}} syntax is valid. No issues here.

---

Summary: One factual item to verify (the install script URL) and one scope gap to clarify (WSL coverage), then this is ready. The writing quality and Quarto mechanics are solid.