patchloom: v0.9.2

Patchloom for VS Code 0.9.2

This release follows Patchloom CLI 0.37.5. Preview and Apply stay on the same text, and the command palette works in a new folder even when the status bar is hidden.

Highlights

Recommended CLI is now 0.37.5. The minimum is still 0.3.0. No settings migration is required.

The extension starts when VS Code finishes starting. A click on the status bar opens Show Status. The full report is in the Output channel.

New features

• The palette stays available. Commands remain in the palette when the status bar is hidden. Patchloom: Refresh Status rechecks the CLI, AGENTS.md, and MCP files (#317).
• Setup Workspace asks once. It confirms the folder, then lists what was already present, what it ran, and what you skipped (#317).
• Workspace MCP files use the command patchloom. A stale absolute path is rewritten. Windsurf can keep the resolved path. patchloom.mcpSurface chooses the full tool list or the 12-tool core pack. Writing .vscode/mcp.json asks first, because that file adds a second server next to the built-in one (#317).
• Preview runs in the workspace. Format config and EditorConfig match Apply. The diff is a patchloom-preview document. Content fields keep newlines. A single-line selection seeds a pattern or anchor. Search hits open from a list. Undo can target the latest backup, a session, or a path (#317).
• Windows npm install -g patchloom works. patchloom.cmd and patchloom.bat launch through cmd.exe. A path that ends in a backslash is quoted so the next argument is not swallowed (#317, #318).

Bug fixes

• A dry run that would change files looked like a failure. Batch Apply, Patch Apply, and Patch Merge treat CLI exit 2 as a successful preview when the JSON says ok: true and nothing has been written yet. The write still requires exit 0. A merge that conflicts stops instead of offering Apply, unless you chose Allow conflict markers (#317).
• An outside patch showed up in source control. Patch apply and patch merge copy that file under .patchloom/, which git already ignores (#318).
• Dismissing the second-server question still wrote other MCP files. Escape cancels Configure MCP. Skip that file still drops only the VS Code workspace file (#318).
• Batch Apply wrote an older plan. If you edit the plan after the dry run, Apply stops and asks for another dry run (#319).
• Apply did not match the preview. Unsaved edits block the preview. If the file changes while the preview is open, Apply stops. A line-ending difference alone does not (#319).

CLI 0.37.5

These show up when the extension runs the recommended CLI (#296).

• Configure MCP still offers 66 tools, or a 12-tool core pack on CLI 0.37+.
• On replace --regex, a replacement group the pattern does not contain is refused and the file stays unchanged.

Numbers

Metric	Previous	Current
Extension version	0.9.1	0.9.2
Recommended CLI	0.37.1 (minimum still 0.3.0)	0.37.5 (minimum still 0.3.0)
MCP tools (CLI full / core)	66 / 12	66 / 12

Upgrading

1. Update the extension to 0.9.2 (VS Code Marketplace, Open VSX, or .vsix from the GitHub Release).
2. Update the Patchloom CLI using the channel that matches how the extension resolved it (see Patchloom: Show Status, Source):

# Managed install (extension storage): command palette
# Patchloom: Update Patchloom

# PATH via Scoop (preferred Windows PATH channel)
scoop update patchloom

# PATH via Homebrew
brew upgrade patchloom

# npm / cargo / shell installer: see README Install section

3. Confirm with Patchloom: Show Status that the detected CLI is 0.37.5 or newer (0.3.0+ still runs; 0.37.5 is recommended).
4. Optional: set patchloom.mcpSurface to full or core, then run Patchloom: Configure MCP.

Install

• VS Code Marketplace
• Open VSX
• GitHub Release assets: patchloom.vsix and build provenance (patchloom.vsix.intoto.jsonl)

Full changelog

patchloom-v0.9.1...patchloom-v0.9.2