v0.14.0 — ripples on the water

Two things, one small and delightful, one small and important.

Standby splash (#1, first community contribution — thanks @Sch2048 🎉): before any map exists the pane now shows a MELLOS / MAPPING wordmark lit by interfering ripples — damped rings born at randomized corners, summed for real interference, driving one indigo→cyan→white ramp. Fully deterministic (no Math.random), TTY-only, and --no-color --ascii still ripples in shade characters.

Multi-page store made explicit in the docs: a field report showed an agent probing .claude/mellos-mapping.json, finding nothing, and announcing "no map yet" — while the pane was correctly rendering named pages from .claude/mellos-mapping.pages/. The store has been multi-page since 0.7.0; now commands/mmap.md and the skill say so, and direct agents to mmap_view for existence checks instead of probing paths.

(v0.13.0's window-targeting launcher ships here too if you're coming from 0.12.x: the pane opens in the terminal window hosting YOUR session, --window for a dedicated window.)

v0.13.0 — the pane lands in YOUR window

The map pane now opens beside the conversation that asked for it — even with several Windows Terminal windows open.

Why it went wrong before: the agent's shell isn't attached to your terminal window (no WT_SESSION), so wt -w 0 sp split the most recently used window — i.e. wherever you last clicked.

What's new

• scripts/open-pane.mjs: identifies the WT window hosting the session (ancestor walk + AttachConsole + a console-title nonce — the nonce only lights up when the session tab is the window's active tab, so identification doubles as the split precondition), brings it to the foreground through a verified cascade (plain SetForegroundWindow → Alt-key unlock → AttachThreadInput), and only then splits.
• Deterministic fallback: if the window can't be identified or focused (tab inactive, screen locked, not hosted in WT), the map opens in a dedicated window named mellos-mapping — never a random window.
• --window: open the dedicated window on purpose (map on a second monitor, separate from the chat).
• One watcher per map file: repeated /mmap no longer piles up panes (--force overrides).

/mellos-mapping:mmap and the Codex/manual routes all go through the launcher on Windows; tmux and printed-command routes are unchanged.

v0.12.0 — npm-ready, animated demo, CI

Highlights

• Animated demo in the README — the whole discipline in 16 seconds: ghost design → spinners climbing the layers → all green → a cracked foundation spreading upward → honest recovery. Generated from the real renderer (scripts/demo-svg.mjs), no screen recording.
• npm-ready package: bin entries for the MCP server and the watch pane, real-path entry guards so npx symlink launches work, shebangs in the bundles, metadata complete. Publishing to npm makes any MCP client a one-liner: npx -y mellos-mapping.
• CI on three OSes (ubuntu / macos / windows): typecheck + 152 tests + build, plus a guard that the committed dist/ is exactly the build of the committed src/.
• scripts/release.mjs bumps all five version sites atomically and gates on the full verify.
• server.json drafted for the official MCP registry.

Install

Claude Code:

/plugin marketplace add GuangminJu/mellos-mapping
/plugin install mellos-mapping@mellos-mapping

Codex CLI:

codex plugin marketplace add GuangminJu/mellos-mapping
codex plugin add mellos-mapping@mellos-mapping
node ~/.codex/plugins/cache/mellos-mapping/mellos-mapping/0.12.0/scripts/codex-register.mjs