Using Intabula with Obsidian

Intabula opens an existing Obsidian vault as-is: it reads the same Markdown files, the same YAML frontmatter, and the same [[wikilinks]]. You can run both apps against the same folder at the same time and use each for what it's best at.

What Intabula adds to an Obsidian vault

• Database views: folders become collections with typed columns, table and Kanban views, and saved views in the sidebar.
• An AI agent: a built-in agent (Claude, Codex, or OpenRouter) that edits through specific typed operations. Field and body edits change only the affected bytes, so your formatting survives, and a rename rewrites every wikilink to the record. Deleting a record can leave links pointing at it; those show up in the needs-attention inbox. The agent writes to the vault folder and to any external collections you've added, which can live in other folders.
• Schema inference: recurring frontmatter keys are offered as official columns. Violations are flagged in an inbox, and the write is not rejected.
• An iOS app: search, views, and editing on the phone, plus an optional agent that runs on OpenRouter with your own key. The vault syncs through iCloud Drive with no server. See Sync, sharing, and iOS.

What stays yours

Intabula's index is a rebuildable cache. The Markdown files remain the source of truth, in Obsidian-compatible form. Nothing in your vault is converted or locked in. If you stop using Intabula, the vault is exactly the folder it always was.

A note on agent safety

Pointing a general coding agent at an Obsidian vault gives it a shell: it can rename a file and silently break every link to it, or rewrite formatting wholesale. Intabula's agent has no shell. Its renames rewrite every wikilink atomically under a crash-recovery journal, and every change is logged with a before-and-after diff. See Write safety.