@pleach/base-tools changelog
Release history for @pleach/base-tools — site-docs entries that materially touched the @pleach/base-tools surface, newest-first. Canonical runtime history lives upstream.
This page collects the site-content changelog entries that
materially touched the @pleach/base-tools
docs surface or named a @pleach/base-tools symbol. It is not the
runtime changelog — the canonical record of @pleach/base-tools
runtime behavior lives in the upstream package
CHANGELOG.md and on
npmjs.org/package/@pleach/base-tools.
See the combined site changelog at
/docs/changelog/combined for the
chronological unified view across every SKU.
Unreleased
Deprecated
@pleach/base-toolsis deprecated — folded into@pleach/core. The tools now ship inside@pleach/coreat the opt-in subpath@pleach/core/base-tools(with the same per-tool subpaths). Import from there — zero extra install, identical surface. The standalone package is a thin re-export shim, retained only for back-compat, and is no longer maintained. New projects should not add it; the tools themselves are unchanged.
Added
- Ten new tools documented on
@pleach/base-tools. Two zero-config:json_query(path extraction over a JSON document — the partner tohttp_json) andmemory(durable cross-session key/value, namespaced, with a pluggableMemoryStorebackend). Eight opt-in and injected:web_search(provider-injected, with a bundled no-keycreateDuckDuckGoProvider),web_fetch(allowlisted HTML → readable text over theurl_fetchSSRF core),http_json/http_head(previously shipped, now documented),code_exec(injected sandboxrunner),ask_user(injected human-inputaskhandler),fs_read/fs_write/fs_list(injectedFileSystemAdapterwithallowedRootsconfinement, read-only by default), andrecall(query the session event log via an injectedreader). All follow the refuse-by-default, inject-the-capability rule. - Model-driven memory can be approval-gated. Documented
requireApprovalForWrites+ the injectedapproveWritegate, andcreateGraduatingApproval— prompt the human for the first N writes, then let the agent write autonomously once trust is established. summarizeToolOutcomesdocumented — a pure fold of recalled events into per-tool{ started, completed, failed, lastError }counts, for turning the audit log into a prompt hint.
Fixed
- Registration examples corrected to
createBaseToolsPlugin(...).baseToolsPluginis the zero-config singleton;createBaseToolsPluginis the factory that takes anincludeset + capability config. The prior examples called the singleton as if it were the factory and used a staleenable/allowListfield shape (nowinclude/allowedHostnames). The zero-config default set is now the seven tools that need no injected capability.
Fixed
- Schema
codeRepository+sameAsfor@pleach/base-toolscorrected in the site's Organization + SoftwareApplication JSON-LD@graph(inlined in<head>on every page). Both fields now point athttps://github.com/pleachhq/base-tools(washttps://github.com/pleachhq, a leftover from when the SKU schemas were drafted against an upstream monorepo). Load-bearing becausesameAsis the field AI search engines use for entity reconciliation across the npm ↔ GitHub ↔ docs boundary. See the combined view for the full cross-SKU pack.
2026-06-08 — page-level restructuring
Changed
- Examples reframed and renamed to
Reference apps. Inbound links on
Getting started,
@pleach/base-tools, and the prior changelog entry are repointed.
2026-06-08
Changed
- Packages table corrected to real published
version —
@pleach/base-tools 0.1.0(was largely stale "Reserved · placeholder" framing).
Versioning policy
Semver, deprecation, schema-bundle versioning, and `AUDIT_RECORD_VERSION_HISTORY`.
@pleach/coding-agent changelog
Release history for @pleach/coding-agent — site-docs entries that materially touched the @pleach/coding-agent surface, newest-first. Canonical runtime history lives upstream.