FlowState

Setup guide · Beta

Set up FlowState Relay

Reach the FlowState on your own computer from claude.ai, ChatGPT and your other AI apps, from anywhere. Your data stays on your computer. You don't need to be a developer, but you will type a few commands.


1. What you need

FlowState Relay connects your AI apps to FlowState on your computer. Here's what that takes.


2. Install and start FlowState

FlowState keeps your project memory in one file on your computer. The easy way to install it is to let an AI app that can run commands do it for you.

The easy way: paste this into Claude Code, Cursor, Codex CLI or Grok Build. It asks which apps to connect, shows you what it will change, then installs.

Set up FlowState for me from https://github.com/dialectforge/FlowState by following its AGENTS.md.

By hand: open a terminal and run these lines. On Windows, type python where it says python3. Put the apps you use after --clients (for example claude-desktop,cursor).

git clone https://github.com/dialectforge/FlowState.git FlowState
cd FlowState
python3 setup_flowstate.py --clients claude-desktop --schedule-backups --no-offsite --install-skill --dry-run
python3 setup_flowstate.py --clients claude-desktop --schedule-backups --no-offsite --install-skill --verify

The first setup line only shows what would change. The second makes the changes, then checks that FlowState answers. Then fully quit and reopen the apps it connected.

Already have FlowState? Update it to get the relay agent. In the FlowState folder, run these lines, with the same apps after --clients as when you installed:

git pull
python3 setup_flowstate.py --clients claude-desktop --schedule-backups --no-offsite --install-skill --verify

Your database is kept. Then fully quit and reopen your apps.

There's nothing to start by hand: the apps on this computer start FlowState when they need it. The relay (step 5) runs its own copy for your other apps.


3. Create your FlowStateMCP account

Go to flowstatemcp.com/signin and continue with Google or GitHub, or get a 6-digit code by email. There are no passwords. The first sign-in creates your account.


4. Get an enroll code and enroll your computer

An enroll code links your computer to your account, once. It takes three steps.

Run these in the FlowState folder. On Windows:

.venv\Scripts\python -m flowstate remote passphrase
.venv\Scripts\python -m flowstate relay enroll --code YOUR-CODE

On macOS and Linux:

.venv/bin/python -m flowstate remote passphrase
.venv/bin/python -m flowstate relay enroll --code YOUR-CODE

When it works, it prints Enrolled. Your relay address: https://<handle>.fsmcp.com/mcp. Write the address down: it goes into your AI apps in step 6. It also gets a certificate for your address, made with a key that never leaves your computer.

If the beta is full, it says so with your place in line, and your code isn't used. See Troubleshooting. If it says relay is not a valid choice, your FlowState is older than 2.2.0: update it (step 2).

From here on, flowstate ... is short for the same start as above (.venv\Scripts\python -m flowstate or .venv/bin/python -m flowstate), in the FlowState folder.


5. Keep the relay agent running

Your AI apps can reach FlowState only while the relay agent runs. Start it and leave the window open.

The relay agent doesn't start by itself. After your computer restarts, run flowstate relay run again in the FlowState folder, or set it to start when you sign in (below).

.venv\Scripts\python -m flowstate relay run
.venv/bin/python -m flowstate relay run

The first line is for Windows, the second for macOS and Linux. To check on it, run flowstate relay status in another window: it shows Relay: ON, your address, the certificate's date and Tunnel: connected.

Optional: start it when you sign in, with your computer's own tools. Put your FlowState folder's full path in place of /path/to/FlowState. Then don't also start it by hand: only one copy can run.

C:\path\to\FlowState\.venv\Scripts\python.exe
-m flowstate relay run
C:\path\to\FlowState
launchctl load ~/Library/LaunchAgents/com.flowstatemcp.relay.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0"><dict>
<key>Label</key><string>com.flowstatemcp.relay</string>
<key>ProgramArguments</key><array>
<string>/path/to/FlowState/.venv/bin/python</string>
<string>-m</string><string>flowstate</string><string>relay</string><string>run</string>
</array>
<key>WorkingDirectory</key><string>/path/to/FlowState</string>
<key>RunAtLoad</key><true/>
</dict></plist>
[Unit]
Description=FlowState Relay

[Service]
WorkingDirectory=/path/to/FlowState
ExecStart=/path/to/FlowState/.venv/bin/python -m flowstate relay run

[Install]
WantedBy=default.target

6. Connect your AI apps

Apps on this computer already use FlowState directly since step 2; they don't need the relay. The relay is for apps in the cloud, on your phone, or on another computer. They all use your address: https://<handle>.fsmcp.com/mcp.

Connecting an app opens a FlowState page: choose Read only or Read and write, type your owner passphrase, and approve. Some apps take a fixed key instead: make one with flowstate remote add-client --name "App name" on your computer. It's shown once. Keep it in your app's settings or an environment variable, never in a chat.

To cut an app off later: flowstate remote clients lists them, and flowstate remote revoke --client ID stops one at once.


7. Replacing a computer, and your data

Your FlowState data lives in one file on your computer. The relay never stores it and can't read it.

More on what the relay and this site can and can't see: how FlowState is secured.


8. Troubleshooting

What you might see, and what to do.


9. Help

Email hello@flowstatemcp.com. Tell us what you ran and what it printed, but never send your passphrase, a key or a token.

FlowState itself is open source: github.com/dialectforge/FlowState. Setting it up with an AI agent? Point it at the guide for AI agents.

Found a security problem? Email support@flowstatemcp.com. See how FlowState is secured.