Stop re-introducing yourself to your AI.

Why this exists

You've already written everything. Your standups, your design docs, your half-finished thoughts. The problem isn't capturing knowledge — it's making it usable by the agents you work with every day.

It's not another chat UI bolted onto Obsidian. It's the connective tissue that makes your existing AI tools dramatically more useful.

Quick start — Local Docker (private)

Run everything on your machine — your notes never leave the laptop.

1. 1
   Install the plugin and switch Mode to 🏠 Local (Docker).
2. 2
   Open LLM provider keys and paste at least one key — Gemini, OpenAI, Anthropic, Moonshot, HuggingFace, OpenRouter, or xAI. Or skip the keys and run Ollama locally for fully offline.
3. 3
   Click Save to vault — writes docker-compose.cortex.yml next to your notes with your keys baked in (encrypted at rest).
4. 4
   Open a terminal in your vault folder and run:

   docker compose -f docker-compose.cortex.yml up -d

   Prefer not to use a terminal? Hand this step to Claude Code, Cursor, or Cline →

   Paste the prompt below into any agentic coding assistant. It checks Docker is running, starts the stack, polls the health endpoint, and surfaces logs if something fails — same prompt the plugin's “Copy LLM setup prompt” button uses.

   You're helping me bring up the HangarX local stack for the Obsidian plugin
   (https://community.obsidian.md/plugins/hangarx). Be terse — one update per
   phase, no narration.
   
   1. Find docker-compose.cortex.yml at the root of my Obsidian vault. Ask me
      for my vault path if you can't infer it. If the file doesn't exist,
      stop and tell me to open Obsidian → Settings → HangarX → Local mode →
      click "Save to vault" in step 2, then re-run this prompt.
   
   2. Verify Docker is ready: `docker --version` and `docker ps` both
      succeed. If Docker Desktop isn't installed, point me to
      https://www.docker.com/products/docker-desktop/ and stop. If installed
      but not running, launch it (`open -a Docker` on macOS) and wait until
      `docker ps` succeeds before continuing.
   
   3. cd to my vault and run:
      docker compose -f docker-compose.cortex.yml up -d
      First run pulls hangarx/cortex-api, falkordb/falkordb, and
      pgvector/pgvector:pg16 — expect a few minutes.
   
   4. Poll `curl -sf http://127.0.0.1:3400/health` every 3 seconds for up
      to 90 seconds. If it doesn't come up, show me the last 30 lines of
      `docker compose -f docker-compose.cortex.yml logs cortex-api`.
   
   5. Once healthy, tell me to open Obsidian's command palette and run
      "HangarX: Sync". The plugin's settings page will flip from the
      three-step wizard to "✓ Local stack running" on its next probe.
   
   If anything fails:
   - Port 3400 in use → `lsof -i :3400`. Either stop that process or
     change CORTEX_PORT in the compose file and re-run with
     `up -d --force-recreate`.
   - cortex-api exits immediately → check the logs. Most common: missing
     LLM provider key (re-save the YAML from Obsidian with a key
     configured) or Postgres healthcheck failing on first boot
     (`docker compose down -v` and retry).
   
   Don't generate the docker-compose file yourself — the plugin owns it
   (encryption keys + provider keys are baked in by Obsidian so re-saves
   stay in sync). If the file is missing or broken, hand control back to
   the plugin's "Save to vault" button.

5. 5
   Switch back to Obsidian — the connection pill turns green when the stack is up. Run HangarX: Sync from the command palette (⌘P) to push your vault.

Requires Docker Desktop. No source code, no Node.js, no compile step — images are pulled from Docker Hub.

Inside Obsidian

You don't have to use external agents. The plugin ships with:

Commands