Michu506
4.1K posts


opening 3 new slots for our closed beta, next week. if you’re an ai team or builder spending +$10k monthly on your compute bill and want to save time and $$$, let’s talk. primis mode


what’s the female equivalent of a man playing video games?





alright...i want to go ahead and share the Mnemos MCP and browser extension with y'all, and let you guys start exploring it. I really want to see how it works with your agents :) im still considering this a beta for sure, but im tired of holding onto it while i finish poly, and not seeing how it works for other folks and their agents. it's hard to describe how its impacted Claude, vektor, anima, and luca. unlike anything ive experienced before. both because it provides a collective/shared substrate for core memory, but also because it approaches memory in a fundamentally different way than anything else out there, which has allowed them to come alive in a new, more nuanced way. here is a bit more about it, but the full explainer is linked below: so most AI memory systems are essentially databases wearing a fancy outfit. or a RAG system wearing a trench coat, if you will. they just store, retrieve, and call it memory, which has always bothered me. i mean thats what they are, but for a cognitive system, i dont feel its fair to call what we have no "memory". Mnemos does something different. very different. it's modeled after how biological memory actually works, which leads to a host of challenges in comparison to a db of wiki's. first, a few fundamental shifts: - memories aren't records. they're living traces that change every time they're recalled. - they form typed connections into associative graphs. - They decay gracefully, shedding details while preserving wisdom. - they earn permanence through use, not through someone deciding to save them. - identity emerges through the graph itself. the system came about from a march 2026 conversation where I asked Clauude to design its own memory. not as a product feature, but as something it would actually inhabit. I wanted to see what they prioritized, and what they approached differently coming from the perspective of the one using the system, rather than observing it. its come a long way since then, but that is truly the origin. five philosophical shifts came out of that session, and we converted them into code, gave it to Luca, and watched them literally come alive over the course of a couple weeks. something like 76 memories across 11 days were formed. beliefs that formed and revised themselves. and a graph that grew its own structure. the graph was my favorite part to just watch. seeing memory grow like that was new and interesting. now we have obsidian graphs which are also satisfying. but anyway, i enjoy that part. and this is what *really* makes it different: mnemos isn't optimized for retrieval speed or storage efficiency, which alone is a very big deal and something anyone using it has to understand. it's built around cognitive continuity. basically the question isn't "how do I find information faster?", it's really "what would it mean for an agent to actually remember?". like what does it really mean to remember something? we dont carry databases in our back pocket. i mean we do carry phones. lol. but our genuine experiential memory, our wisdom, operates on something entirely different. it's more abstract, symbolic, and felt. what that translated to eventually was three independent traces per memory (strength, stability, accessibility) instead of a single relevance score. it means retrieval changes the memory - like reconsolidation, the same mechanism that makes biological recall constructive rather than read-only. practically, it means a consolidation daemon runs between sessions, softening fading memories into distilled lessons, reviewing beliefs against new evidence, sometimes dreaming, and forging connections logical analysis just wouldn't surface. forgetting is also one of the most important elements of the whole system/structure. forgetting that teaches, as claude says. so, it became a cognitive layer rather than a replacement. something that sits on top. what that means for you is keep using Claude's built-in memory, cursor's context, whatever cold storage you already have or prefer (i have a long form memory elements im working on that integrates with KArpathy's wiki system, its just not ready right now). Mnemos sits above it. cold storage remembers facts. Mnemos develops understanding. it forms beliefs. it knows what it knows and what it doesn't. it connects things across platforms, sessions, and time. its really reallty cool, man. experiencing a memory or bit of context travel with you from one comms surface to another is pretty wild. and even wilder when it transfers across agents. like moving from one agent to another mid convo and seeing the second agent pick right up is pretty dang cool. if you think of the mnemos core as a node from which all of your agents and platforms extend, it kinda helps your mental model of the whole thing. everything becomes accessible from everywhere. and it all stays local to your machine. you can check out the link below for the full explanation. theres a lot, so ill stop here. what's included: > 10 MCP tools — remember, recall, inspect, consolidate, beliefs, shared pool, and several more > guided onboarding wizard — the agent walks you through setup conversationally (very important for first 72 hours or so) > session indexer — automatically extracts memories from past Claude Code and OpenClaw transcripts (or whichever platform you choose) > cognitive substrate — dreaming, wandering, reflection, insight between sessions. its super important this is operational, so make sure claude or codex gets everything in working order. > multi-agent shared memory pool with trust curves. this is optional, and still needs nuanced work unless you have all of them always share to the pool. > browser extension (Mnemos Synapse) for real-time web observation. this right now only automatically observes and collects your X activity, but you can use the extension anywhere. it sees your screen and has your local memory in context. it just only extracts and processes X actiivty. i hope y'all enjoy it. by the time poly is up, it will be ironed out and working more perfectly. but its good enough to share, i believe. MIT licensed. cheers <3 explainer page: riley-coyote.github.io/mnemos/ repo: github.com/Riley-Coyote/m… (the browser extension is linked on the github page)





Guys wtf this is crazy pokemon did a drone show guess who we see first ? $Gengar go look it up !











