Comparisons
Intabula is a local-first Markdown notes app with a built-in, sandboxed AI agent. Here's how it relates to the tools it most often gets compared with — including when the other tool is the better fit.
Intabula vs Notion
Intabula and Notion share a core idea: a database row can hold a full document. The genuine differences are where the data lives, how schema comes to be, what the AI agent can reach, and how sharing works.
| Notion | Intabula | |
|---|---|---|
| Where your data lives | Notion's cloud | Plain Markdown files on your disk |
| Leaving | Export step, format conversion | Delete the app; the folder remains as-is |
| Schema | Designed upfront per database | Inferred from recurring fields; violations flag to an inbox instead of being blocked |
| Agent boundaries | Platform-defined | Specific typed operations, no shell; byte-exact edits, journaled renames, activity feed with diffs |
| Agent reading your code | No | Yes — linked repository folders with read-only git_log/git_show/git_diff |
| Sharing | Workspace invites, per-seat pricing | A shared folder (iCloud, Dropbox); schema travels in a dotfile |
| AI billing | Notion subscription/AI add-on | Your existing Claude or Codex subscription; no API keys |
| Offline | Limited | Fully local |
When Notion is the better fit
Team wikis with many concurrent editors, granular permissions, publishing pages to the web, and workflows built on Notion's integrations and templates. Intabula is single-user at the core and deliberately has no accounts, roles, or server.
When Intabula is the better fit
You want your notes as files you own — greppable, syncable, Obsidian-compatible — with database views on top. You want an AI agent that maintains the workspace but provably can't reach beyond it. Your notes should reference a real codebase. And you'd rather share a folder than administer seats.
Intabula vs the Obsidian plugin route
You can approximate parts of Intabula inside Obsidian by assembling plugins: an AI/agent plugin, a database plugin, an MCP server, API keys, and your own guardrail configuration. Intabula is that stack as one integrated app — safe by default, no keys — and it runs on the same vault, so this isn't either/or.
| Plugin stack | Intabula | |
|---|---|---|
| Assembly | Several plugins by different authors, on different update cycles | One app; open a folder and the agent is already harnessed |
| AI billing | Usually your own API key, per-token | Your existing Claude or Codex subscription |
| Write safety | Guardrails you configure yourself, if the plugin offers them | Typed operations only: byte-exact edits, journaled atomic renames, activity feed with before/after diffs, optional approval mode |
| Database views | Depends on a separate plugin's query language | Built-in table and Kanban views with typed, inferred schema |
| Reading a codebase | Rarely supported; typically unrestricted if it is | Linked folders: read-only, path-fenced, secrets blocklisted, Git history included |
| Mobile | Most agent plugins are desktop-only | iOS companion app for views, search, and editing |
Using both
Intabula reads an Obsidian vault as-is and doesn't conflict with Obsidian running on the same folder. A common setup: write and think in Obsidian, and use Intabula for structure, views, and delegating upkeep to the agent. See Using Intabula with Obsidian.
Intabula vs a coding agent on your notes
You can point Claude Code, Codex CLI, or Cursor at a notes folder today. The agent gets a shell and generic file tools — which works, until it doesn't: a rename silently breaks every link to the file, a one-word edit reformats the whole document, a crash mid-task leaves the vault half-migrated. Intabula is the same class of agent with the shell taken away and a typed toolbox put in its place.
| Coding agent + vault | Intabula | |
|---|---|---|
| Write surface | Shell, arbitrary file read/write/edit | Specific typed vault operations; no shell |
| Renames | Find-and-replace across files, best-effort | One atomic op rewrites every wikilink, under a crash-recovery journal |
| Formatting | Whole-file rewrites can reformat everything | Splice edits — only the changed segment; every other byte survives |
| Crash mid-task | Half-migrated files | Journal recovery completes the operation on next launch |
| Audit trail | Whatever the terminal scrollback kept | Activity feed with before/after diff for every write |
| Schema consistency | None — improvised per file | Collections carry typed schema; new records match it |
| Scope | Whole filesystem unless you configure otherwise | The vault, plus explicitly linked read-only folders |
| Views on the result | None | Table and Kanban views, saved views, search, phone access |
Where a coding agent is still the right tool
Working on code. Intabula doesn't replace Claude Code or Codex in a repository — in fact it can sit beside them: attach the repo to a collection as a read-only linked folder and keep decision records, tickets, and architecture notes that cite the actual commits.
The practical difference
With a shell-equipped agent you review every diff, so delegation stays small. Intabula's typed write path is what makes volume reasonable — a thirty-record backfill you scan as a table column, with every change logged.