context-sync and cortex
These are **competitors** — both aim to provide persistent session context across LLM coding tools, but they target different architectures (local memory store vs. MCP server) for the same problem of maintaining continuity in AI-assisted development workflows.
About context-sync
Intina47/context-sync
Local persistent memory store for LLM applications including continue.dev, cursor, claude desktop, github copilot, codex, antigravity, etc.
Implements the Model Context Protocol (MCP) to expose memory operations as standardized tools across multiple AI IDEs and editors. Uses SQLite for persistent local storage with automatic git hook integration to capture project context changes (commits, merges, checkouts). Supports 10+ platforms including Claude Desktop, Cursor, VS Code with Copilot, Continue.dev, and Zed through a single globally-installed server.
About cortex
ProductionLineHQ/cortex
Persistent memory for Claude Code. MCP server that captures decisions, context, and preferences during sessions and injects them back automatically. Local-first SQLite, quality-gated, multi-machine sync. Your AI starts every session fully informed.
Scores updated daily from GitHub, PyPI, and npm data. How scores work