Does supermemory Work With Any AI Model or Harness, Including Air-Gapped Environments?

Yes. supermemory is designed to sit outside the model itself: memory and learning live in supermemory's own infrastructure rather than inside a model provider, so the same memory can carry across models and harnesses. The site also states that supermemory "runs everywhere, even in air-gapped environments." The practical condition is that your agent must be able to reach supermemory and receive injected context — through the API, plugins, or MCP — so "any model" means any model your harness can wire up to that injection path, not automatic support with zero setup.

Why model choice doesn't lock your memory in

supermemory's stated position is that learning and memory should be separated from model providers and stay highly interoperable. The mechanism is in-context injection: raw data (chats, URLs, files, raw data) enters supermemory, the learner-1 model extracts and "dreams on" the context of each user, task, or tenant, updates/merges/infers/forgets against a vector-graph memory database, and the resulting memories are injected as tokens into your agent's context in real time.

Because the memory is stored and maintained outside the model, switching models or harnesses doesn't reset what the agent has learned. That is the core claim behind "any model, any harness."

What "in-context" means in practice

The model isn't retrained or fine-tuned on your data. Instead, relevant prior memories are placed into the prompt at request time. Two consequences follow:

• Portability: the same memory store can serve different models, since each just receives tokens.
• Model-agnostic behavior: the model's own weights are unchanged; improvement comes from better context, not from the model learning.

How you connect a model or harness

The site lists three access paths: API, plugins, and MCP. It also offers a setup prompt you can open in an assistant (the page names ChatGPT, Claude, Cursor, and Grok as examples) to configure the integration.

A typical flow looks like this:

1. Input: your agent's raw context — chat turns, URLs, files, or raw data.
2. Action: send it to supermemory; learner-1 processes it against the memory DB.
3. Retrieval: prior memories are injected into your agent's context via hooks before the model call.
4. Expected result: the model answers with relevant history and learnings in context, regardless of which model is behind the harness.

The exact endpoint names, SDK calls, and hook configuration aren't specified in the available page content, so check the API/plugin/MCP documentation for concrete parameters rather than assuming menu locations.

Air-gapped and self-hosted setups

The page states supermemory "runs everywhere, even in air-gapped environments." That claim matters if you can't send data to external model providers or SaaS services. However, the source material doesn't detail deployment options, licensing, or what an air-gapped install requires. Treat the air-gapped statement as a stated capability and confirm the specifics — supported deployment targets, offline model requirements, and data handling — with the team before planning around it.

Choosing based on your setup

Practical caveats

• "Any model" still needs wiring. The model must receive injected tokens through a supported path; a harness with no way to call supermemory or accept injected context won't benefit automatically.
• Scale claims are vendor-stated. The page says supermemory serves 100k+ organizations and over a trillion tokens a month; that's a company claim, not an independent benchmark.
• Pricing and plan limits are referenced via the pricing page but not detailed in the available content, so confirm tier features (especially document extraction) directly before committing.

If your goal is memory that survives model swaps and works across harnesses, supermemory's architecture is built for exactly that. If you need air-gapped deployment, verify the operational details first — the capability is stated, but the how-to isn't in the source material.