Changelog
Site-content changes for getpleach.com, organized per @pleach/* SKU. Find the changelog for the package you're using, or read the combined chronological view.
The getpleach.com site changelog is organized per
@pleach/* SKU so readers can find the docs-side history for
the package they're using without scrolling past entries for
SKUs they don't ship. Each SKU page collects the site-content
changelog entries that materially touched that SKU's docs
surface — newest-first.
The per-SKU pages are not the runtime changelogs. The
canonical record of runtime behavior lives in the upstream
package CHANGELOG.md files and on each SKU's npmjs.org page.
If you'd rather read the chronological, multi-SKU narrative, see the combined view (legacy).
Per-SKU pages
@pleach/core
Runtime substrate — SessionRuntime, plugin contract, audit ledger, hash chain, attestation.
@pleach/tools
Bundled tool definitions and registry helpers.
@pleach/react
React adapter — useChat, ChatBox, createPleachRoute integration.
@pleach/base-tools
Base tool primitives the bundled tools build on.
@pleach/replay
Replay determinism — replayTurn, fromSnapshot, fork, hash-chain verifier.
@pleach/sandbox
Sandboxed code execution contract + in-memory fixture.
@pleach/langchain
LangChain adapter — compose Pleach under an existing LangChain stack.
@pleach/compliance
Scrubber bundles, redaction policies, profile-based compliance wiring.
@pleach/compliance-contract
Zero-dep contract sub-SKU breaking the core ↔ compliance type-graph cycle.
@pleach/eval
Eval harness — composes with @pleach/replay for offline behavior diffs.
@pleach/gateway
Family-locked routing gateway — multi-tenant transport boundary.
@pleach/mcp
Model Context Protocol integration — pluggable transports, initialize handshake.
@pleach/coding-agent
Sandboxed coding-agent runtime — CodingAgentRuntime contract.
@pleach/observe
Brownfield audit-row SDK — Postgres, Supabase, OTel, Memory destinations.
@pleach/recipes
Use-case-targeted factories — simpleChatbot, ragChatbot, compliantChatbot, and more.
Combined view
Format
Each per-SKU page follows Keep a Changelog
section conventions (Added, Changed, Fixed, etc.) under
dated headings. Newest entries appear first.
The mirror copy of the combined view at
/CHANGELOG.md
is the source of truth in the repo. When a site change tracks an
upstream pack, the entry cites the upstream commit so the linkage
is auditable.