The decentralized architectural design introduces a unified Model Context Protocol (MCP) continuity layer that bridges fragmented AI clients like Claude, ChatGPT, and Cursor. By decoupling contextual memory from individual application vendor boundaries and hosting it directly inside the developer's personal Cloudflare account, the platform establishes an open-source, serverless state machine. It handles multi-hop recall, graph-based relationship synthesis, and hard duplicate detection down to the vector layer—leveraging Cloudflare Workers, D1 SQLite, and Vectorize to run semantic operations with 100% data ownership.
Second Brain for AI
During our v2 launch, you asked for an easier way. Some mentioned being uncomfortable with git. Others flagged the terminal as a barrier. We listened.
This is the Second Brain desktop app and it exists because of your feedback.
Unlike other memory tools, nothing lives on our servers. Your memories are in your Cloudflare account from day one. We literally can't access them.
Here's what we built: Download. Choose a password. Sign in to Cloudflare (or create a free account if you don't have one, we walk you through it). Five minutes later, your Second Brain is provisioned and running on your machine. No terminal. No git. No technical knowledge required.
You get the full v2 experience, recall-by-meaning, the knowledge graph, all of it, running in a native app on Mac or Windows, pre-authenticated and ready to connect to Claude, Cursor, ChatGPT, and your other tools via MCP.
This is what community-driven product development looks like. Thank you for helping us build this. Now come try it, share your thoughts, and let us know what you think.
Second Brain for AI
@thys_beesman Not a black box. The dashboard has a graph view where every edge carries a weight and its provenance, and if a link is wrong you can unlink it there, from any MCP client, or via the API. Weak inferred edges also get pruned nightly, so bad guesses fade instead of hardening into your model of you. On conflicts, it surfaces both. Promote a memory to canonical and it is protected, and a contradicting newcomer lands as a draft for reconciliation instead of overwriting it. Recall favors what survived the challenge rather than what arrived last. Recency alone was how we got confidently wrong answers.
congrats on making this a real desktop app - the git/terminal barrier was a legit dealbreaker for a lot of people on the v2 launch. since it's pre-authenticated to Cloudflare on setup, does the app ever need you to re-auth or re-enter your password day to day, or is it truly a one-time five minute setup and then it just runs in the background like any other memory tool from then on?
Second Brain for AI
@omri_ben_shoham1 One time. Your password is the auth token and it lands in your OS keychain at setup, so you only retype it when connecting a second machine. The brain itself is a Worker in your own Cloudflare account, so it keeps answering Claude and Cursor whether or not the app is open. The app is the installer and control panel, not the thing that has to stay running.
@rahilpirani Congrats, one thing I'm wondering about though, once it's provisioned on your own cloudflare account, how does syncing work across multiple machines, is it pulling from the same cloudflare instance or does each install create its own graph that needs merging. asking because that's usually where "your data, your account" setups get messy.
Second Brain for AI
@moh_codokiai One brain, not one per install. The second machine signs into the same Cloudflare account and points at the same Worker, so there is nothing to merge. The app is only a client on top of it.
@rahilpirani The no-terminal, pre-authenticated setup is a smart move for adoption. One question does the desktop app sync memories in real-time across multiple devices, or is it single-machine only for now?
Second Brain for AI
@vishnu_kant_07 Nothing to sync. The app is a client, the brain is one Worker in your Cloudflare account, so every machine reads and writes the same memory.
I think making the setup frictionless is just as important as improving the memory itself. A lot of developer tools lose people before they ever experience the core value because the first 15 minutes are too much work. Getting someone from download to actually using persistent memory in a few minutes is a bigger improvement than it might seem.
Second Brain for AI
@varun1jan That first 15 minutes is exactly where v2 lost people. The git clone and deploy step was the whole funnel. Now it is download, pick a password, sign into Cloudflare, and your first recall lands before you have decided whether you like it.
the frame that made me click 'installed' was 'you asked for the app. you asked for better recall. we shipped both.' thats not a launch line, thats a receipt. congrats on the ship rahil. one thing i noticed poking around: the recall-by-meaning + graph combo is actually the missing shape for cross-tool memory. every other 'memory layer' i've tried just replays chronology. this one thinks in relationships. going to run it against a week of conversations and report what breaks.
Second Brain for AI
@thenameisarian Chronology was the easy version to build, and it kept handing back the newest memory instead of the right one. Relationships are what let recall answer the question you did not think to ask. When you run that week, send me the cases where it drags in something irrelevant. Over-linking is the failure mode I want data on most.