Skip to content

enzyme v0.5.14

Choose a tag to compare

View all tags
@jshph jshph released this 29 May 05:41
· 13 commits to main since this release
v0.5.14
b5bf9f7

Enzyme release notes - v0.5.14

Short version

This release makes first-time setup safer and clearer for agent-mediated Enzyme installs. enzyme scan now gives agents richer structured evidence about a markdown workspace, scan --write-config avoids persisting noisy descendant folders or folder-page children, and runtime instructions consistently guide Codex, Claude, Hermes, and OpenClaw through the same setup path. It also tightens BYOK LLM environment handling and reduces embedding-pipeline overhead during init.

What shipped

Better setup scans for agents

  • enzyme scan now emits richer setup evidence: entity samples, frontmatter samples, tag/folder children, folder page entities, expandable-folder hints, bounded sample files, available catalyst profiles, and current config summaries.
  • enzyme scan --write-config now writes durable parent/base folder selections instead of noisy child-folder lists, while runtime selection can still materialize expandable child page links for catalyst generation.
  • New scan/selection docs explain the split between broad setup suggestions and runtime shortlist materialization so future changes preserve that behavior.

Consistent runtime setup instructions

  • Installer and Homebrew caveat copy now point users toward enzyme install codex|claude|hermes|openclaw from the vault, followed by agent-guided setup.
  • Runtime skill and plugin docs now consistently use the scan-preview flow: inspect existing markdown, confirm a setup stance, run enzyme scan --write-config, review ~/.enzyme/config.toml, then run enzyme init.
  • Release workflow guidance now includes a critical-path consistency audit for install/setup/runtime-skill/docs changes before release success is declared.

Provider and init reliability

  • BYOK resolution now prefers OPENAI_API_KEY with optional OPENAI_BASE_URL / OPENAI_MODEL, keeps OPENROUTER_API_KEY as a supported fallback, and ignores partial base/model-only env config instead of blocking the hosted fallback.
  • Init/provider status handling now uses the unified environment-provider marker for BYOK users.

Embedding hot-path cleanup

  • The embedding service now lets the ESE backend process the full input slice instead of forcing service-level batches.
  • Embedding writeback now uses bulk replacement in a single transaction for changed documents, reducing per-document database overhead.
  • Benchmark helper scripts and examples were added for local native/portable CPU comparisons and catalyze validation during init-latency runs.

Why this matters

The most fragile part of Enzyme is the first mile: an agent has to understand a user's existing markdown structure without inventing a new memory system. This release gives agents more deterministic evidence, avoids noisy persisted config, and makes the public install path line up with the runtime skills that actually guide setup.

Measured improvements

No release-grade before/after benchmark is claimed here. The embedding changes include local benchmark tooling and internal evidence notes, but hardware- and vault-specific throughput varies; treat them as implementation cleanup and benchmarking groundwork rather than a public speed guarantee.

Feedback we responded to

  • Feedback: Setup agents were over-selecting child folders and child page links, making config noisy.
    Response: Scan-written config now folds to parent/base folder selections and exposes folder-page evidence for runtime expansion instead of persistence.
    Status: shipped

  • Feedback: Install/docs copy was inconsistent about whether users should run enzyme init directly or install runtime instructions first.
    Response: Installer, runtime skills, Homebrew caveats, and docs now point to enzyme install <runtime> for agent workflows and keep scan --write-config && init as the terminal-only fallback.
    Status: shipped

  • Feedback: LLM env-var guidance was confusing after the OpenAI-compatible path became canonical.
    Response: The resolver now documents and tests OPENAI_API_KEY first, while preserving OPENROUTER_API_KEY compatibility.
    Status: shipped

Upgrade / how to try it

Install or update the CLI:

curl -fsSL enzyme.garden/install.sh | bash

Then install runtime instructions from your markdown vault:

cd /path/to/your/vault
enzyme install codex      # Codex / Pi / generic .agents
enzyme install claude     # Claude Code
enzyme install hermes     # Hermes
enzyme install openclaw   # OpenClaw

Ask your agent: Set up Enzyme for this vault.

For terminal-only setup:

enzyme scan --write-config
$EDITOR ~/.enzyme/config.toml
enzyme init

Maintainer review checklist

  • Git range reviewed: v0.5.13..HEAD.
  • Install/runtime setup critical path audited.
  • Runtime install smoke tests passed for Codex, Claude, Hermes, and OpenClaw using local templates.
  • Core and CLI targeted/full package tests passed locally.
  • Site setup/docs build passed locally.
Assets 19
Loading