High-level differences

• Runtime model

  • Org Mode: deeply integrated with Emacs runtime.

  • Org2: standalone parser/CLI/LSP, editor integrations on top.

• Workflow center

  • Org Mode: Emacs commands and buffers first.

  • Org2: editor integrations first, powered by a shared CLI/LSP backend.

• Portability

  • Org Mode: strongest inside Emacs.

  • Org2: designed for cross-editor usage from day one.

Compatibility stance

• Existing .org files are supported as an everyday workflow.

• New files are recommended as .org2.

• Aim: drop-in replacement for most Org Mode users over time.

• 100% feature-for-feature parity with GNU Org is not the goal.

What Org2 has today

• Core syntax parsing: headings, drawers/properties, links, lists, blocks, tables, timestamps.

• Task workflows: TODO state changes, planning updates.

• Agenda querying with rich filtering.

• Roam-adjacent workflows (IDs, backlinks, node creation, wiki links).

• HTML export/publish pipeline.

What Org2 does not have yet

• Full Org Mode feature parity.

• Mature habits/clocking/recurrence ecosystem.

• Equivalent depth of ecosystem integrations.

Direction

Org2 is meant to eventually replace Org Mode for most workflows.

• Keep the battle-tested core ideas that made Org great.

• Drop accumulated cruft that slows down portability and adoption.

• Support more editors natively, while also supporting Emacs well.

• Keep portability as the non-negotiable center.

• Treat CLI capabilities as shared infrastructure for editor integrations and automation, not as the primary end-user UX.