Skip to content
2 min

Get started

Choose Runtime, Collaboration, CLI, or Worktree based on your goal and find the canonical Univer documentation.

Univer is an SDK stack for building Office applications in which humans and AI Agents operate the same content. Runtime provides the Web editor, Collaboration SDK provides a self-hosted authoritative collaboration service, and CLI SDK lets Agents read and edit the same Unit. With Worktree, Agent changes become isolated, reviewable, and mergeable.

Choose an entry point by goal

GoalUseStart
Embed an Office editorRuntime SDK to display and edit Sheets, Docs, Slides, Boards, and BasesRuntime quick start
Add self-hosted realtime collaborationCollaboration SDK so multiple Clients can edit one authoritative UnitCollaboration SDK quick start
Let Agents read and edit contentCLI SDK to inspect, edit, and validate Units in Node.jsCLI SDK overview
Make Agent changes reviewableWorktree to isolate changes for human review and mergeComplete Worktree workflow

How the two documentation sites relate

DocumentationCanonical scope
docs.univer.aiRuntime SDK, frontend editor features, presets, plugins, and Facade API
office.univer.aiApplication architecture, self-hosted Collaboration SDK, CLI SDK, and Agent Worktree

Both sites describe the same Univer stack. Start in the Runtime documentation when building a Web editor. Return here when adding the new self-hosted collaboration backend or an Agent entry to that application.

How a complete application fits together

An application that supports both human editing and Agent operations typically has Web, CLI, and Server surfaces:

Web provides display, interactive editing, and human review. CLI is the Agent content interface. Server is their shared content authority. These components are composable and can all run locally. See the Univer SDK overview for the complete ownership model.

A practical adoption sequence is:

  1. Build an editable Web application with the Runtime documentation.
  2. When multiple users need to synchronize, complete the Collaboration SDK quick start.
  3. When the application needs an Agent entry, complete CLI content loading and editing.
  4. Add Worktree when Agent changes require isolation and human review.

Example collections

Teaching examples

Application examples