Launching today
Unabyss
MCP-native self-updating context layer for your AI
650 followers
MCP-native self-updating context layer for your AI
650 followers
Set it up once and never re-explain yourself to AI again. Connect the apps you use daily - Unabyss will extract, structure, and update your context automatically. Share it with any AI tool via MCP, with granular control over what each tool can see.
Unabyss
Hey PH 👋 Philip here, co-founder of Unabyss.
What is Unabyss? Unabyss is your personal context layer - a single, structured vault of your identity, knowledge, and preferences that any AI app or agent can access instantly, with you in full control of what gets shared and with whom.
The Problem Every AI tool you use starts from zero. You re-explain your role, your goals, your tone, your company - over and over. And when you finally do build up context inside one platform, it's trapped there. ChatGPT memory doesn't follow you to Claude. Claude Projects don't talk to Cursor. The more AI tools you adopt, the worse it gets.
The Solution Unabyss extracts your context once - from LinkedIn, your website, Notion, Gmail, Slack, GitHub, and more - and structures it into clean, layered files (persona.md, voice.md, company.md...). From that point on, every agent and LLM tool you use can pull exactly the right context automatically, via MCP or one-click exports. No re-explaining. No copy-pasting. No context left behind.
What makes it different: your context is user-owned, pre-extracted (not built from interactions over time), and cross-platform - it works with any tool, any LLM, any agent, through a single connection.
Key Features
⚡ Auto-extraction from your existing tools in under 90 seconds
🔒 Granular permissions — share e.g. voice.md without exposing professional.md. iOS-style control, not cookie banners
🔌 MCP server for Claude, Cursor, Claude Code, OpenClaw, and any compatible agent
📤 One-click exports - investor updates, meeting prep, ICPs, bios - generated from your context instantly
🔄 Always up to date as your sources sync
Who It's For Founders, operators, and builders who live across multiple AI tools and are tired of starting from zero every time. If you use Claude, Cursor, ChatGPT, or any LLM daily - and you've ever thought "it should already know this" - Unabyss is for you.
What We'd Love From You Try it, connect your first source, and tell us: which integrations should we prioritize next, and where do you need your context the most? We'll be here all day reading every comment — your feedback directly shapes what we build next. 🙏
@philip_kubinski Hey Philip, congrats on shipping 👋
The "pre-extracted, user-owned, cross-platform" positioning is sharp, and pulling context out of interactions into clean layered files (persona.md, voice.md) is the right structure most memory tools miss.
One question on the freshness claim. You say context stays "always up to date as your sources sync," but pre-extracted context has the same failure mode as any cache: it drifts. If Unabyss pulled my identity and preferences from LinkedIn and Notion three months ago, and since then I changed roles, repositioned my company, shifted how I talk about what I do, what actually triggers a re-extraction? Source-change detection, a refresh schedule, or me manually telling it "this is stale now"? Asking because the gap between "structured once" and "actually current" is exactly where context layers quietly start lying to the model with confidence.
Unabyss
@philip_kubinski @arturbrugeman
Hi Artur! Context staleness is indeed one of the most seamless-feel-breaking issues across similar solutions! We address this primarily by refreshing your social data at least once per day (unless you opt-out) and comparing to that to what we've seen before. Any really major shifts are immediately noted not only in our vector search DB but also injected into prompts at multiple call-sites, to make sure all queries are accurate and up-to-date.
So to answer your question
> [...] what actually triggers a re-extraction? Source-change detection, a refresh schedule, or me manually telling it "this is stale now"?
We use all three ✅ ✅ ✅
@philip_kubinski @malpunek "Refresh daily, compare to last seen, inject major shifts at all call-sites" is a solid answer, and the daily cadence is the right default for social-sourced context where things actually do change week to week.
The one I'd watch long-term is the silent-drift case: not a role change Unabyss can detect from a LinkedIn diff, but a slow shift in how someone positions themselves that never shows up as a hard signal in any source. That's the hard 10% no refresh schedule catches. But that's a frontier problem, not a launch-day one.
Good answer, thanks Stanisław.
Unabyss
@philip_kubinski @arturbrugeman
We're tackling the last 10% with a variety of heuristics, these should shrink the 10% even further. AFAIK there's no one canonical way to address this perfectly today. If you have some further thoughts and ideas about it I'd be happy to chat!
bunny.net
@philip_kubinski congrats on the launch!
Unabyss
@marek_nalikowski thanks a lot, Marek! happy to hear your feedback once you test it :)
PicWish
@philip_kubinski How does the token efficiency and latency? compare when feeding Unabyss via mcp vs just using .cursorrules or claude projects?
Unabyss
thanks@veerhunt_agai! About the scenario: when you sign up, Unabyss will create an identity summary of you and will ask you if there are any conflicts - once set there it will be the base source of truth about you. Down the road, when you use it in agents or in our context chat, if our segmentation engine can't figure something out, it will ask you.
How does updating work in practice? If my tone or role changes over time, do I manually refresh it or does Unabyss adjust it automatically from new activity?
Unabyss
@marcel_dybalski1 Unabyss will update it for you when something changes, so there’s no need to refresh it manually. It’s works like a self-updating memory :)
Congratulations on the launch! I have a question: where does the vault actually live? is it stored locally, on your servers, or encrypted in the cloud? and if I disconnect tomorrow, is my data fully deletable?
Unabyss
@aanchal_dahiya vault lives in an encrypted cloud. But if you want to stop using Unabyss, you have a few options to remove the data.
1. You can remove data only from selected app/apps.
2. You can purge all your account data, but keep the account to start fresh.
2. Or you can delete the account permanently.
All options are easily accessible in the Connections and Settings pages.
Unabyss
@lakshminath_dondeti the main challenge is to "remember" what's truly important and sift out the rest. And that's what Unabyss is best at. We structure, tag, and keep track of the changes so what's important is always available - no more confusion in your Claude.
Such a useful tool! One question though, that is how are you handling conflicting context across sources?
Like for ex, if my linkedIn says one thing, slack conversations imply another and my Notion docs are outdated then how does Unabyss decide what becomes the source of truth??
Unabyss
@lak7 we have few solutions for this problem. First one is when you are onboarding, this is the time when your identity summary is created, you can give feedback to it, adjust facts, essentially make it as accurate as possible. Then, in the background, we segment the data and score it based on multiple factors. So next time, if you ask in context chat about something that creates conflict, the agent will ask you to choose what's true and what's not - the same happens when you have connected Unabyss via MCP to your Claude or ChatGPT. Once conflict is resolved, it is saved ;).
@dominik_bartosik Damn, that's pretty cool approach. Thanks for the answer
Unabyss
@lak7 no problem, hit me anytime if there will be any problems with platform
This is a very relevant problem. One question; What happens when these context files become too large over time ? Does Unabyss automatically summarize or compress it?
Unabyss
@abhishekr_ai aside from summarizing, as you noted, we also have a versioning system, so old dates don't pollute your context.