Commands and compatibility

• Install with npm install -g celorga.

• The commands are celorga and celorga-lsp. org2 and org2-lsp remain installed as compatibility aliases, so existing scripts, MCP configurations, and editor settings keep working.

• Existing .org2 files, org2.json, and ORG2_* environment variables and properties keep working; no rename is required.

Existing Org notes

• Keep your current .org files.

• Point Celorga CLI/editor tooling at your existing notes directory.

• No bulk rewrite is required.

New files

• Use .org for notes and other documents.

• The Celorga app, CLI, LSP, and editor integrations save accepted shorthand in ordinary Org syntax when the target file ends in .org.

Roam link migration

• Existing [[id:...]] links stay supported.

• New links can use [[Node Title]] when title-based linking is preferred.

• In mixed bases, both forms can coexist.

Recommended transition policy

1. Keep historical ID links untouched.

2. Prefer [[Title]] links for new writing when titles are stable.

3. Reserve explicit IDs for collision-prone or machine-generated workflows.

Compatibility caveats

• Celorga targets practical parity, not bug-for-bug GNU Org behavior.

• Some extension-specific editor UX differs from Emacs org-mode/org-roam.

• Re-run CI/automation commands after migration changes (agenda, roam db-sync, publish) to validate behavior in your environment.