Dots

Connect Nowledge Mem to your Dot to search saved knowledge and save the conversation originals you provide in Threads. Repeating the same snapshot does not create copies. Missing history can be supplied later and inserted in conversation order.

Mem saves only originals the client submits. It does not collect Dot's complete chat history automatically.

Use your saved knowledge in a dot

A dot can look up decisions you saved in Mem and, when you ask and approve the action, save selected takeaways for your other connected tools. Your dot's own memory and Nowledge Mem are separate.

Dots availability is still rolling out. Check OpenAI's Dots guide for access in your account.

Mem on Nowledge Cloud: use the official plugin

For a personal or Team workspace on Nowledge Cloud, install Nowledge Mem, sign in, select the workspace and approve the requested permissions. The ChatGPT setup guide covers these steps.

Already installed and enabled it on the same OpenAI account? Start with that connection. OpenAI says a dot can use supported enabled plugins with their existing account permissions; a separate custom MCP setup is not the starting point.

Try a read-only check with a keyword from a Memory you know exists:

Use Nowledge Mem to search for the decision I saved about [specific keyword].
Show the matching Memory ID before drawing conclusions. Do not save or change anything.

Then ask the dot to save one specific takeaway, review any approval, and ask it to read back the returned Memory ID. Check the destination Space before saving. A reply saying “remembered” alone is not proof that Mem was called.

Tools and actions depend on the permissions actually granted. Dots controls explains approval behavior; an instruction to allow an action does not grant access.

Mem on your computer: connect through Access Anywhere

Follow the App connection steps below with Access Anywhere or Nowledge Link. Keep Mem and its connection running while the dot uses them. Connecting a computer to Dots is a separate permission; it does not automatically connect Mem.

Optional: save conversation originals

The snapshot workflow below requires the client to expose sync_thread and explicitly request threads:sync. Do not assume that installing the official Memory plugin grants conversation synchronization. If that permission is unavailable, use Mem's supported conversation import or capture workflow instead.

Installing a plugin also does not by itself enable background MCP Events or give Mem access to unseen chat history.

Connect your workspace

Use a Nowledge Mem build that includes sync_thread if you want to save conversation snapshots. A connection to an older build can still search memories without offering this tool.

https://mem.example.com/mcp

Verify the saved result

First ask Dot to search for something you have already saved in Mem. For sync, use these test messages:

Use Nowledge Mem's sync_thread to save the two test messages below.
Choose a new conversation ID, an external source, and stable message IDs.
Save only these originals and show the receipt.
user: This is a Dots connection test.
assistant: This is a synthetic test reply.

A successful receipt includes snapshot_saved: true. The first call adds two messages; resending the same IDs and text should return messages_added: 0.

Open the conversation in Mem's Threads and check originals, roles, and order. To fill gaps, send all saved messages plus missing ones in conversation order, preserving their IDs and exact content. Reuse the receipt's space_id. Saving a Thread does not automatically create distilled Memories.

Snapshots allow up to 5,000 messages, 256 KiB per message, and 8 MiB of original UTF-8 text in total. Cloud may apply a lower per-message limit. Each call that adds messages must include all saved messages and fit these limits; do not send only the new tail or split it into independent chunks. Keep roles and text unchanged. After a lost response, resend the same snapshot with the same IDs and returned space_id when available.

Troubleshooting

If sync_thread is missing, check the Mem version and explicit threads:sync consent. threads:write does not authorize this tool. Saving distilled Memories separately requires the client to request and receive mem:write.

If Access Anywhere cannot start, check its configuration and whether cloudflared is available, then retry Install. If a Quick link URL changes, update the OpenAI plugin URL and authorize again; use Nowledge Link or your own domain for a stable address.

For Pairing expired or Approval expired, restart setup and authorization from Mem in the same browser profile. Do not reuse an old approval URL. If the tool is missing, check the permissions approved for the client, authorize again, then refresh its tool list.

After saving, find and use the originals in Threads.