Launched this week

Second Brain for AI

Launched this week

Persistent memory for Claude, ChatGPT & Cursor. Free.

440 followers

Persistent memory for Claude, ChatGPT & Cursor. Free.

440 followers

Visit website

LLM Memory

Every AI conversation starts from zero. Your projects, decisions, and preferences disappear as soon as you close the chat. Second Brain fixes that. It is a self-hosted memory layer that works with Claude, ChatGPT, Cursor, and any MCP client. You can store context once and recall it by meaning instead of keywords. It includes duplicate detection, semantic search, and a web UI. Built on Cloudflare, it offers a free tier and your data remains yours. MIT licensed.

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team / Built With

FramerLaunch websites with enterprise needs at startup speeds.

Promoted

curious how it handles conflicting memories. if you store an architecture decision then change it a month later, does it override or accumulate? stale context injected confidently is probably worse than no context at all

Report

2d ago

Second Brain for AI

Maker

Great question! This is actually something I spent a lot of time on. Second Brain has automatic contradiction detection built in. When you store a new memory, it checks your existing memories for semantic conflicts using vector similarity and LLM judgment. If it finds a contradiction, the old entry is deleted and the new one is stored as canonical. So if you change an architecture decision, the old one doesn't silently linger. You're right that stale context injected confidently is worse than no context and that's exactly why this was a priority build for me.

Report

2d ago

AISA AI Skills Test

persistent memory is the piece most AI tools are missing right now. you end up re-explaining context every session which kills the usefulness for anything beyond one-off tasks. curious how this handles conflicting memories when your thinking evolves over time — does it version or just overwrite?

Report

2d ago

Second Brain for AI

Maker

@ozandag Exactly the problem that made me build this. On conflicting memories it does both depending on how you handle it. The `update` tool lets you explicitly overwrite a memory in place when your thinking changes. But there's also automatic contradiction detection: when you store something new, it checks existing memories for semantic conflicts and auto-resolves by replacing the old one with the new one as canonical. Full versioning history is on the roadmap but not there yet. For now it's explicit update or automatic conflict resolution.

Report

2d ago

Clipboard Canvas v2.0

How does duplicate detection handle near-duplicates or nuanced variations in context? I've found that tricky in my own memory tools.

Report

2d ago

Second Brain for AI

Maker

@trydoff Great question. We use a three tier cosine similarity band in what we call Smart Merge. Anything above 0.95 is a true duplicate and merges automatically. The 0.85 to 0.95 band is the nuanced zone where an LLM decides: merge, append, or keep separate. Below 0.85 it stores as new context. Smart Merge handles most edge cases without being too aggressive about collapsing related but distinct memories.

Report

2d ago

AISA AI Skills Test

the memory problem is so underrated in AI tooling right now. you spend 20 minutes setting up context in a conversation and then it just... vanishes. self-hosted is the right call too, especially for teams dealing with proprietary code. how does it handle conflicting memories across different tools?

Report

2d ago

Second Brain for AI

Maker

@ozandag Exactly right on the self-hosted point. Proprietary code should never be on someone else's server.

On conflicting memories across tools: since all your AI tools write to the same memory layer, conflicts are caught at the time of writing, no matter which tool triggered the write. When a new memory arrives that contradicts an existing one, it is detected through semantic similarity and LLM judgment. The old entry is replaced, and its vector is removed. So, if Claude updates something you told Cursor last week, it resolves automatically instead of accumulating into contradictory context.

Report

2d ago

Calling Clones

Does this add continuity? Like timelime for the machine to understand that Its been 2 months I dont talk in that chat and It did not happen yesterday. I don't understand why is so difficult for ChatGPT to do this. I separate context in different chats...

I've been using persistent memory and cross memory between chats in chatGPT since last summer ( apparently I was an advance user or whatever, and It got activated before).

What I need is a TIME layer on it. Like timestamps / timeline awareness
Memory without time is incomplete.

Does this second brain fix this problem?

Report

1d ago

Second Brain for AI

Maker

@javierfandos Yes, temporal recall is a core feature. Every memory is timestamped and you can query by time…“what did I work on last week”, “after May 1st”, or browse a full timeline view. The model understands when something happened, not just what it was. Memory without time is incomplete, which is why it’s baked in from the start.

Report

1d ago

The maker already shipped a CLI since launch — that’s useful signal. What’s the upgrade path for that CLI in terms of keeping it in sync with the web UI? Does it write to the same memory store, or does it maintain a separate local cache that could drift?

Report

1d ago

Second Brain for AI

Maker

@sounak_bhattacharya Same brain. The CLI talks directly to your Cloudflare Worker endpoint, so anything you store shows up in the web UI instantly and vice versa. No separate cache, no drift. It also has offline support built in… if you’re without a connection, writes get queued locally and sync automatically once you’re back online.

Report

24h ago

The 'every conversation starts from zero' problem is real — I waste so much time re-explaining project context to Claude Code every new session. Self-hosted is a big plus for me. Curious about the MCP integration — does it expose memory as a tool that the LLM can call dynamically, or is it more of a pre-prompt injection layer?

Report

1d ago

Second Brain for AI

Maker

@xiaosong001 Dynamic tool calls – fully. Second Brain exposes MCP tools (remember, recall, append, update, forget) that the LLM calls on its own during a session. You do add a short system prompt in your llm profile to tell it when and how to use them, but after that Claude Code handles the rest for all future sessions, recalling context mid-conversation, storing new decisions, appending updates automatically. No manual context files. No re-explaining your project every session

Report

1d ago

1 2 3 4

Forum Threads

p/second-brain-cloudflare

•

3d ago

What breaks your AI workflow between sessions?

I built Second Brain because I kept hitting the same wall.

I'd have a really productive session with Claude, talk through an architecture decision, get to a clear conclusion, close the tab. Next day I'd open a new chat and have to explain everything from scratch. Same thing with Cursor. Same thing with ChatGPT. Every tool starts fresh, every time.

View all