Who can see what my assistant saves?

Whoever may read the vault it saved in. A note in your personal vault is seen only by you and your own assistants; one in a team vault by that team; one in the workspace’s notebook by everyone in the workspace. Someone who leaves the workspace loses access, and so do their assistants.

Can an assistant change or delete notes without me?

Only as far as you let it. Per vault you choose Off, Read only, Read and write, or Ask first, where each change waits as a suggestion for you; deleting also needs the assistant to be allowed to delete. An admin’s rule can set the most any assistant gets. Every note keeps its history, so you can see who changed what and read an older version.

Can I store passwords or API keys in memory?

No. A note whose title, tags or text looks like a password, a token or a private key is refused, and you are told to put it in a connector’s sign-in instead. Notes are encrypted with keys of their own per vault.

Does Codex see the password or key for Flowplane memory?

No. You sign in to Flowplane memory through Flowplane, which keeps that sign-in sealed. Codex only gets a Flowplane sign-in for you, which you can revoke in the console.

Can Codex change things in Flowplane memory without asking?

Yes, by default: none of its changes in Flowplane memory waits for approval. Your workspace’s rules can make any of them ask first, per tool.

Connect Codex to Flowplane memory

Codex reaches Flowplane memory through one Flowplane address. You add Flowplane memory once in Flowplane, add that address to Codex, and sign in. Notes your AI assistants save and recall in any app: decisions, preferences, how-tos. Just for you, or shared with your team or company.

Connect Flowplane memory →Set up your assistant

Tools: 13 read · 11 change
Sign-in: Your own account
Approval, by default: Set per tool
MCP server: Part of Flowplane

1
Add Flowplane memory in Flowplane
Memory is part of every workspace, so there is nothing to add. When you connect an assistant, its Memory step sets per vault what it may do: Off, Read only, Read and write, or Ask first, where every change it makes is a suggestion you approve in the console.
There is nothing to sign in to: each person’s assistants act with that person’s own access. Notes live in vaults. Your personal vault is yours alone; not even the workspace’s admins can open it. A team vault is shared with a team, and the workspace’s notebook with everyone in it, and an admin can make a vault shared with chosen people and teams. An assistant never gets more than its person’s role in a vault: a reader’s assistant only reads.
Connect Flowplane memory →
2
Add Flowplane to Codex
Your address is shown in the Flowplane console; it looks like
https://mcp.flowplane.eu/<your-label>
1. Add the server with the first command below.
2. Sign in with the second: your browser opens Flowplane; sign in and allow Codex.
3. In the IDE extension: MCP servers › Add server, choose Streamable HTTP, paste https://mcp.flowplane.eu/<your-label>, then Authenticate.
```
codex mcp add flowplane --url https://mcp.flowplane.eu/<your-label>
codex mcp login flowplane
```
Steps checked against the vendor’s documentation (OpenAI)
3
Ask Codex
- “What did we decide about the price of the support contract?”
- “Remember that overdue reminders go to finance@example.com, one per customer.”
- “Add to my journal that the offer for Janssens went out this afternoon.”
- “Update our onboarding runbook: new laptops are now ordered through IT, not purchasing.”
- “Who changed the note on our holiday policy, and what did it say before?”

What it can do

What Codex can do in Flowplane memory

Memory is Flowplane’s own shared memory for people and their AI assistants: decisions, preferences, runbooks and project facts, kept as notes in Markdown with folders, links and files. Your assistant searches it before it answers, saves what it learns, keeps a journal of your day and updates a note when something changes, and you read and edit the same notes in the console. Because it lives in Flowplane and not in one vendor’s chat history, what Claude saved today ChatGPT or Copilot can recall tomorrow.

Reads13

List vaultsThe notes you may read or write inmemory_list_vaults
Search memoryFind entries by words in title, tags or textmemory_search
Formats for notesThe chart, diagram and formula formatsmemory_formats
Links of a noteWhat links to and from one notememory_links
History of a noteWho changed a note, and what it said beforememory_history
Read an entryThe full text of one entrymemory_read
List foldersThe folders of a vaultmemory_folders
List attachmentsThe files on one entrymemory_list_attachments
Get attachment detailsIts name, type and sizememory_attachment_meta
Read an attachmentThe text of an attached filememory_attachment_extract
Get attachment linkA short-lived link to download itmemory_attachment_url
List tool notesThe notes on a toolmemory_tool_notes_list
Folder instructionsThe rules for writing in a foldermemory_folder_instructions

Changes11

Save an entryA new fact, decision or how-tomemory_write
Add to the journalA line about what happened todaymemory_journal
Create a folderA new foldermemory_folder_create
Write a tool noteA note on a tool, for next timememory_tool_notes_write
Edit an entryReplace exact text in itmemory_edit
Change an entryRewrite its title, text and tagsmemory_update
Delete an entryRemoves it for good, with its filesmemory_delete
Add an attachmentA file on an entrymemory_attachment_add
Change a vault's instructionsChange a vault's instructions for assistantsmemory_vault_instructions_set
Change a folder's instructionsChange a folder's instructionsmemory_folder_instructions_set
Remove an attachmentRemoves the file, the entry staysmemory_attachment_delete

FAQ

Questions

Who can see what my assistant saves?: Whoever may read the vault it saved in. A note in your personal vault is seen only by you and your own assistants; one in a team vault by that team; one in the workspace’s notebook by everyone in the workspace. Someone who leaves the workspace loses access, and so do their assistants.
Can an assistant change or delete notes without me?: Only as far as you let it. Per vault you choose Off, Read only, Read and write, or Ask first, where each change waits as a suggestion for you; deleting also needs the assistant to be allowed to delete. An admin’s rule can set the most any assistant gets. Every note keeps its history, so you can see who changed what and read an older version.
Can I store passwords or API keys in memory?: No. A note whose title, tags or text looks like a password, a token or a private key is refused, and you are told to put it in a connector’s sign-in instead. Notes are encrypted with keys of their own per vault.
Does Codex see the password or key for Flowplane memory?: No. You sign in to Flowplane memory through Flowplane, which keeps that sign-in sealed. Codex only gets a Flowplane sign-in for you, which you can revoke in the console.
Can Codex change things in Flowplane memory without asking?: Yes, by default: none of its changes in Flowplane memory waits for approval. Your workspace’s rules can make any of them ask first, per tool.

Your assistant

Other assistants with Flowplane memory

Everything about Flowplane memory and Flowplane →

Pricing

Let your AI work with your data. Safely, from today.

Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.

Start free →Book a call