kotobase
Menu

Obsidian, without surrendering your vault

Keep writing in Markdown. Turn links into answers, give AI only the context it needs, and keep a reproducible history you can leave with.

Your notes already contain a graph

Ask beyond folders

Find the people, decisions, sources, and open questions connected across years of notes—not only pages that contain the same keyword.

Give AI context, not your whole vault

Query the relevant relationships for a task and pass that bounded result to an agent. Your vault does not have to become one giant prompt.

Sync without silent winners

When local and remote copies both change, Kotobase preserves the remote version in a conflict file and waits for your explicit resolution instead of overwriting your work.

Revisit the evidence

Each graph commit is content-addressed. Keep the CID beside an AI answer or decision and return to the same knowledge snapshot later.

What remains yours

Markdown is the source of truth

Notes, frontmatter, and [[wikilinks]] remain ordinary files in your vault. Kotobase adds a queryable graph beside them; it does not replace Obsidian with a proprietary editor.

There is an exit path

Stop syncing and the vault still works. A portable Datomic transaction EDN export is available for migration, audit, or self-hosted workflows.

Use a narrow identity

Connect a dedicated editor service account limited to graph read and write. Tokens go only to the configured Kotobase origin; remote paths cannot escape the vault or write into .obsidian.

Start with the vault you already have

Current scope

The current plugin syncs Markdown notes, frontmatter, wikilinks, renames, and tombstones. Attachments, Canvas files, and Obsidian plugin settings are not synchronized. Installation currently uses the repository build rather than the Obsidian community-plugin directory.