Share context between Claude, ChatGPT and other AI assistants

Documentation reviewed 2026-10-25. Host verification dates are listed separately.

STEM lets a supported assistant save useful context that another connected assistant can recall. Both assistants must authorize the same STEM account. This works in either direction: Claude to ChatGPT, ChatGPT to Claude, or between other compatible clients.

A practical handoff

1. Choose the context. In the source conversation, ask for a short summary of the decisions, constraints and next steps you want to keep. Review it before saving. Keep sensitive or unrelated details out.
2. Save the approved summary. Ask the source assistant to use STEM remember for that exact summary. Give it a recognizable project name. Confirm the successful tool result and saved ID.
3. Recall in the destination. Connect the destination assistant to the same STEM account, select STEM for the conversation, and ask it to recall the project name. Have it show the retrieved context before continuing the work.

Example prompts

In the source assistant:

Summarize the decisions and next steps for the garden website. Show me the proposed memory first. Do not save it yet.

After reviewing the summary:

Save that exact summary to STEM with the project name “Garden website” and type decision. Report the saved memory ID only after the tool succeeds.

In the destination assistant:

Recall the “Garden website” decisions from STEM. Show the relevant saved notes and IDs, then help me continue from those decisions. Do not save anything yet.

Can I import all of my old ChatGPT or Claude chats?

STEM does not currently provide a bulk conversation-history importer. Installing a connector does not copy earlier chats or either provider's built-in memory. A connected assistant can save context you make available and authorize it to save. If you provide an old conversation yourself, ask it to extract and review the specific notes you want to retain before saving those notes.

A saved record is shared context, not a live synchronization of two conversations. STEM does not send messages between assistants, run their tasks, or make every agent automatically read every note. The destination assistant must invoke recall, and results depend on the query and retrieval limits.

Export your STEM memories

In the STEM web app, open Settings and choose Export my memories. The download is stem-memories.json, containing saved memory nodes, their links and counts. Export is included on all plans and remains available when storage is full.

Authorized developer clients can use GET https://awase.dev/stem/export with their issued bearer access token. The JSON response includes exportedAt, nodes, edges and counts. This is not a public download link. The current export implementation requests up to 100,000 memory records and 200,000 links; contact support if you need a larger export.

Export gives you a portable copy. STEM does not currently offer a corresponding one-click restore or importer for arbitrary provider exports. Another system's ability to accept the file depends on that system. The memory export is not an export of entire provider conversations or uploaded media files.

Keep your shared context useful

• Use one topic or decision per memory, with a recognizable project name.
• Include the date or version when a fact can change.
• Recall related notes before adding a duplicate.
• Mark corrections clearly, or explicitly remove the outdated record by its ID.

Choose what gets remembered

Ask explicitly to save with remember. Optional automatic memory is a separate choice for each eligible OAuth connection in STEM Settings → Memory preferences. The agent must call memory_status with {} before an automatic save, require automaticSavingAllowed: true, and use remember_automatically. Host approvals still apply. Switching to manual does not erase existing memories.

STEM saves selected context supplied by a connected assistant. Connecting does not import earlier conversations, give access to other chats, or guarantee a save on every turn. Do not save passwords, tokens or secrets.

Start with the harmless cross-assistant test, or read the MCP reference.