Project Info

Synk: Universal Memory Layer

Devpost

Inspiration

Two weeks ago, I spent 20 minutes explaining my background to ChatGPT for career advice. The next day, I switched to Claude for the same conversation... and had to start over. Then I opened my IDE, and... same thing. I realized: We're in an AI revolution, but memory is still stuck in the 1990s. Every AI tool treats you like a stranger. Your context dies the moment you switch platforms. We use 5-7 AI tools daily (ChatGPT, Claude, Cursor, Copilot, Notion AI) but switching between services means losing all context, making every conversation repetitive and disconnected. Memory isn't just a missing feature. It's the fundamental infrastructure layer AI needs to be truly intelligent. Without it, we're talking to the world's smartest assistant with amnesia. That's why we built Synk.

What it does

Synk is the universal memory layer for AI. It's a cross-platform memory system that works across desktop, web, IDEs, and terminals. It captures, structures, and recalls key personal context so every AI you use instantly feels personalized. Here's how it works: 1. Capture Once, Intelligently You tell ChatGPT: "I'm a Berkeley student in SF, .... vegetarian,... job hunting in AI safety" Synk extracts and structures what matters: location, preferences, facts, goals Upload files like your resume → Synk automatically extracts relevant context (name, college, work experience) 2. Recall Everywhere, Instantly Switch to Claude: "Find me a breakfast spot" → Synk intelligently injects "SF, vegetarian, student budget" based on relevance. Open up Cursor: "Tell me an app that I can build that aligns with my interests and would make my resume stronger." → Already knows your background and target roles No re-explaining. Ever. 3. Works Across Everything Desktop apps, websites, IDEs, terminals. One memory, infinite platforms Every AI interaction becomes context-aware and personalized

How we built it

We built Synk as a three-layer architecture: 1. Capture Layer (Intelligent Extraction) Integrated hooks into popular AI interfaces (ChatGPT, Claude, Cursor, terminal) Built an LLM-powered extraction engine that identifies and categorizes personal context into structured types: preferences, facts, events, notes, tasks, ideas File parsing system to extract context from uploads (resumes, documents, notes) 2. Memory Layer (Storage & Structure) Created a semantic memory database that stores context as structured, queryable entities Privacy-first encryption to ensure user data stays secure Deduplication and conflict resolution to keep memory clean and accurate 3. Injection Layer (Context Recall) Real-time context retrieval that identifies relevant memories based on the current conversation Built adapters for each platform (browser extension, desktop app, IDE plugin, terminal wrapper) Seamless injection of context into AI prompts before they're sent to the model

Challenges we ran into

1. Intelligent Context Extraction Not everything someone says is worth remembering — we had to build smart filters to capture signal, not noise Teaching the system to distinguish between facts ("I live in SF"), preferences ("I'm vegetarian"), and temporary context ("I'm hungry right now") 2. Cross-Platform Integration Each AI platform has different APIs, UI structures, and access methods Building a universal adapter layer that works across web, desktop, IDE, and terminal without breaking user experience 3. Context Relevance Knowing when to inject memory is just as important as what to inject Building a retrieval system that surfaces the right context at the right time without overwhelming the AI or the user

Accomplishments we're proud of

Built a working universal memory layer that actually works across multiple AI platforms in one weekend Intelligent extraction that works — our system accurately categorizes personal context with 85%+ accuracy Real cross-platform support — not just a browser extension, but working integrations for desktop, web, IDEs, and terminal Made AI feel personal — experiencing Synk for the first time genuinely feels like AI finally "gets you"

What we learned

1. Memory is infrastructure, not a feature The more we built, the more we realized this isn't just a nice-to-have — it's foundational to making AI truly useful 2. Context is king The quality of AI responses dramatically improves when you inject even small amounts of relevant personal context 3. The problem is universal Everyone we talked to during the hackathon had the same pain point — this isn't a niche problem, it's the problem 4. LLMs are great at structure Using LLMs to extract and categorize information from natural language works surprisingly well

What's next

Immediate (Next 3 months): Expand platform support: Notion AI, GitHub Copilot, VS Code, more IDEs Build memory management UI: let users view, edit, and delete their memory graph Improve extraction accuracy with fine-tuning and user feedback loops Medium-term (6-12 months): Shared memory spaces for teams — imagine your whole team's AI tools having shared context about projects, decisions, and preferences Smart memory suggestions — proactively suggest what context to capture based on conversation patterns Memory analytics — show users how their memory is being used and what's most valuable Long-term Vision: Become the standard memory protocol for AI — the HTTP of AI memory Build an open memory format that any AI tool can plug into Create a memory marketplace where users can share anonymized memory structures (e.g., "memories for software engineers" or "memories for students") The big picture: Just like the internet needed HTTP as its universal protocol, AI needs a universal memory layer. Synk is that layer. We're building the memory infrastructure for the AI era.

Analysis

Compare with all teams

View

Metric

Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.

Technology

Found in codeClaimed only
  • AnthropicIn code
  • FastAPIIn code
  • PythonIn code

3 of 3 appear in the indexed code.

AI coding agents

No AI coding agent signals were found in this repository.

Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.

Codebase size

Source size

113 KB

Source files

25

Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.

0 stars