My problem with all of these kinds of things is that memory architecture is the whole point.
If all I needed was common memory space I'd just use symlinks and cloud sync, Obsidian or whatever.
But the context shaping is what makes memory useful in the first place, so just doing one stop shop memory is IMO about as useful as plain old markdown...
With products coming out like this, many claim to do basically the same thing.
How is this better than Claude Code's built in agent orchestrator? Do I need 100 agent types? How do I know the trained agents here are somehow better? Specialization doesn't equate to "better" in every case.
I want to see the light but at this point it feels like these kinds of projects need a better way to benchmark how they are improving on the available state of the art.
It feels like in 2018, a new browser state management tool emerging. Why does this exist?
I have had a stressful, difficult week. Work is volatile right now, and it's taken a toll on my mental health.
Your story took me entirely out of that state, and your words regarding joy and optimism... reframing unimaginable to unfathomable, in particular... have both lifted me and left me with a feeling of unquenchable desire to help.
Thank you for sharing your story, and for being so deeply authentic throughout.
You know, this actually seems like an interesting opportunity to use this locally as a superpowered CMS for my statically generated site. I’d have to figure out how to create a linkage that can be translated to my Next-based resource URLs, but at least this would give me more to work with than just my text editor to manage my markdown stuff.
If all I needed was common memory space I'd just use symlinks and cloud sync, Obsidian or whatever.
But the context shaping is what makes memory useful in the first place, so just doing one stop shop memory is IMO about as useful as plain old markdown...