Skip to main content
Memory Crystal uses one Integration Contract. The Support Tier is the part of that contract the host can actually honour.

​
Integration Contract

  1. Credentials registered
  2. Native memory provider active, when the host can run one
  3. Explicit tool surface registered
  4. Discipline layer delivered, by context injection or a managed block
  5. Declared agent identity set
  6. A verification pass that checks only the layers that install claimed

​
Support tiers

Tiers come from the platform table (tier, and hooks.inject). Do not treat a host as Full if it cannot inject context. Context injection is the line between Full and Capture. Grok has hooks, and those hooks capture, but passive events ignore stdout. That is a harness limit. Injection is opt-in on every host that can do it. Set MEMORY_CRYSTAL_INJECT_RECALL=1 or true, or set injectRecall: true in config. A non-empty environment variable takes precedence over config. Grok ignores that setting.

​
Capability and publication

Publication (which hosts are listed as official) is separate from the tier. Cursor’s absence from the official list is a publication difference. It is not evidence that Cursor is unsupported.

​
What the installer actually writes

Codex CLI and Codex Desktop share ~/.codex/config.toml and ~/.codex/hooks.json (CODEX_HOME overrides the directory). Either target writes that shared config. Shared hooks are a Bash install. Native PowerShell writes MCP config and skills, then skips hooks for every row whose hooks.shells is bash. A PowerShell install of a Full host does not give you capture or injection. Hermes is Bash-only. OpenClaw’s native plugin path is Bash-only. Cursor’s local plugin directory is staged by Bash; PowerShell still writes Cursor’s MCP entry and skills. Grok’s hooks capture and do not inject, on both installers, once the Bash hook layer is present.

​
Buzz

Install into the CLI Buzz is running. Channel memory is not available, and channel isolation is not enforced. See Buzz.

​
Client guides