Skip to main content
Every assistant you connect to Dexi works against the same notes. A decision saved from ChatGPT on Monday turns up when Claude Code searches on Tuesday, and Gemini CLI can append to it on Wednesday. Your Dexi account holds the memory, not any one assistant, so nothing has to be exported or synced between them. Setup has three parts: connect each assistant, give them all the same instructions, and (optionally) fence their memory into one folder.

1. Connect each assistant

Every client uses the same server URL, https://mcp.dexi.net/mcp, with OAuth. Follow the guide for each one you use: Each one appears as its own entry under Settings → Connected apps in Dexi, so you can limit or revoke them one at a time.

2. Give them the same instructions

Chat assistants only read or write memory when they decide to, or when you ask. Agent runtimes like Hermes and OpenClaw do it automatically through their plugins. A short standing instruction makes the chat assistants behave the same way. Paste this block into each one:
Memory instructions
Where each client takes it: Change the tag names to suit you, but keep them to letters, digits and underscores: Dexi ends a hashtag at a hyphen, so #project-atlas would be saved as #project. What matters is that every assistant gets the same block, so they file and search the same way.

3. Optional: give memory its own folder

By default a connected assistant can read your whole workspace: notes, bookmarks, saved emails, feed articles. If you’d rather the assistants share only what they write themselves:
  1. Create a folder in Dexi, e.g. AI memory.
  2. In Settings → Connected apps, choose Edit access on each assistant and restrict it to that folder. You can also pick a restriction when you first approve a connection.
A restricted assistant sees only notes in that folder, and every note it creates is filed there automatically. Give all of them the same folder and they share one fenced-off memory; give each its own folder and they stay separate. A tag restriction (e.g. #memory) works the same way if you prefer tags. The full rules are under Access restrictions.

Switching agents

Because the memory lives in your Dexi account, trying a new agent runtime does not mean exporting anything. Connect the new one, with its plugin or as a plain MCP client, and it searches the same notes from its first turn. Moving from OpenClaw to Hermes, for example, is the Hermes plugin install and nothing else: Hermes’ recall before each turn is a semantic search over the whole library, with no filter on which agent wrote a note.

Starting from a blank account

If the agent you are leaving has months of memory and Dexi has none of it yet, import first. Both plugin CLIs read an agent’s native memory files and write them to Dexi as notes, with no model involved:
A curated file becomes one note per top-level section, a daily log one note per day with a logged:: date property, and every note is tagged #memory #imported plus the source agent’s tag. Either CLI can import the other agent’s files: hermes dexi import ~/.openclaw/workspace --tag '#openclaw' brings OpenClaw’s memory in from the Hermes side. Re-running is safe. A local manifest skips unchanged sections and rewrites changed ones in place, so you can keep importing while both agents are still in use. Dry-run first if you are near the free plan’s note cap: it prints how many notes the import would create. Three conventions make the hand-over tidy:
  • One tag spans every agent. The Claude Code plugin saves decisions under #memory, and the Hermes and OpenClaw plugins put #memory on every session digest next to their own #hermes / #openclaw tag. “What do you remember?” is list_notes with tag: "#memory"; “what did OpenClaw and I cover last week?” is the same call with agent: "openclaw" and period: "week". Keep #memory in your pasted instructions above so chat assistants file the same way.
  • Match the connection’s access. If the old agent’s connection was restricted to a folder or tag under Settings → Connected apps, give the new one the same restriction (or a wider one), or it will not see those notes.
  • Save what lived outside Dexi before you leave. OpenClaw keeps nothing else once the plugin owns its memory slot, so everything it remembered after that point is already in Dexi. Hermes keeps writing its own MEMORY.md and USER.md, which the Dexi plugin does not mirror live. Run hermes dexi import before retiring Hermes to carry them over. Session digests are off by default in both plugins, so turn them on if you want the conversation trail itself to carry over.
The old agent’s connection can stay or go. Revoking it under Connected apps stops its access without touching the notes it wrote, and created_via keeps recording which agent that was.

Telling the assistants apart

Each note written over MCP records the app that created it (created_via) and the app behind its latest edit (edited_via). Every tool result includes both, and Dexi shows them on the note card and in the editor. If you edit the note in Dexi yourself, edited_via is cleared. See Agent provenance.

Limits worth knowing

  • The free plan’s note cap applies. Memory notes count toward the 1,000-note free limit. An assistant that saves often will reach it sooner than you would, so one note per decision (rule 2) matters.
  • Recall depends on the assistant asking. In chat apps nothing runs between your messages. If an assistant didn’t search, ask it to: “check Dexi first”.
  • Writes are confirmed per client. ChatGPT, the Gemini app and Gemini CLI ask before tool calls unless you’ve told them to trust the server. Claude asks according to your connector settings.