patchloom: v0.7.0

Patchloom for VS Code 0.7.0

This release aligns the extension with Patchloom CLI 0.33.0. You can list object keys and count structured length from the Quick Action picker, and the docs match dest glob rules on the current CLI.

Highlights

Recommended CLI is now 0.33.0. Two new read-only Quick Actions run doc keys and doc len (CLI 0.32+). Search dests such as *.txt match the current directory only; use --glob when you want nested files.

Minimum supported CLI remains 0.3.0. No settings migration is required.

New features

• List structured keys. Quick Action runs patchloom doc keys (CLI 0.32+) on a JSON, YAML, or TOML file. Use . for the document root. An array at that selector is a type error; a wildcard or predicate is ambiguous (#265).
• Count structured length. Quick Action runs patchloom doc len (CLI 0.32+) and reports how many array items or object keys sit at the selector (#265).
• CLI 0.33 dest globs. A dest such as *.txt is the current directory only. sub/*.txt stays in that directory. Use **/*.txt or Search --glob for nested files. YAML merge-key edits on CLI 0.32+ keep <<: and comments (#265).

Numbers

Metric	Previous	Current
Extension version	0.6.0	0.7.0
Recommended CLI	0.31.0 (minimum still 0.3.0)	0.33.0 (minimum still 0.3.0)
Unit tests	431 passed, 7 skipped	433 passed, 9 skipped
MCP tools (CLI 0.33 full / core)	58 / 11	58 / 11

The extra skipped tests are version gates for doc keys / doc len and dest globs when the CLI on PATH is older than 0.32 / 0.33.

Upgrading

1. Update the extension to 0.7.0 (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.33.0 or newer (0.3.0+ still runs; 0.33.0 is recommended). The new Quick Actions need CLI 0.32.0+.
4. Optional: from the Quick Action picker, run List structured keys or Count structured length on a JSON, YAML, or TOML file. Use . for the document root.

Install

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

Full changelog

patchloom-v0.6.0...patchloom-v0.7.0

patchloom: v0.6.0

Patchloom for VS Code 0.6.0

This release adds Quick Actions for multi-match document edits and applying a patch file. It also fixes Native MCP registration and Configure MCP so the CLI shows up in VS Code and Cursor without wiping existing config.

Highlights

Three new Quick Actions cover updating or deleting matching JSON, YAML, or TOML nodes, and applying a unified diff, Codex Begin Patch, or Aider SEARCH/REPLACE. Native MCP now registers in VS Code 1.100+ and runs in the open workspace folder. Configure MCP keeps JSONC comments and writes Cursor's mcpServers key.

Minimum supported CLI remains 0.3.0. Recommended CLI is still 0.31.0. No settings migration is required.

New features

• Update matching structured values. Quick Action runs patchloom doc update (CLI 0.27+) to change every JSON, YAML, or TOML node that matches a wildcard or predicate, with the same preview-then-apply flow as other document edits (#246).
• Delete matching array items. Quick Action runs patchloom doc delete-where (CLI 0.27+) with an array path plus a key=value predicate. A miss is treated as a hard failure, not a silent no-op (#246).
• Apply patch (unified / Begin Patch / SEARCH-REPLACE). Quick Action runs patchloom patch apply (CLI 0.30+) on a unified diff, Codex *** Begin Patch, or Aider SEARCH/REPLACE file. Merge patch remains the three-way path for stale unified diffs (#246).

Bug fixes

• Native MCP never appeared in VS Code 1.100+. The provider called a method name that does not exist, so registration did nothing. It now registers a stdio server with the resolved CLI path and only PATCHLOOM_* environment keys (#249, #250).
• Native MCP tools resolved relative paths from your home directory. The server working directory is now the first workspace folder (#251).
• Configure MCP wiped comments and sibling servers in JSONC. A parse failure used to become an empty object and then a rewrite. Invalid files are refused; valid JSONC keeps comments and other servers (#248).
• Cursor wrote VS Code's servers key. .cursor/mcp.json now uses mcpServers. A Cursor file that only has servers is no longer treated as already configured (#252, #253).
• A broken patchloom.path kept offering Install. When the setting points at a missing or outdated binary, the status action is Open Settings, not a managed Install or Update (#249).
• Update Patchloom compared the latest release to the active PATH or settings binary. Managed Update now compares GitHub latest to the binary in extension storage (#244).
• A path or value of --apply or --contain dropped workspace sandboxing or turned a confirmed apply into a dry run. Those tokens stay operands. Files named --apply and option values such as -n are passed so the CLI does not treat them as flags (#254, #256, #257).
• A workspace symlink to an outside patch escaped --contain. Apply now follows the real path and stages an outside target under .patchloom-* so the write sandbox stays on (#247).
• Search failures stayed in a toast. Errors now also write the CLI text to the Patchloom output channel (#244).

Numbers

Metric	Previous	Current
Extension version	0.5.0	0.6.0
Recommended CLI	0.31.0 (minimum still 0.3.0)	0.31.0 (minimum still 0.3.0)
Unit tests	373 passed, 6 skipped	431 passed, 7 skipped
MCP tools (CLI 0.31 full / core)	58 / 11	58 / 11

Upgrading

1. Update the extension to 0.6.0 (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.31.0 or newer (0.3.0+ still runs; 0.31.0 is recommended). The new Quick Actions need CLI 0.27.0+ for doc update / doc delete-where and 0.30.0+ for patch apply.
4. Optional: run Configure MCP if you use Cursor or a commented .vscode/mcp.json, then Update matching structured values or Apply patch (unified / Begin Patch / SEARCH-REPLACE) from the Quick Action picker.

Install

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

Full changelog

patchloom-v0.5.0...patchloom-v0.6.0

patchloom: v0.5.0

Patchloom for VS Code 0.5.0

This release tracks Patchloom CLI 0.31.0: recommended binary bump, a Search files without match Quick Action, and Output-channel results that no longer depend on turning on CLI trace.

Highlights

Recommended CLI is 0.31.0. Search, undo, patch-merge, and batch apply now write their results (and failures) to the Patchloom output channel even when patchloom.trace.server is off. Native MCP stays registered if you install the CLI after the window opens, and it follows patchloom.path or trust changes without a reload.

Minimum supported CLI remains 0.3.0. No settings migration is required.

Aligned with Patchloom CLI 0.29–0.31

You do not need every CLI feature to use the extension. These matter if you upgrade the binary from 0.28.x:

CLI	What you get with a current managed install
0.29	search -L / files_without_match; agent-rules --surface core honors --mode
0.30	Numeric selectors (servers[port>8000]); patch apply accepts unified diffs, Codex *** Begin Patch, and Aider SEARCH/REPLACE
0.31	YAML alias-to-merge on doc set; create/rename report parent path is not a directory when a parent is a file

MCP stays 58 tools full and 11 in the core pack. search_files accepts files_without_match. Workspace Quick Actions and Batch Apply still pass global --contain.

New features

• CLI 0.31 alignment. Recommended version, requirements, troubleshooting, and MCP docs cover 0.29–0.31 peels (#234).
• Search files without match. Quick Action runs patchloom search -L (CLI 0.29+) to list files that do not contain the pattern (#234).
• Native MCP after first-run Install. The MCP provider registers even when the CLI is missing at activate, then picks up the binary after Install / Update / Reinstall. Changing patchloom.path or granting workspace trust refreshes that path without reloading the window (#238, #241).

Bug fixes

• Search, undo, and patch merge opened an empty Output channel. With the default trace.server of off, those commands told you to check Output and then showed nothing. Success, patch-merge conflicts (exit 8), hard errors, and Batch Apply now write stdout/stderr there. Settings text no longer implies every CLI stream is trace-gated (#237, #238).
• First open ran --version three times. Status bar, auto-update, and native MCP now share one in-flight probe. Settings, trust, and managed install drop that probe before they refresh so a long cold start cannot pin a stale path (#240, #241).
• Empty Batch Apply could report success. A whitespace-only plan now warns and does not run the CLI (#238).

Improvements

• Safer workspace env overlay. patchloom.env only forwards PATCHLOOM_* keys. Workspace values are ignored in an untrusted folder. Loader keys such as PATH and LD_PRELOAD are dropped (#236).
• Patch merge --contain. When the patch file itself lives inside the workspace, merge uses the same write sandbox as other Quick Actions. Filenames that start with .. stay inside the folder (#236).
• Managed install redirects. Followed Location headers must stay on GitHub or known GitHub release CDN hosts (#238).
• Clearer next-step hints. Fail-closed doc errors now say try doc.update instead of suggested_op: doc.update (#238).
• UI tests compile in CI. ExTester sources are compiled before the UI suite so that job is no longer a no-op (#236).

Numbers

Metric	Notes
Extension version	0.4.0 → 0.5.0
Recommended CLI	0.28.0 → 0.31.0 (minimum still 0.3.0)
Unit tests	373 passed, 6 skipped (node:test unit suite on this release)
MCP tools (CLI 0.31 full / core)	58 / 11

Upgrading

1. Update the extension to 0.5.0 (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.31.0 or newer (0.3.0+ still runs; 0.31.0 is recommended).
4. Optional: run Search files without match, then Patchloom: Show Output, with patchloom.trace.server left at off. You should see the file list in the channel.

Install

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

Full changelog

patchloom-v0.4.0...patchloom-v0.5.0

patchloom: v0.4.0

Patchloom for VS Code 0.4.0

This release tracks Patchloom CLI 0.28.0: recommended binary bump, clearer agent-facing error hints (suggested_op, empty paths, non-regular files), better upgrade actions by install source, and Windows install guidance that prefers managed install and Scoop over lagging community packages.

Highlights

• Recommended CLI is 0.28.0. Managed Install / Update Patchloom still download the latest GitHub release with checksum verification. Minimum supported CLI remains 0.3.0.
• Smarter upgrade actions. Status and command warnings pick the action that can actually fix your active binary: Update for managed installs, Open Settings for patchloom.path, Open Releases for PATH installs. Managed Update no longer pretends to replace an outdated PATH binary.
• Richer CLI error peels in the UI. Failure messages still prefer JSON error / error_kind, and now append suggested_op when the CLI provides it (for example multi-match doc.update after a fail-closed doc.set).
• Windows install path. Prefer the extension managed installer or Scoop. Winget and Chocolatey are called out as lagging channels; do not use them when you need the latest CLI the same day.

CLI 0.28 still exposes 58 MCP tools by default (11 in the core pack). No settings migration is required.

Aligned with Patchloom CLI 0.25–0.28

You do not need every CLI feature to use the extension. These matter if you upgrade the binary from 0.24.x:

CLI	What you get with a current managed install
0.25	Clearer create/rename peels; ambiguous markdown headings report error_kind: ambiguous
0.26	Multi-path specials (FIFOs and similar) report refused[].reason: not_regular_file instead of looking like a permission error
0.27	Fail-closed doc navigation may include suggested_op (doc.update or doc.delete_where) so agents and the extension can hint the multi-match sibling
0.28	Empty, whitespace-only, or format-character-only paths fail early with error_kind: invalid_input and message path must not be empty

Workspace Quick Actions and Batch Apply still pass global --contain. Patch merge still skips containment when the patch file may live outside the project.

New features

• CLI 0.28 alignment. Recommended version, requirements, troubleshooting, and MCP counts updated for 0.25–0.28 peels; Batch Apply template includes multi-match doc.update next to doc.set (#226).
• Shared binary remediation. Missing or broken CLI prompts use one path for status and commands: Install, Reinstall, Update, Settings, or Open Releases depending on source and managed storage (#228, #229).

Bug fixes

• Managed Update for an outdated PATH CLI left you stuck. Resolution order is still setting, then PATH, then managed. Offering Install/Update managed when the active binary came from PATH or patchloom.path could refresh storage without changing what the extension runs. Upgrade actions now follow the active source (#229).
• Missing binary only offered Open Settings. When managed install is available, status and command warnings prefer Install Patchloom or Reinstall Patchloom instead of sending you only to settings (#228).

Improvements

• suggested_op in Output and notifications. When the CLI returns a multi-match hint on fail-closed doc navigation, the extension surfaces it next to the error text (#226).
• Windows and upgrade docs. Install and troubleshooting prefer managed install and Scoop; document Scoop/scoop update for PATH upgrades and managed Update for storage installs (#226, #229).
• Dependency hygiene. Cleared high npm audit findings (including brace-expansion override pin) and bumped publishing/test tooling used in CI (#228, #229, #223, #224, #225).

Numbers

Metric	Notes
Extension version	0.3.0 → 0.4.0
Recommended CLI	0.24.0 → 0.28.0 (minimum still 0.3.0)
Unit tests	313 (node:test unit suite on this release)
MCP tools (CLI 0.28 full / core)	58 / 11

Upgrading

1. Update the extension to 0.4.0 (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.28.0 or newer (0.3.0+ still runs; 0.28.0 is recommended).
4. Optional: open Batch Apply and try the doc.update example, or trigger a command with an outdated PATH binary and confirm the status action points at Open Releases rather than a no-op managed update.

Install

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

Full changelog

patchloom-v0.3.0...patchloom-v0.4.0

patchloom: v0.3.0

Patchloom for VS Code 0.3.0

This release tracks Patchloom CLI 0.24.0: recommended binary bump, Morph-style Apply fragment at anchor, agent-rules and MCP core pack options, and clearer CLI error kinds in the UI.

Highlights

• Recommended CLI is 0.24.0. Managed install and Update Patchloom still pull the latest GitHub release. Minimum supported CLI remains 0.3.0.
• Apply fragment at anchor. New Quick Action for apply-fragment (CLI 0.22+): place a freeform fragment with a unique --after, --before, or --old anchor. Morph-style marker lines are stripped. Same diff preview and Apply flow as other write actions.
• Agent-rules surface. Initialize Project can generate a full AGENTS.md document or a short core pack for system-prompt injection (patchloom agent-rules --surface core, CLI 0.24+).
• MCP core pack. Configure MCP can inject the full tool inventory or set PATCHLOOM_MCP_SURFACE=core on the server entry (11 tools on CLI 0.24, including list_files).
• Clearer sole-path and fuzzy errors. Failure messages still prefer CLI JSON error / error_kind. New kinds you may see with a current CLI include binary, invalid_encoding (0.20+), and fuzzy_span_suspicious (0.22+), plus existing already_exists (0.19+) and guard_rejected (0.18+).

CLI 0.24.x exposes 58 MCP tools by default (including list_files and apply_fragment). No settings migration is required. Existing patchloom.path values and managed installs keep working.

Aligned with Patchloom CLI 0.19–0.24

You do not need every CLI feature to use the extension. These are the parts that matter if you upgrade the binary from 0.18.x:

CLI	What you get with a current managed install
0.19	error_kind: already_exists on create/rename conflicts; clearer force hints
0.20	error_kind: binary and invalid_encoding for sole-path non-text loads
0.22	apply-fragment / MCP apply_fragment; fuzzy_span_suspicious on over-wide fuzzy matches; PATCHLOOM_MCP_SURFACE=core (originally 10 tools)
0.23	MCP server_info reports package and protocol versions; WinGet install path documented
0.24	MCP list_files; core pack grows to 11 tools; absolute paths allowed when they resolve inside the MCP workspace root

Workspace Quick Actions and Batch Apply still pass global --contain. Patch merge still skips containment when the patch file may live outside the project. apply-fragment is CLI/tx/MCP only (not batch line format).

New features

• Apply fragment at anchor. Palette action builds apply-fragment <file> --after|--before|--old <anchor> --fragment <text> with preview before apply (#218).
• Initialize Project surface picker. Choose full agent-rules document or core pack (--surface core) alongside mode and platform (#219).
• Configure MCP surface picker. Full inventory (default) or core pack via PATCHLOOM_MCP_SURFACE=core in the generated editor config (#219).

Improvements

• Docs for CLI 0.19–0.24. Recommended version, requirements blurb, troubleshooting for binary/encoding/fuzzy peels and already_exists, MCP tool counts, WinGet install, and walkthrough steps for surface/core options (#217, #218, #219).
• Dependency hygiene. Cleared remaining brace-expansion audit pressure under mocha; Actions and test-electron Dependabot bumps (#217, #215, #216).
• Release merge guard. Scripts no longer claim a PR is safe to merge after an intentional release override; release-please PRs still need an explicit go-ahead (#213).

Upgrading

1. Update the extension to 0.3.0 (VS Code Marketplace, Open VSX, or .vsix from the GitHub Release).
2. Update the Patchloom CLI when you can:

# Managed install from the command palette:
# Patchloom: Update Patchloom

# Or install/upgrade via your preferred channel, then reopen VS Code
brew upgrade patchloom
# npm: npm install -g patchloom
# Scoop / Chocolatey / WinGet / cargo / shell installer: see README Install section

3. Confirm with Patchloom: Show Status that the detected CLI is 0.24.0 or newer (0.3.0+ still runs; 0.24.0 is recommended).
4. Optional: try Apply fragment at anchor on a short source file, regenerate AGENTS.md with surface Core pack, or re-run Configure MCP and pick Core pack for coding agents that prefer a small tool list.

Install

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

Full changelog

patchloom-v0.2.0...patchloom-v0.3.0

patchloom: v0.2.0

Patchloom for VS Code 0.2.0

This release brings the extension in line with Patchloom CLI 0.18.0: multi-document YAML merge from the palette, line-oriented insert Quick Actions, clearer CLI errors in the UI, and docs that match how batch plans and workspace containment work today.

Highlights

• Recommended CLI is 0.18.0. Managed install and Update Patchloom still pull the latest GitHub release. Minimum supported CLI remains 0.3.0.
• Multi-doc YAML merge. Merge into structured file accepts an optional document selector and runs doc merge --selector (CLI 0.16+), so you can merge into document 0 without wiping a multi-document stream.
• Insert before / after match. Two new Quick Actions use line-oriented replace --insert-before and --insert-after (CLI 0.16+), with the same diff preview and Apply flow as replace.
• Clearer CLI errors in the UI. Failure messages prefer the CLI JSON error / error_kind fields. Containment failures show as guard_rejected (CLI 0.18+) instead of a raw multi-line dump.
• Batch plans match modern CLI. The Batch Apply template includes multi-doc doc.merge, line-oriented insert-after, and fuzzy replace. Docs spell out the batch shape: replace PATH OLD NEW (not the CLI replace OLD --new NEW path form).

MCP servers started through the extension still use patchloom mcp-server. Current CLI 0.18.x exposes 56 tools, same as the 0.15 era tool surface the extension already targeted.

No settings migration is required. Existing patchloom.path values and managed installs keep working.

Aligned with Patchloom CLI 0.16–0.18

You do not need every CLI feature to use the extension. These are the parts that matter if you upgrade the binary from 0.15.x:

CLI	What you get with a current managed install
0.16	Multi-doc doc merge --selector, line-oriented insert_before / insert_after, shared binary / invalid UTF-8 path reporting
0.17	Clearer sole-path load errors and stable error_kind on more multi-file failure paths
0.18	error_kind: guard_rejected when --contain rejects a path; clearer batch replace parse hints (PATH OLD NEW)

Workspace Quick Actions and Batch Apply still pass global --contain so paths stay inside the open folder. Patch merge still skips containment when the patch file may live outside the project.

New features

• Multi-document merge selector. Optional selector prompt on Merge into structured file builds doc merge <file> --selector <path> --value <json> when set, and omits --selector for ordinary root merges. (#207)
• Insert text after match. Quick Action for line-oriented insert after each match. (#209)
• Insert text before match. Quick Action for line-oriented insert before each match. (#209)
• Richer Batch Apply template. Default plan includes fuzzy replace, --insert-after=…, multi-doc doc.merge … 0, markdown section insert, and tidy. (#207, #209)

Improvements

• JSON-aware CLI error display. Notifications and failure strings prefer the CLI error field (and error_kind when the message does not already include it), so agents and humans see guard_rejected and batch parse hints cleanly. (#210)
• Docs for CLI 0.18. Recommended version, requirements blurb, troubleshooting for workspace guard rejections, and batch PATH OLD NEW guidance. (#210)
• Quick Actions documentation. Full palette table in the README, including Chocolatey install notes and multi-doc merge. (#205, #207, #209)
• Dependency hygiene. Transitive high-severity npm audit findings cleared (brace-expansion, fast-uri, js-yaml, linkify-it). GitHub Actions CodeQL pin updated via Dependabot. (#206, #209)

Upgrading

1. Update the extension to 0.2.0 (VS Code Marketplace, Open VSX, or .vsix from the GitHub Release).
2. Update the Patchloom CLI when you can:

# Managed install from the command palette:
# Patchloom: Update Patchloom

# Or install/upgrade via your preferred channel, then reopen VS Code
brew upgrade patchloom
# npm: npm install -g patchloom
# Scoop / Chocolatey / cargo / shell installer: see README Install section

3. Confirm with Patchloom: Show Status that the detected CLI is 0.18.0 or newer (0.3.0+ still runs; 0.18.0 is recommended).
4. Optional: try Merge into structured file with selector 0 on a multi-doc YAML file, or Insert text after match on a short text file.

Install

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

patchloom: v0.1.0

Patchloom for VS Code 0.1.0

This is the first 0.1 release of the official VS Code extension for
Patchloom. It pairs the extension
with Patchloom CLI v0.15.2:
more install options, a new markdown Quick Action, clearer Batch Apply
examples, and docs that match the current CLI and MCP surface.

Highlights

• Recommended CLI is 0.15.2. Managed install and Update Patchloom
  still pull the latest GitHub release. Minimum supported CLI remains 0.3.0.
• Insert after section. New Quick Action for md insert-after-section
  (CLI 0.14+): place a sibling markdown section after a full section body,
  not just under the heading line.
• Easier CLI installs. README and Getting Started walkthrough cover
  Homebrew, npm (npm install -g patchloom / npx), Scoop (Windows),
  cargo, and the shell installer, in addition to Install Patchloom.
• Batch plans that match modern CLI. The Batch Apply template includes
  fuzzy replace with --min-fuzzy-score and md.insert_after_section.

MCP servers started through the extension still use patchloom mcp-server.
With CLI 0.15.x that exposes 56 tools (up from 54 in the 0.10 era).

Why 0.1.0

0.0.x covered the full setup path (managed CLI, agent rules, multi-editor
MCP, Quick Actions, Batch Apply, status bar, verify). 0.1.0 is the same
product, now versioned as a stable minor line and aligned with current
Patchloom CLI practice for agent and workspace use.

No settings migration is required. Existing patchloom.path values and
managed installs keep working.

Aligned with Patchloom CLI 0.11–0.15

You do not need every CLI feature to use the extension. These are the
parts that matter if you upgrade the binary:

CLI range	What you get with a current managed install
0.11–0.13	Stronger --contain coverage, clearer plan/batch errors, match reporting on replace
0.14	md insert-after-section, batch flags such as --fuzzy / --min-fuzzy-score, more install channels (npm, Scoop, Chocolatey)
0.15	Stable MCP and JSON contracts (selector on doc tools, applied on write results), 56 MCP tools

Workspace Quick Actions and Batch Apply still pass global --contain so
paths stay inside the open folder. Containment follows the effective
working directory (the workspace folder). Patch merge still skips
containment when the patch file may live outside the project.

New features

• Insert after section. From Patchloom: Quick Action, insert
  sibling content after a full markdown section (for example a ## FAQ
  after ## Config without stuffing text under the Config heading).
  Same diff preview and Apply flow as other markdown actions. (#198)
• Richer Batch Apply template. Default plan lines demonstrate fuzzy
  replace and md.insert_after_section alongside replace, doc.set,
  file.append, and tidy.fix. (#198)
• Install docs for npm and Scoop. Getting started and the walkthrough
  list the channels Patchloom publishes today, so Windows and Node users
  have a clear path when they are not using Homebrew. (#198)

Improvements

• Docs match live CLI/MCP contracts. Recommended version, tool count,
  and capability descriptions track CLI 0.15.2. Command shapes used by
  the extension (replace with --new, doc selectors, MCP selector,
  agent-rules mode/platform, line-oriented batch) were re-checked
  against that release. (#198)
• Initialize Project and Batch Apply tests. Extra coverage for
  agent-rules mode/platform picks and for Batch Apply always invoking
  batch with global --contain. (#192)

Upgrading

1. Update the extension to 0.1.0 (VS Code Marketplace, Open VSX, or .vsix).
2. Update the Patchloom CLI when you can:

# Managed install (Command Palette)
# Patchloom: Update Patchloom

brew upgrade patchloom

npm install -g patchloom

scoop update patchloom

curl -LsSf https://github.com/patchloom/patchloom/releases/latest/download/patchloom-installer.sh | sh

3. If you use MCP in VS Code, Cursor, or Windsurf, restart the MCP host
   after a CLI upgrade so tool lists and schemas refresh.
4. Optional: run Setup Workspace or Initialize Project if you want
   a fresh AGENTS.md for the current CLI guidance.

CLI version guidance

Level	Version	Notes
Minimum	0.3.0	Older builds may miss commands the extension offers
Recommended	0.15.2+	Current MCP tool set, markdown section insert, fuzzy batch flags, path containment

Requirements

• VS Code 1.90 or newer (or compatible editors: Cursor, Windsurf, VSCodium)
• Patchloom CLI 0.3.0 or newer (0.15.2+ recommended)

Links

• Extension: VS Code Marketplace · Open VSX
• CLI release: patchloom-v0.15.2
• Issues: patchloom/patchloom-vscode

patchloom: v0.0.9

Patchloom for VS Code 0.0.9

This release aligns the extension with Patchloom CLI v0.10.0: safer workspace CLI runs, a working Create file action on current CLI builds, and a few high-value Quick Action and Initialize Project improvements.

Highlights

• Create file actually creates files on CLI 0.9+ and 0.10+. The action now collects initial content and always passes --apply (preview-only create returns exit code 2 and does not write).
• Workspace path guarding for Quick Actions and Batch Apply via CLI --contain (0.10+), so edits stay inside the open folder.
• Prepend to file Quick Action (CLI 0.9+) and richer Initialize Project options for agent-rules mode and platform.

Recommended CLI: 0.10.0+ (minimum remains 0.3.0). Managed install and Marketplace auto-update pull the latest CLI when available.

Aligned with Patchloom CLI v0.10

CLI 0.8–0.10 added agent reliability features the extension now tracks:

CLI	What matters for the extension
0.8	54 MCP tools (up from 43), server_info, better tool discovery
0.9	File prepend command; MCP doc params use selector (not key)
0.10	Preview exit code 2 when changes would apply; optional global --contain

Docs and tests follow those contracts so the extension stays compatible with the latest managed CLI install.

New features

• Prepend to file. Quick Action for patchloom prepend <file> --content <text> with the same diff preview and Apply flow as Append. (#189)
• --contain on workspace edits. Quick Actions and Batch Apply run the CLI with global --contain so paths cannot escape the workspace root. Patch merge opts out so you can still apply a patch file stored outside the project. (#189)
• Initialize Project mode and platform. When generating or diffing AGENTS.md, pick integration mode (all / CLI only / MCP only) and shell platform (all / Linux-macOS / Windows) for patchloom agent-rules. (#189)

Bug fixes

• Create a new file. Previously the action ran patchloom create <path> without --content or --apply. Current CLI requires content (or stdin) and only writes when --apply is set. You are prompted for initial content (empty is allowed), then the file is created and opened. (#188)
• MCP doc_set e2e against latest CLI. Managed-install end-to-end tests use the selector parameter for doc_set (CLI 0.9+), matching production MCP schema. (#185)

Upgrading

1. Update the extension to 0.0.9 (Marketplace, Open VSX, or VSIX).
2. Update the CLI to 0.10.0+ if you can:

brew upgrade patchloom
# or
cargo install patchloom --locked
# or
# Command Palette: Patchloom: Update Patchloom

3. Re-run Patchloom: Setup Workspace or Initialize Project if you want fresh agent rules with the new mode/platform choices.
4. For MCP in Cursor/VS Code/Windsurf, Configure MCP is unchanged; restart the MCP host after a CLI upgrade so tool lists refresh.

No settings migration is required. Existing patchloom.path and managed installs continue to work.

patchloom: v0.0.8

Patchloom for VS Code

This release aligns the extension with Patchloom CLI v0.7.0 and completes platform parity for the managed installer.

Aligned with Patchloom CLI v0.7.0

v0.7.0 renamed CLI arguments to match what LLMs naturally generate. The extension's Quick Action Replace text now uses the v0.7.0 syntax (patchloom replace <old> --new <new> <file>), and the MCP e2e test suite is updated for the selector to key parameter rename in doc tools.

If you use the Replace quick action, update the CLI to v0.7.0+ before upgrading the extension.

Full platform parity for managed install

The managed installer now covers all 8 targets shipped by the CLI. Three new platforms added in this release:

Target	Use case
aarch64-pc-windows-msvc	Windows ARM64 (Surface Pro X, Snapdragon laptops)
x86_64-unknown-linux-musl	Alpine dev containers, musl-based CI runners
aarch64-unknown-linux-musl	Alpine ARM64 dev containers

Musl detection is automatic: the extension checks for /lib/ld-musl-<arch>.so.1 and downloads the correct binary. No configuration needed.

Install or update the CLI

brew upgrade patchloom                  # Homebrew
cargo install patchloom                 # from source

Or run Patchloom: Update Patchloom from the VS Code command palette if you use the managed installer.

patchloom: v0.0.7

Patchloom for VS Code

This release aligns the extension with Patchloom CLI v0.6.0, the biggest CLI release to date: 41 PRs, 112 files changed, and 1,816 tests.

What's new in the CLI

11 AST tools for code-aware agents

The CLI's MCP server now exposes 43 tools (up from 32), with 11 new AST tools powered by tree-sitter:

Tool	What it does
ast_list	List symbol definitions (functions, classes, structs) across 20 languages
ast_read	Read a specific symbol's source code by name
ast_rename	Rename identifiers across files (skips strings and comments)
ast_validate	Check syntax and report parse errors with line numbers
ast_search	Structural search using tree-sitter queries and code patterns
ast_refs	Find all references to a symbol, distinguishing definitions from uses
ast_deps	Extract import/dependency statements from source files
ast_map	Generate a ranked repository map using PageRank over the symbol graph
ast_diff	Structural diff showing added, removed, and modified symbols
ast_impact	Transitive impact analysis: trace dependents through the reference graph
ast_replace	Replace text only within a specific symbol's body

Declarative MCP tool registry

The MCP server architecture was rebuilt around a declarative registry. Tool schemas are derived directly from Rust types via schemars, eliminating schema drift between CLI operations and MCP tools.

Performance improvements

• spawn_blocking for all sync I/O on Tokio's blocking thread pool, critical for HTTP/HTTPS transport under concurrent requests
• Tree-sitter parse tree caching for repeated AST queries against the same file
• PageRank convergence using L1-norm (threshold 1e-6) instead of fixed iterations

Bug fixes

• doc flatten now includes empty arrays and empty objects instead of silently dropping them
• Transaction engine preserves idempotent delete semantics within a plan
• search --jsonl with zero matches returns exit code 3 consistently
• ast_rename with a no-op rename returns early instead of rewriting files identically
• Git argument injection blocked across all commands that accept paths
• Concurrent-write warnings added to all MCP tool descriptions

Install or update the CLI

brew upgrade patchloom           # Homebrew
cargo install patchloom          # crates.io

Or run Patchloom: Update Patchloom from the VS Code command palette if using the managed installer.