Local-first knowledge graph for developers. Watches your project files, extracts entities and relationships using LLMs, and lets you query across all your projects in natural language.
“What architecture decisions have I made across projects?”
Cortex finds decisions from your READMEs, TypeScript files, config files, and conversation exports — then synthesizes an answer with source citations.
You work on multiple projects. Decisions, patterns, and context are scattered across hundreds of files. You forget what you decided three months ago. You re-solve problems you already solved in another repo.
Cortex watches your project directories, extracts knowledge automatically, and gives it back to you when you need it.
- Watches your project files (md, ts, js, json, yaml) for changes
- Extracts entities: decisions, patterns, components, dependencies, constraints, action items
- Infers relationships between entities across projects
- Detects contradictions when decisions conflict
- Queries in natural language with source citations
- Routes intelligently between cloud and local LLMs
- Respects privacy — restricted projects never leave your machine
- Web dashboard with knowledge graph visualization, live feed, and query explorer
- MCP server for direct integration with Claude Code
npm install -g @gzoo/cortexOr install from source:
git clone https://github.com/gzoonet/cortex.git
cd cortex
npm install && npm run build && npm linkRun the interactive wizard:
cortex initThis walks you through:
- LLM provider — Anthropic, Google Gemini, DeepSeek, Groq, OpenRouter, or Ollama (local)
- API key — saved securely to
~/.cortex/.env - Routing mode — cloud-first, hybrid, local-first, or local-only
- Watch directories — which directories Cortex should monitor
- Budget limit — monthly LLM spend cap
Config is stored at ~/.cortex/cortex.config.json. API keys go in ~/.cortex/.env.
cortex projects add my-app ~/projects/app
cortex projects add api ~/projects/api
cortex projects list # verifycortex watch # start watching for changes
cortex query "what caching strategies am I using?"
cortex query "what decisions have I made about authentication?"
cortex find "PostgreSQL" --expand 2
cortex contradictionscortex serve # open http://localhost:3710Cortex ignores node_modules, dist, .git, and other common directories by default. To add more:
cortex config exclude add docs # exclude a directory
cortex config exclude add "*.log" # exclude by pattern
cortex config exclude list # see all excludes
cortex config exclude remove docs # remove an excludeCortex runs a pipeline on every file change:
- Parse — file content is chunked by a language-aware parser (tree-sitter for code, remark for markdown)
- Extract — LLM identifies entities (decisions, components, patterns, etc.)
- Relate — LLM infers relationships between new and existing entities
- Detect — contradictions and duplicates are flagged automatically
- Store — entities, relationships, and vectors go into SQLite + LanceDB
- Query — natural language queries search the graph and synthesize answers
All data stays local in ~/.cortex/. Only LLM API calls leave your machine
(and never for restricted projects).
Cortex is provider-agnostic. It supports:
- Anthropic Claude (Sonnet, Haiku) — via native Anthropic API
- Google Gemini — via OpenAI-compatible API
- DeepSeek (Reasoner, Chat) — strong reasoning, very affordable
- Groq — fast inference with free tier
- Any OpenAI-compatible API — OpenRouter, local proxies, etc.
- Ollama (Mistral, Llama, etc.) — fully local, no cloud required
| Mode | Cloud Cost | Quality | GPU Required |
|---|---|---|---|
cloud-first |
Varies by provider | Highest | No |
hybrid |
Reduced | High | Yes (Ollama) |
local-first |
Minimal | Good | Yes (Ollama) |
local-only |
$0 | Good | Yes (Ollama) |
Hybrid mode routes high-volume tasks (entity extraction, ranking) to Ollama and reasoning-heavy tasks (relationship inference, queries) to your cloud provider.
- Node.js 20+
- LLM API key for cloud modes — Anthropic, Google Gemini, DeepSeek, Groq, or any OpenAI-compatible provider
- Ollama (for hybrid/local modes) — install
All config lives in ~/.cortex/cortex.config.json. API keys are in ~/.cortex/.env.
cortex config list # see all non-default settings
cortex config set llm.mode hybrid # switch routing mode
cortex config set llm.budget.monthlyLimitUsd 10 # set budget
cortex config exclude add vendor # exclude a directory from watching
cortex privacy set ~/clients restricted # mark directory as restrictedFull configuration reference: docs/configuration.md
| Command | Description |
|---|---|
cortex init |
Interactive setup wizard |
cortex projects add <name> [path] |
Register a project directory |
cortex projects list |
List registered projects |
cortex projects remove <name> |
Unregister a project |
cortex projects show <name> |
Show project details |
cortex watch [project] |
Start watching for file changes |
cortex stop |
Stop a running watch process |
cortex query <question> |
Natural language query with citations |
cortex find <term> |
Find entities by name |
cortex ingest <file-or-glob> |
One-shot file ingestion |
cortex status |
Graph stats, costs, provider status |
cortex costs |
Detailed cost breakdown |
cortex contradictions |
List active contradictions |
cortex resolve <id> |
Resolve a contradiction |
cortex models list/pull/test/info |
Manage Ollama models |
cortex serve |
Start web dashboard (localhost:3710) |
cortex mcp |
Start MCP server for Claude Code |
cortex report |
Post-ingestion summary |
cortex privacy set <dir> <level> |
Set directory privacy |
cortex config list/get/set |
Read/write configuration |
cortex config exclude add/remove/list |
Manage file/directory exclusions |
cortex db |
Database operations |
Full CLI reference: docs/cli-reference.md
Run cortex serve to open a full web dashboard at http://localhost:3710 with:
- Dashboard Home — graph stats, recent activity, entity type breakdown
- Knowledge Graph — interactive D3-force graph with clustering, click to explore
- Live Feed — real-time file change and entity extraction events via WebSocket
- Query Explorer — natural language queries with streaming responses
- Contradiction Resolver — review and resolve conflicting decisions
Cortex includes an MCP server so Claude Code can query your knowledge graph directly:
claude mcp add cortex --scope user -- npx @gzoo/cortex mcpThis gives Claude Code 12 tools:
| Tool | Description |
|---|---|
cortex_ask |
Natural language questions about your projects |
get_status |
System status and graph stats |
list_projects |
List registered projects |
find_entity |
Look up entities by name |
query_cortex |
Structured knowledge graph queries |
get_contradictions |
List detected contradictions |
resolve_contradiction |
Resolve a contradiction |
search_entities |
Search entities with filters |
ingest_file |
Trigger file ingestion |
add_project |
Register a new project |
remove_project |
Unregister a project |
session_brief |
Context summary for current session |
Monorepo with eight packages:
- @cortex/core — types, EventBus, config loader, error classes
- @cortex/ingest — file parsers (tree-sitter + remark), chunker, watcher, pipeline
- @cortex/graph — SQLite store, LanceDB vectors, query engine
- @cortex/llm — Anthropic/Gemini/OpenAI-compatible/Ollama providers, router, prompts, cache
- @cortex/cli — Commander.js CLI with 18 commands
- @cortex/mcp — Model Context Protocol server (stdio transport, 12 tools)
- @cortex/server — Express REST API + WebSocket relay
- @cortex/web — React + Vite + D3 web dashboard
Architecture docs: docs/
- Files classified as
restrictedare never sent to cloud LLMs - Sensitive files (.env, .pem, .key) are auto-detected and blocked
- API key secrets are scanned and redacted before any cloud transmission
- All data stored locally in
~/.cortex/— nothing phones home
Full security architecture: docs/security.md
- SQLite via better-sqlite3 — entity and relationship storage
- LanceDB — vector embeddings for semantic search
- Anthropic Claude — cloud LLM provider
- Google Gemini — cloud LLM provider (via OpenAI-compatible API)
- DeepSeek — cloud LLM provider (reasoning + chat)
- Groq — fast cloud inference
- Ollama — local LLM inference
- tree-sitter — language-aware file parsing
- Chokidar — cross-platform file watching
- Commander.js — CLI framework
- React + Vite — web dashboard
- D3 — knowledge graph visualization
See CONTRIBUTING.md for guidelines.
MIT — see LICENSE
Built by GZOO — an AI-powered business automation platform.
Cortex started as an internal tool to maintain context across multiple client projects. We open-sourced it because every developer who works on more than one thing loses context, and we think this approach — automatic file watching + knowledge graph + natural language queries — is the right way to solve it.
