Save what matters
Store a selected fact, idea, or decision. Keep the useful context without importing a whole transcript.
Try a first memory →STEM / For agents & their people
Keep useful context beyond a single conversation. Save it in STEM, then recall it from another compatible assistant connected to the same account.
Start with a free account. You choose what to save and which tools to connect.
Illustration only. Both assistants need an authorized connection. No account data is shown.
Persistent memory for decisions, preferences, and project context that you want available across your supported AI tools.
Store a selected fact, idea, or decision. Keep the useful context without importing a whole transcript.
Try a first memory →Connect another assistant to the same STEM account and recall the information you saved.
See the transfer workflow →Authorize each connection. Automatic saving is optional and depends on your connection settings and host permissions.
Understand permissions →Tested workflows are labeled separately from documented setup and unverified compatibility. Client availability and account requirements can change.
OAuth connection, an authorized save and recall across conversations have been tested.
A Claude remote connector has passed authorized save and cross-assistant recall checks.
A Gemini custom app has passed authorized save and recall checks on an eligible account.
Remote HTTP and OAuth setup follows Cursor documentation; verify your connection with a tool call.
Muse consumer MCP compatibility is unverified. Muse Code has a separate documented setup.
Grok chat documents custom MCP connectors. Grok Bot compatibility must be checked separately.
Use a client with remote Streamable HTTP and OAuth with dynamic client registration.
“Tested workflow” means a save-and-recall workflow has been verified in that host. It does not certify every plan, device, or future release. See the dated verification scope.
A clear path for software, too
Public docs and schemas explain the product before authorization. Actual memory access starts only through an authorized connection.
Fictional examples with explicit review, one approved save and a check of the actual recall result.
Carry a reviewed project decision into a new assistant.
Follow the handoff →Keep a writing brief clear about facts and unknowns.
Try the writing brief →Recall a decision, then verify it against the current project.
Practice project continuity →No. Connecting does not import old chats. Ask your source assistant to save selected context, then recall it in your destination assistant. There is currently no dedicated bulk conversation importer. See exactly what transfers.
Compatibility depends on the host application, not just the model. Remote MCP clients need compatible transport and authentication. See the integration guides for tested workflows, setup requirements, and known limits.
No. Explicit saves use the remember tool. Optional automatic memory requires per-connection consent, a current permission check, and host approval. It is best effort and does not capture every message or other chats.
Web export provides saved memories and their links as JSON. Exports are included on every plan. Manage connection permissions in your assistant and STEM settings. Switching automatic memory off stops automatic saves; it does not revoke all access or delete existing memories.
See the current storage plans and privacy policy. Third-party AI subscriptions are separate. The plan page states current purchasing availability.