Skip to content

Exocortex

A personal knowledge OS that thinks while you sleep.

Exocortex is not a notes app. It is a self-hosted reasoning engine — a typed graph plus an LLM synthesiser plus a hybrid retriever — that ingests what you read, hear, and decide, and compiles knowledge from it on its own schedule.

Obsidian, Notion, Telegram, and the shell are interchangeable surfaces. The brain lives in Postgres.

What it does

  • Ingests automatically — meetings (Fireflies), newsletters (Gmail), RSS feeds, and any Markdown file you drop in your vault are pulled in on a schedule.
  • Builds a typed graph — every fact becomes a node; relationships are typed edges (causes → / contradicts → / cited_in →). Powered by Postgres + pgvector + Apache AGE.
  • Synthesises while you sleep — an LLM runs nightly over the graph and rewrites your wiki/ from scratch: meeting summaries, client dossiers, topic deep-dives, contradiction flags.
  • Answers in context — 15 MCP tools give Claude (or any MCP client) access to GraphRAG retrieval over your own knowledge, with ranked source provenance.
  • Sends alerts — Telegram bot surfaces resurfaced notes, action items, and contradictions it found while you were away.
Sources          Graph (Postgres)     Wiki (Markdown)    Query
─────────────    ────────────────     ───────────────    ─────
Obsidian .md  →  thoughts             _home.md        →  MCP tools (15)
Gmail / RSS   →  + pgvector           clients/*.md       GraphRAG ask
Fireflies     →  + AGE graph          meetings/*.md      Telegram bot
Notion tasks  →  edges (35 types)     by-tag/*.md

When it makes sense

  • You generate more notes than you can manually revisit.
  • You want a system that surfaces connections, not just stores links.
  • You're comfortable with a local Postgres + Python stack.
  • You want LLM reasoning over your own graph, not a cloud knowledge base.

It does not make sense if you want a hosted SaaS, a drag-and-drop UI, or a system another person manages for you.

A real example

You: "What did I decide about the auth architecture last quarter?"

Exocortex: Based on 3 synthesised notes and 2 meeting summaries from Oct–Dec:
  → Decision: JWT stateless, no session store (2024-11-14, meeting with @alice)
  → Contradicted by: email thread 2024-12-03 — "reconsider session invalidation"
  → Action item (unresolved): spike Redis session store before v2 launch

Sources: [meeting:acme-2024-11-14] [email:thread-4a2f] [note:auth-spike-dec]

Where to go from here

If you want to… Start with
Run Exocortex in 5 minutes Quickstart
Configure for your own vault Configuration
Understand the full design Why Exocortex
Build a plugin from scratch Writing a plugin
Look up an MCP tool MCP tools reference
Understand the architecture Architecture overview

GitHub: hretheum/exocortex · PyPI: pip install exocortex-os · Docker: ghcr.io/hretheum/exocortex:v0.1.0