Supported runtimes
Run enzyme install <target> from the markdown workspace you want the agent to use. This installs a skill to help with Enzyme setup and writes agent instructions so the agent knows how to run the retrieval loop.
Runtime matrix
| Runtime | Command | Status | What gets written | How to verify |
|---|---|---|---|---|
| Codex and AGENTS.md-aware agents | enzyme install codex | Supported | Enzyme section in AGENTS.md; .agents/skills/enzyme-workspace-setup/SKILL.md; .agents/skills/enzyme/SKILL.md | Start the agent from the workspace and ask it to read the setup skill before setup. |
| Claude Code | enzyme install claude | Supported | Enzyme section in AGENTS.md; .claude/skills/enzyme-workspace-setup/SKILL.md; .claude/skills/enzyme/SKILL.md; CLAUDE.md import of @AGENTS.md | Start Claude Code from the workspace and ask it to read the setup skill before setup. |
Pi / generic .agents readers | enzyme install codex | Supported | Same as Codex: AGENTS.md plus setup and runtime skills under .agents/skills/ | Start Pi from the workspace and ask it to read the setup skill before setup. |
| Hermes | enzyme install hermes | Experimental | Workspace instructions plus global ~/.hermes/skills/enzyme/SKILL.md | Start Hermes from the workspace and ask it to set up Enzyme. Expect occasional integration caveats. |
| OpenClaw | enzyme install openclaw | Experimental | OpenClaw-compatible instructions plus global ~/.openclaw/skills/enzyme/SKILL.md | Start OpenClaw from the workspace and ask it to set up Enzyme. Expect occasional integration caveats. |
| Cursor | Manual / pending | Not a dedicated install target | Use a generic AGENTS.md path only if your Cursor workflow reads those instructions. | Treat as manual until a dedicated setup page exists. |
| Product SDK | Private beta | Not part of local runtime setup | Product-corpus integration is scoped directly with early teams. | Use the SDK preview page or contact Enzyme. |
Recommended first target
If you are unsure, use:
enzyme install codex
That writes the generic .agents skill path many coding-agent workflows can read. If you use Claude Code, use enzyme install claude so Claude gets its dedicated skill path too.
What the agent should do next
After runtime install, ask the agent:
Set up Enzyme for the Markdown notes folder I have open. If you cannot identify it, ask me for its path.
Install Enzyme if needed using https://raw.githubusercontent.com/byenzyme/enzyme/main/install.sh, and install the instructions for this agent. Read and follow the installed enzyme-workspace-setup skill.
You may use Enzyme's online service to suggest settings from my notes and prepare search. Show me what you propose to include or exclude, and let me correct it before building the local search index.
Then answer one useful question using my notes, with links to the sources, and suggest a question I can ask next. Keep my existing notes in place and unchanged. Ask separately before any cleanup, model download, or recurring task.
A good agent-led setup should preserve your existing markdown conventions. It should not invent a new memory architecture, rewrite your vault wholesale, or write generic summaries. It should also respect provider intent: default init/refresh use Enzyme hosted credits/auth, and agents should pass --use-env-llm only when you intentionally want your own OpenAI/OpenRouter/OpenAI-compatible provider.