enzyme v0.5.15

Enzyme release notes - v0.5.15

Short version

This release makes Enzyme setup safer and easier to explain: enzyme init and enzyme refresh now default to Enzyme hosted credits/auth instead of silently consuming inherited OpenAI/OpenRouter environment keys. Users who intentionally want to bring their own LLM provider can opt in with --use-env-llm. Runtime and setup skills now explain Enzyme as a compile step that turns ordinary markdown into source-grounded questions agents can search quickly.

What changed

Safer LLM provider defaults for init and refresh

• enzyme init and enzyme refresh now use Enzyme hosted credits/auth by default and ignore inherited OPENAI_* / OPENROUTER_* LLM keys.
• New explicit opt-in flag: --use-env-llm for users who want their own OpenAI, OpenRouter, OpenAI-compatible, or local provider.
• Detached/background init and refresh propagate the same provider choice, so agent/voice flows do not accidentally switch providers mid-run.
• If --use-env-llm is set without a valid env key, Enzyme fails with a direct explanation instead of falling back silently.

Faster non-local catalyst generation

• Catalyst generation concurrency now treats only local providers (localhost or ENZYME_LOCAL_MODEL=1) as serial.
• Direct OpenAI/OpenRouter/OpenAI-compatible remote providers use parallel catalyst generation by default.
• This addresses slow quiet init runs where direct OpenAI was being treated like a local single-request server.

Clearer agent setup language

• Runtime and setup skills now explain Enzyme as a compiler for markdown memory: init does the slower interpretive pass once, creates source-grounded questions for recurring ideas, and leaves fast search handles for future agents.
• Refresh is described as the step that folds new markdown into that compiled map.
• Setup instructions tell agents not to unset shell variables or silently spend personal API keys; use --use-env-llm only when the user intentionally wants their own provider.

Validation

• cargo check
• cargo check -p enzyme-cli
• cargo test -p enzyme-cli --bin enzyme commands::init::tests
• cargo test -p enzyme-core llm::client --lib
• cargo test -p enzyme-core pipeline::catalysts --lib
• python3 scripts/sync-agent-runtime-skill.py --check
• Manual sanity checks:
  • default enzyme init --quiet with inherited OPENAI_API_KEY fails on missing Enzyme login, proving the env key is not used by default;
  • enzyme init --quiet --use-env-llm without env keys fails before creating .enzyme.

Notes

The CLI still supports env-based providers for users who want BYOK or local catalyst generation; the change is that using those credentials is now explicit.