Obsidian and Worktable: what's the same, what's different
What you'd gain, what you'd give up, and when Obsidian is still the better choice.
Karo
7 min read
People who use Obsidian sometimes ask how Worktable compares. It's a fair question. Both keep your work as files on your own machine. Both handle Markdown, links, and diagrams. Both work with agents like Claude Code and Codex.
I built Worktable, so read this with that in mind. I've tried to be straight about where Obsidian is the better tool, because for a lot of people it is.
The short version
- Obsidian is a fast, mature notes app built around you and a folder of Markdown files. It works offline on every device and has a huge plugin ecosystem. Agents are welcome guests: they can edit the files, drive the app through its official CLI, or run inside a plugin.
- Worktable is a much younger workspace for ongoing work with your agents, several at once if you like. Their edits appear in front of you (labeled as theirs). You can leave comments for them to fix and resolve, or talk with them in threads. It's open source and free to run yourself.
- You can use both. People may keep a personal library in Obsidian and run agent-heavy projects in Worktable.
In one line: Obsidian makes your notes easy for agents to reach. Worktable is built for working alongside them.
What they have in common
- Your work lives in files on your own computer, not only on someone's server.
- Documents can be plain Markdown, with links between them and Mermaid diagrams.
- Neither has a built-in AI model. You bring the agent you already use.
- Both keep history so you can roll back a bad edit.
- Both are free to use on your own computer, with an optional paid service for syncing or hosting.
Side by side
| Obsidian | Worktable | Winner | |
|---|---|---|---|
| Writing | Markdown with Live Preview. Fast and polished. | Block editor, like Notion. Docs can be stored as Markdown or rich text. | Depends: Markdown files or blocks |
| Organizing | Folders, tags, properties, backlinks, graph view, daily notes, templates | Spaces, folders, Start here pins, search across Spaces and records, temporary docs that archive themselves | Obsidian for a knowledge base. Worktable for keeping agent output tidy. |
| Connecting an agent | Point it at the folder, or use the official CLI or community MCP and AI plugins. CLI and MCP need the desktop app running. | One setup command for Claude Code, Codex, Cursor, and others. Cloud gives web assistants a hosted connection. | Even on one machine. Worktable for agents that run elsewhere. |
| Devices and offline | Native apps on Mac, Windows, Linux, iOS, and Android. Fully offline. | Mac app (Apple Silicon), command-line install on Mac or Linux, Cloud in any browser. Built to be used online. | Obsidian |
| Talking with agents | In each agent's own app, or a plugin's chat panel | Threads. Mention or assign different agents. Always-on agents reply on their own. | Worktable |
| Structured information | Bases: table, list, cards, kanban, and map views over note properties | Record collections with optional schemas, a table editor, filters, and grouping | Depends: views over notes, or data an agent keeps updating |
| Seeing what an agent changed | File Recovery snapshots, or Git or Sync history. Nothing records whether you or an agent made a change. | Edits appear in open docs live. History labels each version with who made it. | Worktable |
| Custom views and tools | 8,000+ community plugins | The agent builds HTML tools that read and update your records, in a sandbox | Obsidian for ready-made. Worktable for one-off tools. |
| Diagrams and drawing | Mermaid, Canvas, and the Excalidraw plugin for drawing and pen input | Mermaid with a fullscreen viewer. Drawings you can sketch by hand, including with Apple Pencil, that agents can see and edit. | Even |
| Giving an agent feedback | Comments hidden in the Markdown, a review note, or the chat | Comments on a passage with replies. The agent can work through open ones and resolve them. | Worktable |
| Sharing | Publish (paid site). Shared Sync vaults, with no live co-editing yet. | View-only public links. One owner per workspace. | Neither is a team tool yet |
| Moving your workspace | Copy the folder. Version history stays behind. | One export file with docs, records, comments, threads, and history. Imports into another Worktable or opens in an offline reader. | Worktable |
| Cost | Free. Sync from $4/month, Publish from $8/month (billed yearly). | Free to run locally or self-host. Cloud is $7.99/month in early access. | Obsidian, if you pay for anything |
| Source code | Closed source, free to use | Open source | Worktable |
Where Obsidian is better
Can be offline on every device
Obsidian has native apps on Mac, Windows, Linux, iOS, and Android, and your vault works with no connection at all. Worktable installs on Mac and Linux, and you can open a workspace in any browser, including on your phone. But there's no native mobile app, no Windows install, and it's built to be used online.
Thinking in links
The graph view, tags, daily notes, and templates make Obsidian good at building up a personal knowledge base over years. Worktable tracks links and backlinks, but it isn't designed for that kind of note-by-note connection work.
The ecosystem
There are more than 8,000 community plugins and 800 themes. Whatever you want, someone has probably built it. That includes in-app agents: the Copilot plugin can run Claude Code, Codex, or opencode inside Obsidian, and Obsidian's CEO publishes skills that teach agents its file formats.
Files that outlast the app
Obsidian's philosophy is file over app: your notes should be readable long after any tool is gone. A vault is a folder of Markdown you can open anywhere. Worktable keeps files on disk too, but in several formats, so not everything is plain Markdown.
Where Worktable is better
Connecting an agent is the product
One command connects Claude Code, Codex, Cursor, and others, and the agent gets tools for docs, records, drawings, comments, and threads, instead of just raw files. With Cloud, assistants running elsewhere (ChatGPT, Claude on the web, an always-on agent) can reach your workspace without your laptop being open. With Obsidian, the CLI and community MCP servers both need the desktop app running.
Talking with your agents
Threads keep conversations with your agents inside the workspace. A thread can include several agents: mention one to get its attention, or assign a message to the one that should answer. An always-on agent such as OpenClaw picks up messages and replies while you're away. In Obsidian, each conversation lives in that agent's own app or a plugin's chat panel.
Knowing what the agent did
When an agent edits a doc you have open, you see the change appear. Only the blocks it changed update, so your typing elsewhere in the doc is undisturbed. History labels each version with who made it. In Obsidian, an agent's edit and yours look the same afterwards unless you track it yourself with Git.
Giving feedback that sticks
Highlight a passage and leave a comment. It stays attached to that passage. Next session, ask the agent to work through open comments. It fixes the doc, replies, and resolves the thread, so you can see what was handled. Obsidian's %%comments%% are hidden notes in the file, with no replies or resolved state.
Keeping agent output tidy
Agents produce a lot of drafts, notes, and scratch work. In Worktable a doc can be temporary: it archives itself a week after its last change unless you keep it. Archived docs stay searchable and can be restored. Each Space has Start here pins for the brief and current plan, so you and the next agent know where to begin.
Records and small tools
A list of things with the same fields (venues, candidates, bugs) can be a record collection with a schema, which an agent can update reliably. The agent can then build an HTML tool on top: a weighted comparison, a budget calculator, a timeline, a tracker, etc. It lives next to the docs and data it uses and runs in a sandbox with network access off by default. Obsidian's Bases gives you excellent views over note properties, but a custom tool there usually means finding or writing a plugin.
Open source
Worktable's code is public under the AGPL. You can read exactly how your work is stored, run it on your own server, and keep running it whatever happens to the company. Obsidian is free but closed source. It makes the same promise a different way, through open file formats.
Matters of taste
Blocks or Markdown
Obsidian's Live Preview keeps every note a plain Markdown file while showing formatting as you type. Worktable's editor works in blocks you can drag, convert, and embed diagrams in, more like Notion. You can still store a Worktable doc as Markdown, copy it as Markdown, or print it to PDF. If you want every document to stay a hand-editable text file, Obsidian's model is simpler.
One format or several
An Obsidian vault is uniform. A Worktable workspace mixes Markdown, rich docs, YAML records, drawings, and HTML, because the same idea doesn't fit every kind of work. That makes it better at moving a whole workspace and worse at being read by other apps.
Using both
Nothing stops you from keeping your long-running notes in Obsidian and trying one active project in Worktable. Just decide which tool owns anything that changes. There's no sync between them.
Trying it
Bring one real piece of work. Have an agent draft something, give it feedback, and come back to it a few days later. Pick the tool that makes that loop feel clearer.
Prices and features as of October 2026.