One of the hardest decisions in Second Brain v2 was deciding how much related context recall should include.

Imagine asking:

"What did we decide about the Product Hunt launch?"

One of the earliest problems we ran into building v2 was this:

You decide something in January. You change your mind in March. You ask about it in July.

Most knowledge tools put the connection work on you. Tag this. Link that. File it in the right folder.

Second Brain v2 builds the graph automatically.

The more AI tools I used, the stranger their memory systems started to feel.

Claude knew one part of my life. ChatGPT knew another. Cursor understood a project until I switched tools. Every new assistant meant rebuilding context from scratch.

Most AI memory tools store your data on their servers. That means your context, decisions, and personal knowledge live in someone else's infrastructure, governed by their retention policies, subject to their pricing changes, and potentially readable by their team.

Second Brain v2 runs entirely on your own Cloudflare account.

Most people already have context somewhere. Meeting notes in Notion. Decisions in a doc. Research in a database.

Second Brain v2 can sync directly from Notion, so you do not have to re-enter everything manually.

When an AI system decides what context to surface, you are usually trusting a black box. You do not know exactly why one memory ranked higher than another, or how the system handles edge cases.

Second Brain v2 is fully open source. The recall scoring, the graph traversal, the conflict detection logic, all of it is readable.

AI can remember a fact.

But can it understand how that fact connects to everything else?

Since our May 31 launch (v1.6), we shipped two major releases:

v1.7 added OAuth 2.0 on the MCP endpoint and importance-score-aware smart merging, so high-value memories resist being collapsed by near-duplicates.