enzyme v0.5.13

Enzyme release notes - v0.5.13

Short version

This release makes Enzyme easier to bring into agent runtimes and faster to use in voice-first setup flows. The CLI now has a direct enzyme install <runtime> path for Hermes, OpenClaw, Codex, and Claude, installing durable runtime skills without requiring the old enzyme agents command shape. Voice-ready initialization can return seed Petri context while the full index continues in the background, and streamed provisional catalysts reduce the time before agents have useful first-turn context. Init also fails more clearly when catalyst generation quality is insufficient, and OpenAI GPT-5 token-limit handling is updated.

What shipped

Runtime skill installation

• Added enzyme install hermes|openclaw|codex|claude as the primary runtime setup command, with Hermes as the default target.
• Moved substantial agent behavior into runtime-specific skill files while keeping the workspace AGENTS.md marker small, bounded, and replaceable.
• Codex and Claude installs write workspace-local skills under .agents/skills/enzyme/SKILL.md and .claude/skills/enzyme/SKILL.md.
• Hermes and OpenClaw installs write runtime skills under $HERMES_HOME/skills/enzyme or $OPENCLAW_HOME/skills/enzyme, falling back to ~/.hermes and ~/.openclaw.
• Added an isolated Codex smoke harness that installs the skill in a temporary workspace and can run codex exec against it without writing to the user's real workspace.

Voice-ready initialization

• Added enzyme init --voice-ready for agents that need early readable context before the full semantic index is complete.
• Added readiness controls: --voice-entities, --voice-min-catalysts, and --voice-timeout-secs.
• Added streamed provisional catalyst writes for the detached voice-ready worker, so complete catalyst records can become visible before an entity's full LLM response finishes.
• Documented the voice-ready contract and the difference between seed Petri readiness and full semantic-search readiness.

Init reliability and model compatibility

• Added guards around catalyst generation quality so init can fail with clearer progress and diagnostics instead of silently accepting poor catalyst output.
• Updated OpenAI GPT-5 token-limit handling to use the parameter shape expected by newer OpenAI models.
• Added benchmark artifacts and a reusable init-latency harness for protecting the voice-ready contract.
• Tightened the shared release workflow so future releases validate runtime skill installs in isolated homes, handle dirty working trees explicitly, and only require marketplace checks when marketplace/plugin files changed.

Why this matters

Agent setup was doing too much through one workspace file and an older enzyme agents command shape. This release makes runtime setup explicit: install the integration for the agent you are actually using, keep the workspace marker small, and let the runtime skill carry the detailed retrieval/write-back behavior. For voice agents, waiting for a full index before speaking creates a poor first-turn experience; --voice-ready separates early Petri context from full initialization while preserving the normal enzyme init completion contract for non-voice usage.

Measured improvements

• Full copied-vault baseline before voice-ready: 6,442 markdown files copied; normal full init returned in about 27.5s, with indexing at about 8.8s, first entity at about 12.7s, catalysts at about 21.6s, and similarities at about 27.1s (scripts/benchmark_init_latency.py, copied Obsidian benchmark artifact).
• Voice-ready smoke benchmark: 200-file smoke, high allocation returned early around 2.07s with seed catalysts visible; detached completion followed about 6.33s later with 115 final catalysts and 5,750 similarity rows.
• Voice-ready full copied-vault benchmark: full copied Obsidian, high allocation returned early around 10.71s with 21 provisional DB catalysts and 14 Petri-visible catalysts; detached completion followed about 39.42s later with 794 final catalysts, 4,503 chunk embeddings, and 39,700 similarity rows.

Caveat: these are local benchmark artifacts committed with the release work, not cross-platform CI performance guarantees.

Feedback we responded to

• Feedback: Runtime setup needed a direct command for the active agent instead of the old enzyme agents shape.
  Response: enzyme install <runtime> now supports Hermes, OpenClaw, Codex, and Claude.
  Status: shipped

• Feedback: Voice agents need useful first-turn context without waiting for full initialization.
  Response: enzyme init --voice-ready returns seed Petri context while a detached worker completes the full index.
  Status: shipped

• Feedback: Enzyme should layer onto existing markdown and Obsidian structure, not impose a new memory schema.
  Response: Runtime skills now explicitly guide agents to preserve folders, tags, wikilinks, frontmatter, people/company conventions, and existing note structure.
  Status: shipped

Upgrade / how to try it

Install or update Enzyme, then run the runtime setup from your workspace root:

enzyme install hermes
# or
enzyme install openclaw
enzyme install codex
enzyme install claude

For voice-first setup:

enzyme init --voice-ready --voice-entities 3 --voice-min-catalysts 1

For normal setup, continue using:

enzyme scan
enzyme scan --write-config
enzyme init --quiet
enzyme status

Maintainer review checklist

• Git range and release channel are correct: v0.5.12..HEAD.
• Every feature claim maps to a commit in the release range.
• Metrics use committed benchmark artifacts and include caveats.
• Private feedback is anonymized.
• No unsupported security, privacy, customer, or benchmark claims.