What Is Univer? An Agent-Native Office Runtime

Updated

Univer is an office harness for AI agents: a single runtime that handles spreadsheets, documents, slides, canvases, relational tables, and PDFs, and turns office files into structured, verifiable code. It fits you if you're building a product that needs multiple office tools working on the same data, or if you want agents to edit real office files with human review rather than one-shot generation. It is not a standalone office app you download — the site positions it as an SDK plus a runtime you embed and self-host.

The core idea: one runtime, six tools

Most office stacks are separate applications that happen to share a file format. Univer inverts that: six tools share the same storage and computation layer, so they can compose and embed freely.

Tool What the site claims
Spreadsheet Full engine, web rendering of 10 million cells, 500+ built-in functions, PivotTables, sparklines, 31 editable chart types
Docs Typesetting engine with Word-class layout and Notion-like editing, headers/footers, pagination, section breaks, multi-column layout
Slides Part of the same .univer file model
Canvas Lays out other blocks
Relational Table Structured data alongside the document tools
PDF Editor Listed as one of the six tools

The practical consequence: a slide can hold a live sheet, a doc can cite its source, and a canvas can lay it all out — with references updating when sources change. That's the difference between "export a chart image into a deck" and "the deck reads the sheet."

Why "agent-native" matters

The site's framing is that every file becomes structured, verifiable code. Three mechanisms back that up:

  • Isolated worktrees. Multi-agent workflows run on worktrees, parallel by default. Agents don't fight over one mutable file.
  • Human-reviewed changes. Changes are reviewed by design, not as an afterthought — you can trace every edit.
  • Shared context across file types. Agents work across every file type without losing context, because the tools share one runtime rather than passing files between apps.

The site lists compatibility with OpenCode, Claude Code, OpenClaw, Hermes, Codex, WorkBuddy, and Kimi Work, so the harness is meant to sit under whichever agent you already use.

What you actually build with

Univer ships as an Office SDK. According to the site, you can:

  • Build with all six office tools and multi-agent worktrees inside your own product
  • Build your own UI and UX on top of the SDK
  • Self-host and connect your own auth, databases, and knowledge bases
  • Customize formulas, assets, and components down to the engine
  • Use one integration for all six tools, composed and embedded freely

There's a copyable SDK prompt and a live demo linked from the page if you want to evaluate before committing.

When Univer is the right choice

Choose it when your product needs more than one office surface sharing the same data, when agents must edit files with reviewable diffs, or when you need to self-host and wire in your own auth and storage. Look elsewhere if you want a finished end-user office suite, or if a single embedded spreadsheet is all you need — the six-tool runtime is the point, and you'd be paying for scope you don't use.

The site's own summary is the cleanest test: "Not one tool — the whole runtime." If that sentence describes your requirement, start with the SDK prompt and the live demo.