u/rahilpirani5

Why doesn’t my context follow me when I switch between ChatGPT and Claude?

Every time I switch tools, I start over. ChatGPT doesn’t know what I told Claude. Cursor doesn’t remember what I decided yesterday. I am the same person working on the same projects, yet I have to re-explain everything.

I’ve tried keeping a running document to paste at the start of each session. It works, but it’s manual, and I always forget. I’ve also tried the memory features in ChatGPT and Claude, but they are separate; one doesn’t share with the other.

Is there a better way to keep context across AI tools that I’m missing? Has anyone actually solved this issue?

I became frustrated enough that I started building something on my own. I’m creating an open-source memory layer that connects different tools, but I wonder if I am just reinventing the wheel.

reddit.com
u/rahilpirani5 — 2 days ago
▲ 2 r/mcp

second-brain: one memory layer, every AI tool

I use Claude for thinking, Cursor for coding, and ChatGPT for a second opinion. The problem is that none of these tools share information. Each one starts from scratch.

So I built second-brain, a single MCP memory layer that connects all of them.

Store something in Claude, and recall it in Cursor. The context travels with you across tools, sessions, and devices automatically.

Four MCP tools:

- `remember` — store a note, decision, or context
- `recall` — retrieve by meaning, not exact keywords
- `append` — update an existing memory without creating a duplicate
- `list_recent` — browse by time, with `after`/`before` for queries like "what did we decide last week?"

What makes recall actually work:

- Semantic retrieval — finds the right memory even if you phrased it differently when you saved it
- Time-decay reranking — recent context surfaces above old notes automatically
- AI importance scoring — frequently recalled memories rank higher over time
- Duplicate detection — repeated context updates the existing entry instead of cluttering your store

Self-hosted on Cloudflare's free tier. One-click deploy sets everything up. Your data never leaves your account.

Works with Claude, Cursor, ChatGPT, Windsurf, and any MCP-compatible tools.

Demo: https://youtu.be/oMoQomwwvE8
Repo: https://github.com/rahilp/second-brain-cloudflare

Would love your feedback! Drop a comment here, open a GitHub issue, or start a discussion on the repo. Feature requests especially welcome.

u/rahilpirani5 — 2 days ago
▲ 28 r/OpenSourceAI+5 crossposts

Built a semantic memory API on Workers + D1 + Vectorize + Workers AI — all on free tier

Been wanting to push Cloudflare's AI stack harder, so I built a personal memory/notes API that combines all four services into one Worker.

What it does: HTTP API + MCP server that stores notes, embeds them as vectors, and lets you search by semantic meaning rather than keywords. Query "infrastructure decisions" and it surfaces a note about "why we switched from Vercel" — no keyword overlap needed.

The stack:

  • Workers — handles all routing, auth, MCP protocol
  • D1 — stores the raw entries (content, tags, source, timestamp)
  • Vectorize — cosine similarity search across 384-dim embeddings
  • Workers AI — runs bge-small-en-v1.5 for text embedding

Every write hits D1 synchronously (instant response) and queues the embedding to Vectorize in the background. So /capture returns immediately and the vector catches up within a second or two.

One thing worth knowing about local dev: Vectorize and Workers AI don't run in wrangler dev locally — you have to use --remote for anything touching those services. Slightly annoying but not a dealbreaker.

Deployment is one click — the repo has a Deploy to Cloudflare button that provisions D1, Vectorize, and deploys the Worker automatically. Took me longer to write the README than to get it running.

Fits comfortably in the free tier for personal scale. Haven't stress-tested the limits yet but for a single user hitting it dozens of times a day, nothing close to quota.

Repo if you want to look at the implementation: https://github.com/rahilp/second-brain-cloudflare

Curious if anyone else has run into the D1 + Vectorize dual-write pattern and has opinions on better ways to handle consistency there.

u/rahilpirani5 — 2 days ago

60% of Americans have no estate plan. Not because they don’t know they need one. Because the process feels like a headache they’ll deal with later.

I built TrustBuilder (form-trust.com) to remove that excuse.

It’s a free, browser-based living trust generator. All 50 states. About 15 minutes. No account, no email, no data sent anywhere. Your information never touches a server because it runs entirely in your browser. Close the tab and it’s gone from our end, because it was never there.

The output is a real draft document you take to an estate attorney before signing. I’m not trying to replace attorneys. I’m trying to make the attorney meeting shorter, cheaper, and something people actually schedule.

Two things I genuinely can’t figure out and want honest takes on:

Does the privacy angle actually matter to users? I built around “your data never leaves your browser” because it felt like the right call for a legal document tool. But I don’t know if real users care about that or if they’d rather have saved progress and an account.

Does the attorney handoff framing land? The pitch is that TrustBuilder gets you 80% of the way there so the attorney does less and charges less. Or does that just make the tool feel unfinished?

Tear it apart. I can take it.

form-trust.com

u/rahilpirani5 — 26 days ago