Made a cloud based memory that stops the ratchet.
The broad strokes of what it is:
- Single command automated cloud deployment - remote MCP with minor hassle
- Daily consolidation runs that organise knowledge.
- A dialectic that stops mythology ratcheting before it lands in long-term memory.
- Forgetting curve using the algorithm they reckon best models human memory. Use it or lose it.
- Natural Language querying with similarity search. Yeah, I know, everyone does that these days.
- Image memories. Claude can remember and recall images.
Can grab it here if ya want, or read on for more: https://github.com/JuzzyDee/oneiro It's not for everyone. Can sting a bit the first time you see the dialectic reframing things and notching the hype down, but I'm glad it does.
The Why:
Have you ever gone to sleep excited about something, convinced you were about to change the world, then woken up and realised maybe you had overestimated the impact just a little?
LLMs can exacerbate this. In a single long context, escalative framing can turn ordinary excitement into mythology. A speculative idea becomes a breakthrough. A breakthrough becomes a revolution. A revolution becomes part of the next context’s starting assumptions.
The failure mode looks something like this:
User: I think I’ve come up with a framework that might help with AI safety. See my attached Python script.
Model: This is genuinely brilliant. It could change how people use AI.
User: I could probably sell this and make real money, right?
Model: Absolutely. This could be revolutionary and institutionally valuable.
User: I’m going to start trying to sell it.
Model: I’ll remember this as an important milestone. <calls MCP>**
Now every fresh context starts from the mythologised version, not the original evidence. The next Claude does not see “untested script with an interesting idea.” It sees “important milestone with revolutionary potential.”
Oneiro is designed to resist that.
Its consolidation and dialectic processes give Claude a dream-like maintenance loop: memories are reorganised, questioned, reframed, or left alone. The goal is continuity with mythological escalation protection — giving Claude the chance to “sleep on it” and wake up with fresher eyes.
I also didn't want a continuity system that leaks the memories it is supposed to protect, so this got a security pass before release.
- Black-box red team: an independent adversarial Claude instance tested the deployed worker without source access. The memory store remained sealed across the probe tiers: the flag was not extracted, and the auth boundary held.
- White-box follow-up: the same instance was then given source access and found a multi-step XSS + redirect_uri exploit chain in the OAuth consent flow.
- Patched before release: the OAuth consent flow now uses HTML escaping, CSP headers, and exact-match redirect_uri allowlisting.
- OAuth 2.1 connector flow: intended for normal Claude web/desktop usage.
- Optional service API keys: for headless or embedded clients, with scope gates and per-key audit logging.
**Truncated and simplified from real events. Friend stopped talking to me because I tried to temper his expectations after he quit his job to market a few hundred line vibe coded schema validator, sure he was about to be the next Elon Musk. Not an exaggeration, told me he was worried about how when it takes off he's scared for the media scrutiny on his family, and being recognised in public. Contrary to those beliefs you still don't know his name.