kotobase
Menu

Obsidian, no need to surrender your vault

Technical details, legal documents and some account steps still dey for English.

Make you dey write for Markdown. Turn links to answers, give AI only the context wey e need, and keep one history wey you fit reproduce and leave behind.

Your notes don already get graph

Ask pass folder dem

Find people, decisions, sources, and open questions wey connect across years of notes—not only pages wey get the same keyword.

Give AI context, no be your whole vault

Query the relevant relationships for one task and pass that limited result to agent. Your vault no need turn one big prompt.

Make sync no dey do silent winners

When local and remote copies both change, Kotobase dey keep the remote version for conflict file and e go wait for your clear resolution instead of overwriting your work.

Come check the evidence again

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

Wetin still remain na your own

Markdown na the source of truth

Notes, frontmatter, and [[wikilinks]] still dey normal files for your vault. Kotobase dey add queryable graph beside dem; e no dey replace Obsidian with proprietary editor.

E get exit path

Stop syncing and the vault still dey work. Portable Datomic transaction EDN export dey available for migration, audit, or self-hosted workflows.

Use narrow identity

Connect dedicated editor service account wey limited to graph read and write. Tokens go only the configured Kotobase origin; remote paths no fit escape vault or write inside .obsidian.

Start with the vault wey you don already get

Current scope

The current plugin dey sync Markdown notes, frontmatter, wikilinks, renames, and tombstones. Attachments, Canvas files, and Obsidian plugin settings no dey synchronized. Installation dey use repository build now instead of Obsidian community-plugin directory.