Launching today
Contextberg
Turn your work into AI agent memory, served over MCP
63 followers
Turn your work into AI agent memory, served over MCP
63 followers
Contextberg is a local memory app for AI agents. It watches your screens, browser history, and agent conversations in the background β so Claude Code, Cursor, and friends can just remember.
Contextberg
Hey Product Hunt π
Tired of re-explaining yourself to your own AI agent?
I'm Tiger. Every session reset. Every task switch meant catching my agent up from scratch. My brain was doing the memory work that the agent should be doing.
So I built Contextberg β the missing piece.
𧩠What It Does
A local memory app that runs in the background and feeds context to your agent via MCP.
Watches your screens, browser history, and agent conversation history
Builds both short-term and long-term memory in the background
Supplies context to your agent via MCP using built-in skill commands
No build step. Just install from the Microsoft Store and sign up β that's it. Free to start.
πͺ Built for Windows Developers
Every tool like this was Mac-only. Windows developers were always left out.
Contextberg is Windows-first β and built specifically for Windows, so it runs efficiently without hogging your CPU.
Close your laptop Friday night, mid-debug.
Open it Monday morning. "Where should I start?"
Your agent already knows.
π Long-Term Vision
The end goal: accumulate your personal context into your own data warehouse, and use it as fine-tuning material for a truly personalized LLM. An AI that knows you β not just your last session.
Roadmap:
γ- macOS & Linux support
γ- Hermes model integration
γ- Auto-generation of skill commands
γ- Skills management view
Got ideas? Drop them in the comments β your feedback shapes what we build next.
π v1.0.0 Is Live Today
What context do you wish your agent just already knew?
Interesting idea, especially the focus on Windows developers since most AI memory tools seem Mac-first. One thing Iβm curious about: how are privacy and data controls handled when Contextberg watches screens, browser history, and agent conversations? It would be useful to have very granular controls over what gets stored or excluded.
Contextberg
The passive capture approach is what makes this architecturally different from most memory tools I've seen... instead of explicitly saving context like most MCP memory layers do, Contextberg just watches and builds it automatically. I've been thinking about this exact tradeoff while working on my own memory system: explicit memory gives you cleaner, more intentional retrieval but passive capture catches the stuff you'd never think to save yourself.
Curious how you're handling the signal-to-noise problem though.. screen and browser history is extremely noisy. Are you doing any relevance filtering before storing, or does everything go in and the retrieval layer handles pruning? Because in my experience with ChromaDB retrieval, garbage-in-garbage-out hits hard when the vector store gets polluted with irrelevant chunks.
mailX by mailwarm (YC S20)
I think memory/context is becoming one of the biggest bottlenecks for AI agents. The model can be smart, but if it forgets the project every session, the user still does the real work.
How do you think guys about privacy and user control with screen/browser history being part of the memory layer?
mailX by mailwarm (YC S20)
congrats on your launch!
Contextberg