Your context is trapped inside each AI tool by design. Sulci captures it everywhere and surfaces it everywhere — so you stop re-explaining yourself.
Self-host locally with a one-liner. Your data stays on your machine. Or use Sulci Cloud: fully managed, zero setup, access from anywhere.
curl -fsSL https://sulci.xyz/install.sh | bashsulci-start → opens localhost:8080
~/.sulci data directorysulci-startFully managed. Sign up, connect your AI tools, and your knowledge is captured and synced. No local server, no API keys, no maintenance.
localhost:8080
You use multiple AI tools every day. Not one of them shares context with the others. Your history, preferences, and decisions stay locked inside each tool, by design. Your brain is the connective tissue holding your entire AI stack together.
Here's what that looks like in practice:
When you re-explain from memory, details mutate. Small errors compound. Claude debugs a system that doesn't exist, built from your inaccurate recall.
Decisions evolve, but each tool is frozen at the last thing you said. ChatGPT still thinks RabbitMQ while Claude plans your Kafka migration.
Every tool only sees its own conversations. It gives confident advice while missing critical context from every other tool you use.
Shared context is portable. Portable means you can leave, and that kills the $20/month subscription. So your history, preferences, and decisions become an ever-growing switching cost. The fix won't come from the vendors. Your context should be yours.
Now every tool shares one brain. Ask anything and Sulci surfaces the right context instantly, regardless of which tool captured it.
Every Claude Code session starts with a blank slate. Your preferences, decisions, project context. Gone. Sulci gives Claude Code a persistent brain that survives across sessions and projects.
Preferences, decisions, and project context persist across every Claude Code session. No more re-explaining.
Auto-detects which project you're in. Atlas context stays with Atlas. Global preferences follow you everywhere.
Decisions from ChatGPT, research from Claude, calendar events, Slack threads. All available in Claude Code.
Conversations flow in via Chrome extension, MCP server, API proxy, or REST API. Every interaction is captured automatically.
POST /api/v1/interactions
An LLM extracts structured knowledge atoms (facts, decisions, preferences, entities, relationships) with project scoping and conflict detection built in.
KnowledgeExtractor → gpt-4o-mini
SQLite for relational data. ChromaDB for vector embeddings. Dual-indexed for both structured queries and semantic search.
SQLite + ChromaDB
Relevant context flows out via MCP tools, proxy injection, or API queries. Core atoms (importance ≥ 0.75) are always prepended first. Query-matched atoms follow, ranked by relevance, freshness, and confidence.
0.5×similarity + 0.2×freshness + 0.15×confidence + 0.15×frequency
CLAUDE.md was a great start. But a static file in a single tool can't keep up
with how you actually work. Here's what changes when your context layer evolves.
CLAUDE.md only works in Claude Code. Sulci works everywhere. Knowledge stored in one tool is instantly available in every other tool you use.
Instead of dumping everything into every prompt, Sulci uses vector embeddings to surface only the most relevant context. Faster, cheaper, and more precise.
CLAUDE.md is a static file you manually edit. Sulci builds a knowledge graph that understands relationships between atoms. It captures knowledge, detects contradictions, verifies facts, and evolves as your project evolves.
Your knowledge is yours. Sulci runs 100% locally with AES-256 encryption at rest, automatic PII detection, scoped API keys with RBAC, and audit logging. Your data never leaves your machine.
Every piece of information extracted from your conversations is classified, structured, scored, and scoped to the right project.
Sulci assigns every atom an importance score and semantic flags. The most critical facts — your architecture decisions, coding standards, hard constraints — are always in context. Everything else is retrieved only when relevant.
Atoms with importance ≥ 0.75 are injected into every conversation automatically — before any query matching. Your architecture decisions, coding standards, and hard constraints are never missing, no matter what you ask.
Tag any atom as CORE, DECISION, TECHNICAL, or PREFERENCE. Flags drive automatic importance scoring — instructions score 0.9 automatically, CORE-flagged atoms 0.9, decisions 0.85. No manual tuning required.
Facts can expire. Set a valid_until date and Sulci automatically stops injecting stale knowledge. Sprint goals, deadlines, and time-boxed decisions never pollute future context.
When a decision changes, record a new atom and mark it as superseding the old one. The old atom is expired automatically — no contradictions, no ghosts from the past. Your knowledge base evolves cleanly.
Claude, OpenCode, Cursor, Windsurf & any MCP client
Native integration via Model Context Protocol. Any MCP-compatible coding assistant can query your knowledge, store new information, and extract from conversations through natural language. Auto-detects your current project from the working directory.
query_context
add_knowledge
record_interaction
list_knowledge
list_conflicts
resolve_conflict
verification_queue
calendar_today
slack_post_message
gdocs_read
{
"mcpServers": {
"sulci": {
"command": "/bin/sh",
"args": ["-c", "uv --directory /path/to/sulci run --package sulci-mcp sulci-mcp"]
}
}
}ChatGPT, Claude, Gemini & Perplexity
Passive capture from web AI tools. Install once, and every ChatGPT, Claude, Gemini, and Perplexity conversation is automatically captured and extracted into knowledge atoms. Zero effort required.
IDE Context Sidebar · Works in Cursor & VS Code
Context sidebar right in your editor. Auto-queries relevant knowledge as you navigate code. Type in the sidebar search box or hit Cmd+Alt+K for instant queries. Save any selection as a knowledge atom with Cmd+Alt+J.
Sulci is local-first and privacy-aware by design. No cloud sync, no data sharing, no surprises. You opt in to everything.
All knowledge atoms live on your machine. SQLite database, local ChromaDB vectors. Nothing leaves localhost unless you explicitly enable sync mode for a project.
Every incoming atom is scanned for emails, phone numbers, SSNs, credit cards, and IP addresses. PII is blocked from standard projects. No accidental data leaks.
Need to store sensitive data? Create a Private project. It accepts PII, is clearly marked with a lock icon, and gets extra data handling protections throughout the system.
Each project has its own data mode: Local (never leaves your machine) or Sync (eligible for cross-instance sharing). You control the boundary, per project.
I use Claude Code, ChatGPT, Gemini, Copilot, and Claude every single day. And every single day, I re-explain the same context. "The project uses FastAPI." "I prefer async/await." "Marcus handles DevOps." Over and over.
None of these tools talk to each other. Decisions made in one are invisible to the rest. Context evaporates between sessions. I was losing hours every week to this friction.
So I built Sulci. A local-first knowledge layer that sits underneath all your AI tools, captures what matters, and makes it available everywhere, automatically. No cloud dependency. No data sharing. Your knowledge, on your machine, working for you.
14+ years in B2B tech across Wärtsilä, Aiven, and Ververica. Nuclear Energy Engineering from Technical University of Madrid. Statistics & Data Science from MIT. Based in Helsinki, building at the intersection of developer tools, AI, and revenue.
Sulci is in limited beta. Get early access and never re-explain yourself to an AI tool again.
or email directly: hello@lopez.fi