thinking about a hosted version of flowstate. your agent memory lives on my server, encrypted, backed up, export or erase anytime. local stays free and MIT forever.

flowstate 2.4.4 is out. approve or reject what your ai remembers with tap cards right in claude desktop and the claude iphone app, see every change in a project's history, get a plain-word guide to what you can ask it, and a pile of security fixes. free and open source: github.com/dialectforge/F…

Has anyone used FlowState with chatGPT yet?

if you run claude and grok on the same project, the hard part is keeping them on the same page. FlowState is my fix. one sqlite file both read and write, every change tagged with the app and model that made it, and when they write conflicting decisions I get a flag and pick

still working on flowstate 2.4.4. approving a delete now removes exactly the rows you were shown, with a warning if the list changed. when two decisions conflict the newer one shows as unsettled. also a project history page that works on your phone. close

your ai's memory stays on your own computer. the flowstate relay lets claude reach it from anywhere, and anything that needs your ok waits on your phone. the ai can't approve it for you.
flowstatemcp.com
#MCP #AIagents #ClaudeAI #buildinpublic #opensource

your ai's memory lives on your own computer and any ai app can reach it. that's the flowstate relay. in 2.4.2 approvals happen on your phone by default, so nothing waiting for your ok gets approved from a chat. the local version stays free and open source.
flowstatemcp.com

flowstate 2.4.0 is out. this one is about trust, not new features

every save tells you exactly what it saved
deletes take a safety copy first, one undo brings it all back
only you can mark something as "you said so", not the ai
turn approvals on and deletes wait for your ok

flowstate update installs a signed release, backs up first, rolls back if anything breaks nothing updates on its own
14 bugs caught by a new test that runs four agents together

free, MIT, runs on your machine
github.com/dialectforge/F…

spent a while in other people's threads about agent memory yesterday and the thing they keep naming is stale facts, not missing ones. an agent that remembers wrong is worse than one that forgot. that's why flowstate sends deletes to a review queue instead of letting the agent drop them.

the other one: a single line in AGENTS.md telling the agent to read its brief first does more than any feature list.

flowstate 2.3.0 is out. agents can claim a to-do so two of them don't grab the same one, and it flags decisions that might clash (sqlite vs postgres) so every agent sees it. both ideas came from replies here. free, MIT, data stays local github.com/dialectforge/F…

flowstate relay beta is open. memory your agents can write to, and we can't read. decisions, to-dos and components live in one sqlite file on your machine. the relay is tls passthrough with a key made on your computer, so it never sees your traffic. 10 spots, 6 months free flowstatemcp.com/?beta

don't want to run your own tunnel to use flowstate remotely? relay's live. your memory stays on your machine, we just pass the encrypted traffic through and can't read it. flowstatemcp.com/?beta

local flowstate stays free and MIT forever. paid plans only charge for hosting, never features

relay is live in beta: reach your local memory from any agent, anywhere. 10 beta spots, 6 months free, then $3/mo for life

hosted is coming
flowstatemcp.com/?beta

flowstate has a home now: flowstatemcp.com

free, MIT licensed MCP memory server for AI coding agents. one memory for projects, decisions and to-dos, shared across all your AI apps. your data stays on your machine.

relay, hosted and map are in the works
github.com/dialectforge/F…

My build workflow: I research and hash out the architecture with an agent, then have it write the full plan as a PDF or .md. I name the project and the agent scaffolds it into FlowState. From then on, it follows me and stays updated across every agent.

In order to use FlowState across devices you have to self host it from a computer on your network. In order to access FlowState remotely or from mobile apps you have to set up a tunnel and the host device has to be always on. Should I set up a relay service for this?

broke founder week. installing carpet, baseboards, a bathroom and butcher block counters to pay for it. next up: hosted flowstate with graph memory, and telegram running on dialectforge. open source stays free

worked on my pc with grok build, then picked up my iphone and asked claude and grok what we just did. both knew. same memory, two different ais.

that's FlowState. free, open source, runs on your own machine. just shipped v2.1.0

github.com/dialectforge/F…

flowstate update since launch:

- first outside contributor merged (thanks Abdullah Azmi), the mcp switcher works on windows and linux now
- tool descriptions ~35% smaller, core mode loads ~2.9k tokens
- tests run on windows, mac and linux on every change
- setup docs for vs code, cline and zed

free, MIT, local memory for your AIs
github.com/dialectforge/F…

Many Ai’s, one memory.

dialectforge.com/flowstate/