Comparisons
Intabula is a Markdown notes app for Mac where you work on your notes alongside an agent. This page compares it with the tools it most often gets compared with and says when the other tool is the better fit.
Intabula vs Obsidian with plugins
You can approximate parts of Intabula inside Obsidian by combining plugins: an AI or agent plugin, a database view, and often an MCP server and an API key. Intabula includes the agent and database views in one app, and Claude or Codex run on your plan with no API key. It runs on the same vault, so you can use both.
| Plugin stack | Intabula | |
|---|---|---|
| Assembly | Several plugins by different authors, on different update cycles | One app; connect Claude, Codex or OpenRouter once |
| AI billing | Usually your own API key, per-token | Your existing Claude or ChatGPT plan, or your own OpenRouter key for open-weight models |
| Write safety | Guardrails you configure yourself, if the plugin offers them | A fixed set of operations: byte-exact edits, journaled atomic renames, activity feed with before/after diffs, optional approval mode |
| Database views | Bases, a core plugin, adds table, card, list and map views over note properties, with filters and formulas, and no Kanban view yet; community plugins such as Dataview use a query language | Built-in table and Kanban views with typed, inferred schema |
| Reading a codebase | Depends on the plugin; access is often unrestricted when offered | Linked folders: read-only, path-fenced, secrets blocklisted, Git history included |
| Mobile | Varies by plugin; some agent plugins are desktop-only | iOS app with views, search and editing, and its own agent on OpenRouter |
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 fields, views and agent work. See Using Intabula with Obsidian.
Intabula vs Apple Notes
Apple Notes comes with every Mac and iPhone. With Apple Intelligence it adds Writing Tools that proofread, rewrite and summarize text you select. It keeps notes in its own library, synced through iCloud. Intabula keeps notes as Markdown files and adds typed fields and an agent that can change many notes at once.
| Apple Notes | Intabula | |
|---|---|---|
| Where your data lives | The Notes library, synced through iCloud or kept on the device | Plain Markdown files in a folder you choose |
| Structure | Folders, tags, smart folders, checklists, and tables inside a note | Collections with typed fields, table and Kanban views, saved views |
| AI | Writing Tools and summaries on selected text; no structured fields or table views for it to work on | An agent that queries and edits records and fields across the vault, with a diff for each change |
| Private notes | Locked notes, protected with your device password or a separate password | Encrypted collections that the agent is refused access to |
| Devices | iPhone, iPad, Mac, and iCloud.com in a browser | Mac with Apple Silicon, and iPhone |
| Price and account | Free with an Apple Account | Free, no account |
When Apple Notes is the better choice
You want notes on all your Apple devices with nothing to set up. You write by hand with Apple Pencil, scan documents, or edit shared notes live with other iCloud users. Your notes are mostly free-form and don't need fields or views.
When Intabula is the better fit
Your notes track things with fields such as status and due date, and you want to see them as a table or board. You want an agent that can work through many notes at once and show you each change. You want the notes as files that other tools can open.
Intabula vs Notion
Intabula and Notion share a core idea: a database row can hold a full document. The table below lists where they differ.
| Notion | Intabula | |
|---|---|---|
| Where your data lives | Notion's cloud | Plain Markdown files on your disk |
| Leaving | Export step, format conversion | The notes are already Markdown files in your folder |
| Schema | Designed upfront per database | Inferred from recurring fields; values that don't match are saved and flagged in an inbox |
| What the agent can change | Anything in the workspace you can edit, with your permissions; it can also propose edits for you to approve | Only the vault, through a fixed set of operations with no shell; byte-exact edits, journaled renames, an activity feed with diffs, optional approval mode |
| Agent reading your code | Through the GitHub AI connector on Business and Enterprise plans; no local repository | A local repository linked as a read-only folder, with git_log/git_show/git_diff |
| Sharing | Workspace invites, per-member pricing on paid plans | A shared folder (iCloud, Dropbox); the schema and saved views live in a hidden .intabula folder inside it |
| AI billing | Notion AI is included in the Business and Enterprise plans; Free and Plus get a limited trial | Your existing Claude or ChatGPT plan through Claude Code or Codex (no API keys), or open-weight models via OpenRouter credits |
| Offline | Pages you make available offline | Fully local |
| Undo and recovery | Page history and a trash for deleted pages; history length depends on plan | No trash: a delete removes the file. The activity feed shows the earlier text of agent edits as a diff, with no restore button. Use Time Machine or Git for recovery |
| Encrypted notes the AI can't read | No end-to-end encrypted pages | Encrypted collections stay ciphertext on disk and in sync, and the agent is refused access |
| Price and account | Notion account; free plan plus paid plans | Free, no account; the agent uses your own AI plan or OpenRouter credits |
When Notion is the better fit
Team wikis where many people edit at once and need page-level permissions. Publishing pages to the web. Workflows built on Notion's integrations and templates. Intabula is built for one person per vault and has no user accounts or permission roles.
When Intabula is the better fit
You want your notes as files you own, which you can grep, sync and open in Obsidian, with database views on top. You want an agent that works through a fixed set of operations inside your vault and logs each change; outside the vault it can search the web, fetch pages and read folders you link. Your notes reference a codebase on your machine. You want to share a folder and have no seats to administer.
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. A rename can break every link to the file, and a one-word edit can come back as a reformatted document. Intabula runs Claude Code or Codex without a shell and gives it a fixed set of vault operations instead.
| Coding agent + vault | Intabula | |
|---|---|---|
| Write surface | Shell, arbitrary file read/write/edit | A fixed set of vault operations; no shell |
| Renames | Find-and-replace across files, best-effort | One atomic operation rewrites every wikilink, under a crash-recovery journal |
| Formatting | Whole-file rewrites can reformat everything | Splice edits rewrite only the changed segment; every other byte stays as it was |
| Crash mid-task | Half-migrated files | Single operations that touch several files (record rename, move, collection rename) are journaled and finish on next launch. A multi-record task interrupted halfway stays partly done |
| Audit trail | Whatever the terminal scrollback kept | Activity feed with before/after diff for every write |
| Schema consistency | None; improvised per file | Collections carry a typed schema; values that don't match it are saved and flagged in the inbox |
| Scope | Whole filesystem unless you configure otherwise | The vault, explicitly linked read-only folders, web search and page fetches |
| 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. It can run 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 coding agent in your notes folder you end up reading every diff, so you keep the jobs you hand it small. In Intabula you can ask it to tidy a folder of notes or fill in a field across all of them, then check the result in the table view, with each change in the activity feed.