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.

patchloom: v0.0.6

Patchloom for VS Code v0.0.6

What's New

• Patchloom CLI 0.5.0 support (#166): The extension now recommends CLI 0.5.0, bringing HTTP MCP transport, execute_plan, and an expanded library API.

Bug Fixes

• Accurate CLI compatibility checking (#167): The minimum CLI version is now correctly set to 0.3.0. Previously, the extension reported compatibility with CLI 0.1.0, but commands like append and patch merge did not exist until later versions. Users on older CLIs now get a clear upgrade prompt instead of silent failures.

• Improved test reliability (#157): End-to-end MCP tests are more resilient on slower machines with increased timeouts, reducing false failures during managed install verification.

Internal

• Docs-only changes now skip the full build/test matrix (#162)
• Hardened auto-approve workflow against self-modification edge cases (#160)
• Fixed Scorecard workflow YAML parsing issues (#163, #164)
• Fixed release PRs getting stuck as BLOCKED despite green CI (#157)

patchloom: v0.0.5

0.0.5 (2026-06-22)

Features

• align extension with patchloom CLI v0.4.0 (0629af9)
• align with patchloom CLI v0.4.0 (#145) (0629af9)

Bug Fixes

• ci: prevent spurious Dependabot PR failures from auto-approve and @types/vscode bumps (#143) (3b50515)

patchloom: v0.0.4

Patchloom for VS Code v0.0.4

This release brings full alignment with Patchloom CLI v0.2.0, new Quick Actions, improved documentation, and infrastructure hardening.

What's new

Patchloom CLI v0.2.0 support

• Patch Merge Quick Action: three-way merge is now available directly from the command palette, matching the new patch merge command in CLI v0.2.0.
• Updated documentation links: all "Open Documentation" links now point to the new docs site at patchloom.github.io/patchloom.
• MCP setup guide: the Getting Started walkthrough now includes a direct link to the MCP configuration guide.

Documentation improvements

• The README now lists all 13 commands (previously "Open Documentation" was missing).
• Four undocumented settings are now in the README: patchloom.enable, patchloom.trace.server, patchloom.env, and patchloom.managedInstall.autoUpdate.

Under the hood

• Security: resolved a high-severity vulnerability in markdown-it (GHSA-6v5v-wf23-fmfq) and updated transitive dependencies.
• Code quality: deduplicated constants and error helpers across managed install commands, removing repeated code from three parallel functions.
• CI: replaced the third-party auto-approve action with a native gh pr review call, added a monthly PAT expiry reminder workflow, and added support for curated release notes.
• Dependencies: bumped @vscode/test-electron to v3, @types/node, ovsx, and actions/attest-build-provenance to v4.

Test coverage

252 unit tests, 91% line coverage, zero npm audit vulnerabilities.

patchloom: v0.0.3

0.0.3 (2026-06-07)

Features

• expand Quick Actions with markdown, doc mutations, and undo (#117) (3be2018), closes #114 #115 #116
• expose remaining medium-priority CLI commands as Quick Actions (#122) (cf652a2), closes #120

Bug Fixes

• exclude .patchloom/ from git tracking and VSIX package (#121) (84060fb), closes #119

patchloom: v0.0.2

0.0.2 (2026-06-07)

Features

• add dynamic code coverage badge (#87) (73c7231)
• cache VS Code Marketplace version badge via Gist (#88) (e24a3cc)
• managed install fix + 10 competitive gap improvements (#113) (ea7fcfc)
• MCP-aware status bar, per-editor breakdown, verify command (#94) (21fb8e8)
• use GitHub App token for release-please identity separation (#89) (dfb58f1), closes #77

Bug Fixes

• align release tag format and batch template with patchloom CLI (#98) (623f60f), closes #97
• migrate app-id to client-id in workflow app tokens (#92) (68b9fc8)
• replace retired shields.io Marketplace badges (#82) (00257de)
• resolve CodeQL and AI code quality findings (#100) (6cf1a64)
• skip auto-merge for release PRs (#90) (6613770)
• trim README badges to 7 dynamic essentials (#83) (8e20298)
• update MCP test to use newline-delimited JSON-RPC (#102) (eda9e6b), closes #101
• update release URL tag format and README for patchloom v0.1.4 (#99) (f69d011)
• use App token for auto-merge to unblock post-merge events (#91) (4ed6802)

patchloom: v0.0.1

0.0.1 (2026-06-05)

Features

• add output channel, search/create/doc-get actions, and batch apply (e451e03), closes #27 #28 #29
• implement managed Patchloom binary install, update, and reinstall (d272511), closes #9
• log CLI invocation details in generateAgentRules (9d0095a)

Bug Fixes

• add missing .js extension to re-export in showStatus (2764301)
• ci: exclude private patchloom URLs from lychee (0277fb2)
• ci: fix lychee config syntax and FOSSA job gate (a86c8c8)
• ci: use self-hosted runner for unit tests (private repo) (29e343c)
• correct release-please-action SHA pin (#68) (de77c2f)
• harden managed install download and cleanup (54b061c)
• include workspace name and log errors in generateAgentRules (b194ce4), closes #38
• make all unit tests cross-platform for Windows (#39) (2d82279)
• make dedup test platform-aware for Windows PATHEXT (cf8512d)
• patch test VS Code after download to suppress macOS windows (7549763)
• re-sign VS Code app bundle after LSUIElement patch (c010b30)
• remove placeholder screenshots from README (#66) (b29bbce)
• resolve code quality alerts and improve Scorecard (#54) (cf5aeb0)
• resolve npm audit vulnerabilities via overrides (c3801a9), closes #37
• revert cross-platform CI matrix and use self-hosted for security (93d21a2)
• update integration test for 12 registered commands (b58f606)
• update integration test to expect 9 commands (7e5b78e)
• validate create action path stays inside workspace folder (d107a3b)