Unabyss for Claude - Shared memory across all apps and LLMs. In Claude
byβ’
Claude doesn't know what happens in GPT. Neither one really knows who you are or what your company does. Now they can.
Unabyss gives Claude memories from your other AI agents and everyday apps: email, Drive, GitHub, Notion, meeting recorders, and 20+ more. It saves new memories too, so GPT and Cursor stay in sync with the exact same context - sharper than wiring each tool into Claude one by one.
Finally, a real memory that follows you. Private. Portable.
Replies
Unabyss
Hey PH π Philip here, co-founder of Unabyss.
Our first launch, back in May, ended up winning #1 product of the day - still can't quite believe that one. Thank you!
Since then, we listened to your feedback & rebuilt the whole thing around one idea: your context should live where you actually work. So we moved Unabyss into Claude.
What's new since May - and why we're relaunching:
Claude-first, MCP-first. No browser needed anymore. Connect the MCP once, and everything happens inside Claude.
The part we're most excited about: save context from any Claude chat into Unabyss - and reuse it in Cursor, GPT, or any other agent. What you work out in one place carries over everywhere. Memory that follows you, instead of resetting every session.
Rebuilt the MCP from scratch, now loaded with 60+ skills - Claude just works with your context. No setup, no copying files between tools.
15+ new integrations along the way: Obsidian, HubSpot, Notion, Asana, GitLab, and more.
Who it's for: builders wiring up AI tools, founders juggling context across a dozen apps, consultants who live in other people's stacks. Anyone tired of re-briefing their AI every morning.
Last time, we shipped a context layer you configured in an app. This is context that lives in Claude and travels with you.
We're around all day - try it at unabyss.com and tell us how you'd use portable memory, and what's missing. Tear it apart!
Yours,
Philip & the Unabyss team
@philip_kubinskiΒ the line i'd underline in the pin is 'save context from any claude chat'. i keep md context files across four repos and the same fact lives in all four β nothing tells the other three when one changes. and that's the tidy layer: yesterday i pulled a price into a single constant, and the stylesheet next to it was still describing the old one in a comment. storing the file somewhere better wouldn't fix that. the file being a byproduct instead of a chore might.
Unabyss
@webappskiΒ this is exactly it. the same fact living in four files with nothing to reconcile them is the whole problem - and your stylesheet-comment example is painfully familiar.
the moment context is a file you maintain, it drifts, because keeping four copies honest is a chore nobody does.
"byproduct instead of a chore" is a better line than anything in our pin, honestly. that's the bet: context you use stays current because using it updates it, instead of context you have to remember to go edit.
the price you pulled into a constant yesterday - that's a decision, and it should propagate to wherever that price is described, not sit in one repo waiting for you to notice the other three.
curious where it breaks for you though: with md files across repos you've at least got git history and diffs. what would you actually need to trust a shared layer over four files you can see? that's the honest gap we're still working on.
@philip_kubinskiΒ This looks like the right direction. Portable memory is much more useful when it lives inside the actual tools people already use .
One question: how do you handle memory conflicts when different tools have slightly different or outdated context? For example if Claude saves one version of a project detail but Cursor or Notion has a newer one, does Unabyss rank, merge, or ask the user to resolve it?
@philip_kubinskiΒ Hit this exact thing jumping between Claude and GPT on the same project. Half the context just vanishes. Looks like it actually solves that.
I live in Claude Code all day and maintain CLAUDE.md files across client projects, so the line about a context file being frozen the moment you write it hit home. Mine rot quietly until something breaks. Spent a while on your landing and FAQ before commenting, the comparison against built-in memory and plain context files is the clearest pitch I have seen for this category, and tagging by topic, sensitivity and source is the part that actually matters.
Two honest questions before I plug it into client work. First, when a wrong fact gets extracted from an old Slack thread, where do I see and fix it before it follows me into every tool? A reviewable, editable memory list would be the make or break feature for me. Second, for the agency use case, how confident are the sensitivity tags in practice? One client detail leaking into another client's session over MCP would end the experiment instantly.
Upvoted, and the Pro plan pricing next to a Claude Max subscription is smartly placed.
Unabyss
@abdullah_javaid3Β appreciate your feedback!
1. Wrong facts -> we have conflict resolution in place, so incorrect information won't be retrieved from memory. Facts are cross-checked against other, more recent memories before they're retrieved.
2. Source tagging is bulletproof. Permissions for sensitive/confidential data are handled by the agent, so I can imagine edge cases where things don't work exactly as intended. Agency use-case is very specific and we're launching the agency context architecture soon. Memory silos will be fully isolated, making this 100% secure. Until then, I'd recommend using source-level (connection-level) permissions.
Happy to update you when 2) is live!
@marcin_uchacz1Β thanks Marcin, that helps. The recency weighted cross check is a sensible way to handle stale facts, and I saw Philip mention Context View landing Monday, which covers the reviewable memory list I was asking for. Good timing.
On the agency side, I noticed a few of us in this thread are circling the same worry, so the isolated silos launch will matter to more people than just me. Please do tag me when it is live. I will put two real client projects on it that same week and report back honestly.
Unabyss
@abdullah_javaid3Β I'll make sure to do so!
Unabyss
@abdullah_javaid3Β About the wrong facts and conflicts, we have the conflict resolution engine that works in the background. But if it misses something, you can always adjust it in any agent the Unabyss is connected to or in our in-app context chat. Fixed in one place - fixes it everywhere.
Our permission layer is overprotective. So it is more likely you will get less confidential data than it will return something that it should not.
If you could find time to share your feedback from using Unabyss, it would be great - we ship every day, so if something does not work perfectly, it should be fixed in a few days ;).
@dominik_bartosikΒ appreciated, Dominik. Fix in one place fixes everywhere is the behavior I was hoping for, and overprotective is the right default for a permission layer. False negatives are annoying, false positives are fatal. I will give it a proper run on my own workflow first, before any client data goes near it, and post what I find in this thread. Shipping every day makes that feedback feel worth writing.
Unabyss
@abdullah_javaid3Β thanks a lot! Can't wait to hear more form you ;)
Congrats on the launch! The retrieval-time conflict resolution looks to be the crucial part? A lot of memory layers just dump everything into context and let the model referee - but you look to be on the right path. QQ - recency as the tiebreaker assumes newer means truer, but a stable preference from 3 months back usually beats something I typed once yesterday in a bad mood right? How do you guys tell a durable fact from a throwaway one when the two collide?
Unabyss
@artstavenka1Β thanks! We have a complex conflict resolution engine. When some memories conflict, we don't rely only on the date but also on the source, repetition, who the author is, etc. If automatic resolution raises concerns, we are adding a note explaining why this data changed and when.
Are you introducing team plans?
Unabyss
@jakub_witowskiΒ yes, next week. I'll let you know as soon as it's ready! But you can already onboard your team and we'll merge your accounts into one org in a few days.
Unabyss
@jakub_witowski,Β we are multitasking - as we speak, the team plans are being developed :D.
Audioscribe
wooow does it mean i can connect all my dating apps and claude code will understand whatβs my type??
Unabyss
@kyzoΒ :D why not - this sounds like a valid use case
Unabyss
@kyzoΒ yup, and if you share your MCP with your match, you can skip dating. You'll already know everything about each other!
When local version? I need to start pushing this to my clients.
Unabyss
@greenparrotnowΒ we're shipping local memory next week. I'll share closed beta with you via DM!
Unabyss
@greenparrotnowΒ already in progress ;) local version is launching soon
Huge congratsπ on the launch.. evaluating the new connector nodes right now and the sync times look incredibly tight. quick question how does the system manage context safety checks to ensure one client data node never leaks into an active workspace thread?
Unabyss
@priya_kushwaha1Β thanks!
We worked very hard to improve sync times :)
Can you say more about the 60+ skills? Do they work only with Unabyss or standalone?
Unabyss
@przemek_budnyΒ great question!
You can find all of them here -> https://unabyss.com/skills. It's a mix of skills developed in-house & forks of most starred skills.
You use them along with Unabyss -> it delivers the context needed to deliver the output. E.g. if you use skill "positoning", Unabyss will feed the AI agent with all the data associated with your product, market, competitors, marketing, and more.
Let me know which skill you've tried out! :)
Unabyss
@przemek_budnyΒ skills are solely designed to leverage your context provided via Unabyss, so you need only Unabyss to take advantage of them ;).
Sheesh! It's so cool
It genuinely solves one of the biggest frustrations with ai today, ie having to rebuild context every time you switch tools if it works! Will def try this out and give my feedback
Unabyss
@lak7Β thanks, Lakshay!
DiffSense
Hey guys! Quesstion. There are many shared memory apps out there. What sets this appart from the rest? Also curious about the name, its great! What was the reasoning behind the name? Thanks π
Unabyss
@conduit_designΒ first of all, we want to work in the background. Once you set up, there is no need to change how you interact with any agent. Unabyss does its thing, and you don't even know about it - you just see better results from agents and fewer questions asked.
About the name (thanks!), it comes from a combination of 2 words: "un" + "abyss" - as you can see in the screen below, when you hover over the logo in the footer, you will see the full etymology.
DiffSense
@dominik_bartosikΒ Nice easter egg! I sent you some feedback on LI. Great product launch go for gold! π still nr1