logoalt Hacker News

suncemojeyesterday at 9:23 PM5 repliesview on HN

Lock-in / switching costs are increasingly concerning me. I am using Claude for a good year now and have been accumulating so much "knowledge" in there by now. If Claude became less favorable in terms of price/performance in the future, that would worry me. I've started to think about a distributed solution, where my storage is detached from the inference, but currently Claude is still the way to go for me. Wondering if anyone has similar concerns?


Replies

ksajaditoday at 12:32 AM

This.^ I realized this first when moving a design spec from Claude chat to Claude Code and panicked. I literally had to build something like Notion but for agents to act as a portable memory between all cloud and local models and agents. But honestly it paid off!

If you are interested you can try it out at markbase.cloud (disclaimer and all that). I am not charging for it.

show 1 reply
dadoomeryesterday at 9:37 PM

Isn't all the "knowledge" just text files? I've transitioned between services easily by simply copying the text files.

show 1 reply
fg137yesterday at 10:29 PM

What knowledge?

Unless you work in some obscure domain, chances are that any general "knowledge" Claude has "learned" is already public data somewhere.

If you don't believe me, launch Codex and immediately start working on the same project (s). You might discover that all the knowledge accumulated means almost nothing.

show 1 reply
sparrcyesterday at 9:35 PM

My favorite solution to this is to use the Cline coding agent, which is open and allows you to easily switch between different providers and models.

spicyusernameyesterday at 9:31 PM

Knowledge in there?

Where is the knowledge stored?

All of my knowledge typically gets stored in plans outside of the agent?

And each agent window gets archived regularly, anyways.