[ManushPatel08]

What changed

On Windows, /mission code only said "The code map needs Google Chrome at /Applications/Google Chrome.app/…": the Code view runs Chrome from its macOS path through sh. Fixing the path alone would not help, since Image draws pixels only in kitty, Ghostty and iTerm2, so Windows Terminal would show just the alt text.

On Windows only (macOS takes the same path as before):

• The Code view lists the map as lines: each file's state (● reading, ✎ editing, ✓ changed this turn), the files it imports, and the one-line why.
• b (a Browser button in the Code view) writes the drawn SVG into a page that reloads itself, %TEMP%\mission-control\map.html, and opens it with explorer.exe. Once open, each change redraws it. No Chrome is needed: the browser draws the SVG.
• file_path backslashes become slashes, so titleOf and importsOf work. Before, a file's title was its whole C:\… path and no import resolved.
• Segoe UI and Consolas join the SVG's font stacks.
• README and docs/mods.md notes say what the Code view does on Windows.

Tests:

• New test: on Windows the Code view is lines, b writes and opens the page, and the page follows later changes.
• The test mocks now read paths the way the engine hands them on Windows (/tmp/x arrives as C:\tmp\x), which made two existing tests fail there.
• Run on Windows with Claude Code 2.1.308: claude plugin test mods/mission-control 9 pass; claude plugin validate . and mods/mission-control pass; node --test test/*.test.mjs 33 of 34, and the one failure (the publish workflow regex) fails the same on main in a CRLF checkout.
• I rendered a sample page with headless Chrome to check the picture. Not run on macOS.

Checklist

• claude plugin validate mods/<name> passes
• claude plugin test mods/<name> passes
• Changed a mod: version bumped in its plugin.json and in .claude-plugin/marketplace.json
• New mod: entry in .claude-plugin/marketplace.json
• New mod: README table row and docs/mods.md notes

🤖 Generated with Claude Code

[hamzafer]

Thanks for this, it's a smart way round terminals that show no images. I pushed two commits on top of yours (no force push, your commit is unchanged), so please pull before pushing again:

• Merged main in. fix(mission-control): find Chrome or Chromium on Linux for the code map #135 landed first and touched the same lines. Both notes are kept in docs/mods.md, and the test engine has both sets of options.
• The page now goes straight into %TEMP% (mission-control-map.html). The engine has no way to make folders, so %TEMP%\mission-control\ might not exist on a fresh machine, and b would fail silently. A page that can't be written now shows an error in the pane, and explorer isn't run. New test: on Windows a page that cannot be written says so, and opens nothing.
• Version 0.1.5, plus a Windows line on the site page.

Tests: claude plugin test mods/mission-control 12 pass, validate passes, node --test test/*.test.mjs 36 pass. I can't run Windows here: could you press b on your machine and say if the page opens? That's the last thing before merging.

Not changed, for later: once opened, the page keeps redrawing for the rest of the session, and it reloads every 2 seconds.

[hamzafer]

I merged main in again (normal push, nothing of yours rewritten), so please pull first. #144 had just taken mission-control to 0.1.5, so this PR is now 0.1.6. Both sides are kept: your Windows view plus main's single clock and caught redraws. claude plugin test mods/mission-control 13 pass, node --test test/*.test.mjs 168 pass.

Still the one thing before merging: could you press b on Windows and say if the page opens?