The boundary

OpenOrg is the native workspace, onboarding, integrations, and overall experience for building knowledge locally and putting it to work with people and agents.

Org2 is the open .org2 format, compiler/runtime, CLI, npm package, schemas, and editor tooling underneath it. OpenOrg reads the same ordinary files as other Org2-compatible tools.

Portability

• Ordinary .org2 and .org files are the source of truth.

• The command-line tools are org2 and org2-lsp.

• The npm package is @aviaviavi/org2.

• VS Code, Vim, Neovim, Emacs, CLI JSON, and MCP clients can work with the same corpus.

• Agent runs, workflows, approvals, citations, and provenance are inspectable corpus records.

• Any configured local, remote, hosted, or self-hosted agent can participate above the deterministic Org2 compiler.

What OpenOrg adds

• A native Mac workspace for capture, Agenda, files, meetings, agents, and review.

• A five-minute first-run path from a folder to a cited agent result.

• Clear approval boundaries for consequential actions.

• Local configuration of agent destinations and explicitly authorized context.

• Packaging, updates, diagnostics, and a coherent product experience.

Stable technical identifiers

OpenOrg uses stable bundle, preference, Keychain, executable, corpus, CLI, package, and schema identifiers. These technical contracts let the app, developer tools, and corpus work together consistently.

See Org2 language reference for the format and OpenOrg for macOS for the product client.