Plain Markdown

Open Link in Obsidian when you want a richer notes UI.

Link owns the memory lifecycle. Obsidian can be a comfortable editor and graph viewer for the same local Markdown files.

Import An Existing Obsidian Vault

Use lnk import-obsidian when you already have project notes in Obsidian and want Link agents to ingest them as source-backed knowledge. Link copies Markdown notes into raw/obsidian/<vault>/, skips Obsidian plugin state, and blocks notes with secret-looking values before writing them.

lnk init ~/link
lnk import-obsidian ~/Documents/ObsidianVault ~/link
lnk ingest-status ~/link

The import does not silently create durable memories. It stages raw source notes, then the normal ingest and proposal workflow decides what becomes wiki knowledge or reviewed memory.

Open The Link Wiki

In Obsidian, choose Open folder as vault and select your Link wiki folder:

~/link/wiki

For a project-local install, open that project's wiki/ folder instead. Link uses regular Markdown files, YAML frontmatter, and [[wikilinks]], so Obsidian can read the pages directly.

Edit Safely

Prefer editing prose, titles, aliases, tags, summaries, and source notes. Be careful with lifecycle fields on memory pages, such as status, review_status, scope, project, and source, because agents use those fields to decide what is safe to recall.

Memory rule Use Link commands or MCP tools for durable memory writes when possible. They check duplicates, conflicts, review state, and audit logs.

Keep Link Indexes Current

After manual Obsidian edits, rebuild derived indexes and validate the wiki before asking agents to rely on the new content:

lnk rebuild-index ~/link
lnk rebuild-backlinks ~/link
lnk validate ~/link
lnk health ~/link

The local web viewer is still useful for Link-specific views like health, ingest, memory review, captures, and MCP-ready query context. Obsidian is an editor/viewer for the same underlying files, not a replacement for Link's validation and memory lifecycle.