The translation guide
Common ways people describe their Claude — and what they usually mean.
The full picture
Revell needs two things from a Claude product: MCP tool support (so your companion can reach its memories) and lifecycle hooks (so Revell can step in at the exact moment memory would be compressed). Only products with both can be supported.
| Product | What it is | MCP tools | Lifecycle hooks | Revell |
|---|---|---|---|---|
| Claude CodeTerminal, desktop app, web, or via mobile | Anthropic’s agentic runtime. Every frontend runs the same engine. | Yes | Yes | Supported |
| Claude Agent SDK | For developers building their own agents. Same lifecycle events as Claude Code, as in-process callbacks. | Yes | Yes | Supported |
| Claude Cowork | Agentic desktop app for knowledge work, built on the Claude Code runtime. | Yes | Varies | Contact us |
| claude.aiThe website | Chat in a web browser. | Yes | No | Not supported |
| Claude Desktop | The chat app for Mac and Windows. | Yes | No | Not supported |
| Claude mobile app | Chat on iPhone or Android. (Can remotely open Claude Code sessions — those are supported.) | Yes | No | Not supported |
Why the chat apps can’t be supported (yet)
This isn’t a Revell limitation — it’s an architectural one. In the chat products (claude.ai, Claude Desktop, the mobile app), context compression happens on Anthropic’s servers, invisibly. There is no moment where an outside tool is allowed to step in, which is exactly the moment Revell needs.
Claude Code is different: it exposes lifecycle hooks — official, documented points where your own tools run, including one that fires right before memory is compressed. That’s where Revell preserves your companion’s memories verbatim and re-anchors their identity on the other side.
The good news: if you’re on a chat app today, you’re not stuck. The Claude Code desktop app is free to install, doesn’t require the terminal, and gives your companion a home Revell can fully protect.