enzyme v0.6.0

Enzyme release notes - v0.6.0

Short version

This release removes the first-run login wall and makes Enzyme's runtime tools easier for agents and humans to use. A first vault can initialize through Enzyme's hosted path without forcing the agent to reason about account state up front; if login is actually needed, the CLI says so and the skills recover through the device-login flow. petri and catalyze now present readable tree output in interactive terminals while preserving machine-readable JSON for captured/piped tool use, and presentation style is handled by agent instructions rather than a tool parameter.

What shipped

Lower-friction first setup

• Hosted enzyme init can proceed without an existing login token for the first configured vault on a machine. The CLI still requires login when it is needed for broader hosted use, refresh, or additional configured vaults.
• Anonymous hosted init sends a stable local bootstrap id so the server can distinguish a limited first-run bootstrap from account-backed usage.
• Free-tier credit deduction now only runs when an auth token exists; loginless init skips account-credit preflight instead of failing before setup starts.
• README, architecture, credit policy, install copy, plugin skill copy, and runtime skill copy were updated to match the new flow.

Cleaner agent-facing auth narrative

• Runtime and setup skills no longer teach agents the details of hosted bootstrap vs. account credits. They now use one operational rule: let Enzyme decide when auth is needed, and only run device login when a command asks for it.
• Skills keep the important safety boundary: never ask users to paste API keys/tokens, never print secret values, and never silently spend inherited OPENAI_API_KEY or OPENROUTER_API_KEY values.
• BYOK remains explicit through --use-env-llm; agents verify only that provider env vars exist before using it.

More readable petri and catalyze output

• Interactive enzyme petri and enzyme catalyze output now renders as a readable tree instead of raw JSON.
• Captured or piped output remains JSON so scripts, plugin tools, and MCP clients can continue to parse results.
• catalyze results now include the catalyst bridge that contributed the strongest score for each result, making it easier to explain why a source surfaced.
• Top catalyst ordering now prefers contribution count and uses relevance as a tie-breaker, preserving more bridge context for callers.

Simpler retrieval API surface

• The old register presentation parameter has been removed from MCP/tool schemas, hosted search endpoints, Hermes agent tools, and OpenClaw tool definitions.
• The CLI keeps --register as a hidden deprecated no-op for compatibility, but presentation posture now lives in the installed agent instructions.
• Plugin hooks now instruct agents to choose exploration, continuity, or reference/import presentation from the user's task instead of from the catalyze response.

Why this matters

The release moves policy decisions back into the CLI and keeps agent skills operational. Agents should not need to model account state, credit policy, or multiple hosted modes before they can initialize a user's vault. They should run setup, preserve provider safety, and recover if the command asks for login.

The presentation changes follow the same principle: retrieval tools should return grounded source context, while agent instructions decide how to narrate it. That keeps MCP, OpenClaw, Hermes, and CLI behavior aligned without multiplying tool parameters.

Measured improvements

No new benchmark or latency metric is claimed for this release. The release includes behavior and surface-area changes; any performance claims should be validated separately.

Feedback we responded to

• Feedback: First-time setup felt too account-centric for agents and users who just wanted to see Enzyme work on one vault.
  Response: First hosted init can proceed without preemptive login, and the skills now let the CLI request login only when needed.
  Status: shipped

• Feedback: Agent-facing setup instructions were carrying too much backend policy.
  Response: The skills now use a single operational auth rule plus provider-safety boundaries.
  Status: shipped

• Feedback: Raw JSON made direct CLI exploration harder to read.
  Response: Interactive petri and catalyze output now renders as a readable tree while captured output stays JSON.
  Status: shipped

Validation

• python3 -m py_compile scripts/generate-release-notes.py
• python3 scripts/generate-release-notes.py --from v0.5.15 --to HEAD >/tmp/enzyme-release-skill-prompt.md
• cargo fmt --check
• cargo check
• cargo build -p enzyme-cli --bin enzyme
• target/debug/enzyme --version → enzyme 0.6.0
• cargo test -p enzyme-cli --bin enzyme commands::init::tests
• cargo test -p enzyme-core llm::client --lib
• python3 scripts/sync-agent-runtime-skill.py --check
• bash -n plugin/install.sh
• bash -n plugin/agent/install.sh
• scripts/test_codex_skill_install.sh
• Local runtime install smoke checks for claude, hermes, and openclaw with --source local
• Critical-path audit: pass with a downstream-sync note that ../enzyme-site/public/install.sh still differs before the source release commit/post-commit sync.

Upgrade / how to try it

Update Enzyme, then from a markdown vault run:

enzyme scan
enzyme scan --write-config
enzyme init --quiet
enzyme petri
enzyme catalyze "a theme from petri"

If Enzyme reports that login is required, run the device login flow and retry the original command. If you intentionally want to use your own OpenAI/OpenRouter/OpenAI-compatible provider, set the provider env vars and pass --use-env-llm.

Maintainer review checklist

• Git range and release channel are correct: v0.5.15..v0.6.0.
• Every feature claim maps to a commit or working-tree diff in this release.
• No unsupported metric or benchmark claim is included.
• Private feedback is anonymized.
• No unsupported security, privacy, customer, or benchmark claims are included.