Notes
Writing on continuity, BYOK, and long-term AI tools.
Slow essays on what it means to build a memory layer for AI that survives provider churn, model upgrades, and the years. No newsletter, no schedule pressure — these show up when they're done.
2026 · May
Switch models. Keep the arc.
Why Memrith is BYOK by design. The model can change. Your memory
doesn't. Why the continuity layer should belong to you, not the
AI provider you happen to be using this year.
Planned
The continuity problem with AI
Framing the category. Why chat-by-chat AI products keep
forgetting, why memory features inside cloud AI tools don't
solve it, and what a continuity layer actually has to do.
Planned
Why your AI memory should live on your machine
The case for local-first AI memory: privacy, ownership,
portability, and what changes when you stop renting your
own thinking back from a vendor's cloud.
Planned
Memrith is not a second brain
Explicit category-claim essay. Why "second brain" is the
wrong frame for what Memrith does and what frame fits better.
Planned
A year of using Memrith on myself
Founder dogfood essay, at month 12. What the continuity
layer actually changes about working with AI when the
memory is there.
Want to know when new notes drop?
The Memrith email list (linked at the bottom of the homepage) goes out for shipping notices and the occasional essay. No marketing churn. Unsubscribe in every message.