Org2 vs Obsidian
Obsidian and Org2 share a useful premise: important knowledge should remain in local, readable files. Obsidian has developed that premise into a mature Markdown application and ecosystem. Org2 is developing an open-source compiler/runtime and a set of clients around Org-shaped files.
Both can support serious knowledge work. The main difference is where each system places its shared runtime and how much workflow state it defines.
At a glance
| Concern | Obsidian | Org2 |
| --- | --- | --- |
| Primary experience | Polished Markdown knowledge application | Shared knowledge runtime with Mac, VS Code, CLI, and other clients |
| Source files | Local Markdown, properties, Bases files, and open JSON Canvas files | Local .org and .org2 files plus explicit generated artifacts |
| Runtime and license | Proprietary desktop/mobile app with public plugin APIs | Apache-2.0 parser, CLI, compiler, clients, and integrations |
| Maturity | Established desktop and mobile products with a large community | Early alpha with working CLI, Mac app, VS Code integration, and a private-TestFlight or source-built iOS app |
| Linked knowledge | Backlinks, outgoing links, graph, local graph, Canvas | IDs, wiki/file links, backlinks, graph reports, cited queries, and link-health operations |
| Structured views | Bases tables, lists, cards, maps, formulas, and community views | Agenda/query outputs, data notebooks, materialized SQL views, tables, and deterministic charts |
| Planning | Markdown tasks, properties, Bases, core features, and plugins | Parser-defined TODO, planning, repeater, priority, effort, habit, clock, and agenda semantics |
| Command line | First-party CLI controlling a running Obsidian app | Standalone CLI and JSON/compiler outputs that do not require a GUI client |
| Agent workflow | Core and plugin features can operate on the vault | Cited context, durable runs, approvals, validation, workflows, and artifact provenance |
| Hosted services | Optional Sync and Publish services | Bring-your-own file sync and site hosting |
Obsidian's established strengths
A mature daily application
Obsidian offers refined desktop and mobile editing, fast search, backlinks, graph views, Canvas, themes, embeds, PDF and media handling, and a large body of learning material. Optional Sync and Publish services provide supported paths for cross-device use and hosted sites.
That completeness matters. Someone who wants a polished personal knowledge app can assemble a sophisticated workflow with little infrastructure work.
Bases and visual organization
Bases stores database-like views over Markdown properties. Current core layouts include tables, lists, cards, and maps, with filtering, sorting, grouping, and formulas. Canvas supplies a visual workspace saved in the open JSON Canvas format.
Org2's data views focus more on explicit datasets, SQL materialization, freshness, and report evidence. It does not currently offer an equivalent general-purpose canvas.
Plugins and customization
Obsidian's community ecosystem covers task management, calendars, diagrams, spaced repetition, data views, imports, publishing, and many specialized interfaces. Org2 has a much smaller integration surface today.
A real command-line surface
Obsidian's first-party CLI can search and edit files, inspect tasks and links, query Bases, manage properties and plugins, and invoke application commands. The old version of this page understated Obsidian's automation support.
The architectural distinction is narrower now: Obsidian CLI controls the Obsidian runtime and requires the app to be running, while Org2's CLI is the shared standalone runtime used by its clients and automation.
Org2's current strengths
One semantic layer across clients
Org2 parsing, source ranges, agenda behavior, links, IDs, context retrieval, and artifact metadata live in the TypeScript compiler/runtime. The Mac app, VS Code integration, publishing pipeline, CLI, and agents consume that shared model.
This is useful when deterministic behavior outside the desktop app matters: CI checks, batch publishing, editor tooling, scripts, or an agent can operate on the same semantics through commands and JSON outputs.
Planning and review are part of the corpus model
Org2 defines TODO and planning behavior directly, then builds agenda views and mutations on top. It also keeps delegated work in durable run records with plans, citations, outputs, validation, clarifications, comments, retries, cancellation, and approvals.
The Mac Agent Work surface presents that state as a workflow for coordinating with agents. OpenClaw is the current end-to-end integration; the underlying records and interfaces are provider-independent.
Data, meetings, and generated work keep an evidence trail
Data notebook declarations, materialized query results, charts, meeting transcripts, generated drafts, and published output can all carry explicit provenance and review state. Files under views/ or compiled/ remain inspectable before a result is promoted into durable notes.
That structure is helpful when the workspace holds operational context as well as personal notes.
The complete stack is open source
Obsidian keeps vault content portable and publishes several open formats and developer interfaces. Org2 additionally makes the parser, runtime, Mac client, editor integration, and agent workflow implementation available under Apache-2.0.
This matters for teams that need to audit, fork, embed, or run the knowledge layer without a proprietary application dependency.
Current tradeoffs
Org2 is early alpha. Its Mac app is useful but still evolving, the iOS app is available through a private TestFlight beta or as source, VS Code has the strongest general editor integration, and the plugin/theme ecosystem is small. Packaging, capture/refile depth, visual graph exploration, and cross-platform polish remain behind Obsidian.
Obsidian's rich behavior often comes from the application, installed plugins, and vault configuration. Its files remain portable, but reproducing a complete workflow elsewhere may require reproducing those conventions and extensions as well.
A practical choice
Obsidian is a strong choice for a mature local Markdown application, broad visual tools, mobile polish, and a deep plugin ecosystem.
Org2 fits workspaces that need an open standalone semantic layer, Org-style planning, source-backed data and meeting artifacts, and durable agent runs with explicit review and approval boundaries.
The projects also point toward each other in useful ways: Obsidian demonstrates how approachable local-file knowledge software can be, while Org2 explores how much shared behavior can live below any individual client.