Persistent Flow

Documentation

Learn how to use Persistent Flow.

Complete guides, API references, and tutorials to help you get the most out of your sovereign AI memory.

Connect your assistant

Add the connector

Pick the assistant you use — the address and the steps are right below.

Choose your assistant

ΛClaude

Verified by us

  1. Open Settings → Connectors.

  2. Choose “Add custom connector” and paste the connector address:

    Connector addresshttps://api.persistentflow.com/mcp

  3. Click Connect, then sign in when prompted.

Also verified by us
#SlackNot a paste-the-address flow — ask us and we'll walk you through it.
Speaks MCP — untested by us
Zed
Planned
TTeamsWhatsAppNotionSFSalesforceGitHubObsidian

Using something else that speaks MCP? It should work the same way — tell us and we'll add it here.

How to connect

01 · Copy the address

One URL, for everyone

No account to create first — copy the connector address, you'll use it in the next step.

02 · Connect

Add it to your assistant

Paste it into your assistant's connector settings. It will ask you to sign in — that creates your account. No SDK, no separate signup form.

03 · Talk

It just remembers

Save and recall happen as you talk — verified with every assistant in the picker above, and anything else that speaks MCP should work too.

The command surface

One word, then plain language.

Everything Flow does is reachable by typing it into the assistant you already use. No dashboard to learn, no second place to check.

Get set up

Five minutes once, then never again. Start here.

flow start
A guided setup, about two minutes.
flow menu
Every command, from inside the assistant.
flow i am <name>
Tell your Flow your name, so notes written in the first person resolve to you.
flow whoami
Who your Flow thinks you are.
flow soul · flow soul show
Distil how you write into a voice your assistants can borrow.

Save and recall

The everyday half. This is most of what anyone actually does.

flow save <text>
Keep something. It goes to your active workspace, or your own Flow if you have none.
flow find <query>
Search everything you can see, in whatever words come to mind.
flow about <name>
Everything your Flow holds on a person, a customer, a project.
flow get <id>
Fetch one memory by id, exactly as it was written.

Share with the team

A workspace is one memory owned by the team. People join and inherit it; they leave and lose access while the knowledge stays.

flow workspace list
Your shared workspaces, and which one you are working in.
flow workspace create <name>
Start a shared memory for a team.
flow workspace use <name>
Switch where you are working. Saves and searches both follow.
flow workspace invite <email>
Add someone. They inherit everything the workspace already knows.
flow workspace remove <email>
Remove someone. What they wrote stays with the team; their access does not.
flow workspace role <email> <role>
Change someone's role — member, admin, or owner. Only an owner can change roles.
flow workspace billing
The plan and seats this workspace is using.
flow workspace archive <name>
Hide a workspace you own. The memories are kept — this is not deletion — and it stops counting against your plan.
flow workspace archived · restore <name>
See what you have archived, and bring it back. Owners only, and only once nobody else is left in it.
flow workspace leave
Leave. Access ends immediately; what you wrote stays with the team.
flow context list
Contexts in the active workspace, and what's grouped under each.
flow context create <name>
Start a context inside the active workspace — group memories by team, project or topic.
flow context use <name> · none
Make a context active. Saves and search stay inside it until you switch back with none.
flow decision <text>
Record a decision in the active workspace. Who decided is noted for you.
flow company list
Companies you own.
flow company create <name>
Start a company you own — group several workspaces under one owner.
flow company attach <company> <workspace>
Put one of your workspaces under a company you own.
flow company detach <workspace>
Take a workspace back out of its company — it goes standalone again.
flow company workspaces <company>
The workspaces that belong to a company you own.
flow company find <company> <query>
Search across every workspace under a company you own — answers from whichever one actually has it.
flow company summarize <company>
Each team's own Soul under a company, side by side — not a blended summary.

Keep it true

The half nobody else has. A memory you cannot correct is a liability, so every one of these exists because something went wrong once.

flow review
Memories a later note may have made out of date. Guesses, not decisions.
flow review keep <id> · retire <id>
Answer one: keep it as it stands, or retire it. Only a person can retire a memory.
flow forget <id>
Remove a memory from recall, along with the facts drawn from it.
flow correct <id> <text>
Save a corrected version and retire the old one in the same step. The old memory leaves recall, the history keeps both, and the old record says what replaced it.
flow supersede <old> <new>
Say that one memory replaces another, when both already exist. For the pair you spot while reading — where the correction was written last week and nobody ever connected them.
flow audit
A tamper-evident trail of who did what, and when.
flow export
Everything in your Flow, as a file — a download link that works once.

Sources and confidentiality

Where memories come in — and which ones never go back out.

flow email address [label]
A private address for your active workspace. Forward an email there and it becomes a memory. Shown once — the address is the key.
flow email list · revoke <id>
Your forwarding addresses, and how to switch off one you've let slip.
flow channels
Which channels are linked to your Flow — WhatsApp, email, Slack.
flow confidential on · off
Hold confidential memories back from AIs outside your jurisdiction. They stay in memory and stay searchable from a client you trust.
flow confidential mark <id> · unmark <id>
Mark one memory as never leaving. Reacting with 🔒 in Slack does the same thing.
flow confidential source <channel> on · off
Mark a whole Slack channel as sensitive, instead of one memory at a time.

Type these without a leading slash. In Claude Desktop the “/” key belongs to the app.

Going deeper

Build on the memory layer.

Flow speaks the Model Context Protocol, so anything that speaks it can read and write your memory — including tools you write yourself. No SDK, no lock-in, and the record plane stays in Sweden.

For people building on it

Data Sovereignty

Your data. Your jurisdiction. Your rules.

Not a compromise. Not an upgrade tier. Sovereign by default — because your memory belongs under your flag, not theirs.

🇪🇺 EU Jurisdiction

Stored in Sweden — and the AI that reads it runs in Sweden too. Your memory sits outside the reach of the CLOUD Act, FISA, and every other alphabet soup that wants your data.

🔐 A key of your own

Every person and every workspace is encrypted under its own key. Delete, and that key is destroyed — the ciphertext left behind, backups included, is mathematically unrecoverable. Not a flag in a database.

📦 Always exportable

Export everything in open formats, any time. Delete everything, any time. No lock-in, no hostage data, no 'contact sales to leave.'

Platform, not a client

Build on the memory layer

We're infrastructure. Use our connectors, or build your own solutions on top. The memory layer works with everything.

One URL, no SDK

Paste a single address into your assistant's connector settings and sign in. Nothing to install, nothing to configure, no code.

MCP-native

We speak the Model Context Protocol, so anything that speaks it can read and write your memory — including tools you build yourself.

Platform, not a product

We're the layer between you and every model. Use us directly, or build the next AI tool on sovereign memory infrastructure.

Ready to start?

See licenses