# Univer Workspace
**An open-source Office workspace where people and AI agents create, collaborate, and review together.**
[Univer Docs](https://docs.univer.ai/) · [Office SDK](https://office.univer.ai/) · [CLI guide](apps/cli/README.md) · [Workspace Agent](apps/agent/README.md) · [Issues](https://github.com/dream-num/univer-workspace/issues)
[](LICENSE)
[](package.json)
[](package.json)
English | [简体中文](README.zh-CN.md)
Univer Workspace is a deployable knowledge and collaboration workspace built on the
[Univer Office SDK](https://github.com/dream-num/univer). It brings Sheets, Docs, Slides,
relational tables, canvases, and more into one shared runtime, with data and
references staying connected across artifacts as the workspace changes.
Choose the Workspace Browser for direct editing, Workspace Agent for document
conversations and change review, or the CLI for automation. All three connect to
the Workspace Server, which owns document storage and permissions. Agents work in
isolated Worktrees, verify their changes, and hand the result to a person for
review. Humans can continue editing and stay in control of what gets merged.

## Why Univer Workspace
| For people | For agents | For operators |
| ------------------------------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------- |
| Organize content in Personal and Team Spaces | Create and edit rich Office content through the Univer Facade API | Deploy one Browser and Server application |
| Co-edit Sheets, Docs, Slides, Bases, and Boards | Inspect data, render screenshots/PDFs, and run layout checks | Keep product, collaboration, and Blob data under application control |
| Share content with role- and node-aware access control, including anonymous viewing | Discover version-matched Skills and APIs offline | Integrate password, GitHub, Discord, or application OAuth login |
| Use Recent, Trash, file import/export, and review views | Work through multiple rounds without changing trunk | Operate a documented HTTP API with explicit recovery boundaries |
## Spreadsheet-based mini-apps · [Watch the demo](https://youtu.be/4PBVltY_WEc)
- Agents can generate spreadsheet-based mini-apps, such as decision-making dashboards, interactive reports, and business dashboards.
- Metrics, charts, and controls on the web page are bound to cells, supporting data reads, writes, and collaborative updates.
[](https://youtu.be/4PBVltY_WEc)
## Choose your entry point
| Entry point | Use it for | Get started |
| --- | --- | --- |
| **Workspace Browser** | Edit documents directly, collaborate, organize Spaces, and review changes | [Start Workspace](#quick-start) |
| **Workspace Agent** | Chat with an agent beside your documents, reference local or remote files and folders, and review Worktree changes | [Install and use Agent](apps/agent/README.md#installation-and-first-use) |
| **Workspace CLI** | Automate document tasks from a terminal, scripts, or an existing agent environment | [CLI installation and usage](apps/cli/README.md) |
Workspace Agent is a local web application built on DSH (DeepSeek Harness). Its
local file references point to the machine running Agent; Workspace documents
remain on the connected service. Both Agent and CLI can connect to your existing
Workspace deployment or one you start locally.
## How it works
```mermaid
flowchart LR
Human([Human]) --> Browser[Workspace Browser]
Agent([AI agent]) --> CLI[Workspace CLI]
Human --> AgentApp[Workspace Agent: local conversation and review]
AgentApp --> Server
Browser --> Server[Workspace Server]
CLI --> Server
Server --> Product[(Product data)]
Server --> Collaboration[(Collaboration data)]
Server --> Blobs[(Blob and asset bytes)]
```
The Browser is the direct editing and collaboration surface. Workspace Agent
combines a conversation with document previews and Worktree review. The CLI gives
agents a structured way to load, understand, edit, validate, and render the same
content. The Server resolves authoritative identity and permissions, owns
Workspace product workflows, and composes the Univer Collaboration SDK.
Worktree turns agent editing into an explicit review workflow:
```text
create Worktree
→ agent edits and verifies an isolated draft
→ Ready
→ human reviews in the Browser or Workspace Agent
→ Merge or Reopen
→ trunk
```
Intermediate changes remain isolated from shared content until a person accepts
them. See the [CLI guide](apps/cli/README.md) for the complete product workflow.
## Quick start
These commands start the Workspace service and Browser. To add the conversation
interface, follow the [Workspace Agent guide](apps/agent/README.md#installation-and-first-use).
### Requirements
- Node.js 24 or newer
- pnpm 11
Install dependencies and prepare the application configuration:
```bash
pnpm install
cp apps/workspace/.env.example apps/workspace/.env
```
Start the Server:
```bash
pnpm workspace:dev:server
```
In another terminal, start the Browser development server:
```bash
pnpm workspace:dev:web
```
Open . Vite provides hot module replacement and proxies API
and WebSocket traffic to the Server at .
The Server can also serve the latest built Browser from port 3020 when
`apps/workspace/dist/public` exists. Its product API is available at
and
.
Configuration, authentication, storage, Docker, and database migration details live
in the [Workspace application guide](apps/workspace/README.md).
## Use Workspace Agent
Workspace Agent is a desktop app built on DSH for Univer Workspace. Reference Workspace files with `@`, create and edit documents through conversation, then review changes and choose whether to merge or discard them.
The [Agent guide](apps/agent/README.md#installation-and-first-use)
includes a prompt you can give a coding agent before cloning the repository, as
well as manual setup and usage instructions. It walks through choosing or starting
your own Workspace service, registering the OAuth callback, configuring model
credentials, and opening the complete token URL printed by the local launcher.
Desktop Agent packaging and manual CI are described in the
[desktop guide](apps/agent/desktop/README.md). Downloads use GitHub Releases;
Agent release tags never trigger automatic publication.
## Use the Workspace CLI
To use Workspace with an existing agent such as Claude, Codex, or Kimi Work, install the CLI and [Workspace CLI Skill](skills/univer-workspace-cli/SKILL.md) in the environment where the agent runs:
```bash
npm install --global univer-workspace-cli@latest
npx skills add dream-num/univer-workspace --skill univer-workspace-cli -g
```
Point the CLI at your own Workspace deployment, then begin browser-approved login:
```bash
univer-workspace-cli config set workspace.origin
univer-workspace-cli login
```
After the user approves the displayed URL and verification code, complete the
one-time exchange:
```bash
univer-workspace-cli login --complete
```
The installed package includes version-matched Skills, structured JSON output,
Facade API discovery, content inspection, PNG/PDF rendering, Office exchange, and Worktree
workflows. See the [CLI guide](apps/cli/README.md) for the complete usage and login
contract.
## Repository layout
```text
apps/workspace Workspace Browser, Server, HTTP contract, and deployment app
apps/cli Agent-ready remote Workspace automation application
apps/agent Workspace Agent application for document conversations and review
packages/client-core Private Node-hosted Workspace Agent Client capabilities
packages/reference-provider Private Browser-only referenced-Unit policy
packages/workspace-html-viewer Private shared HTML View sandbox and binding host
packages/workspace-markdown-viewer Private shared read-only Markdown preview
packages/dsh-univer-workspace-plugin Workspace Agent Workspace capabilities and browser UI
packages/dsh-univer-workspace-skin-plugin Workspace Agent Workspace visual skin
scripts SDK version and local CLI release tooling
```
This repository is the product composition root, not a replacement for the upstream
SDKs. Univer Runtime owns the Unit model, rendering, Facade APIs, and Office content
capabilities. Univer Collaboration SDK owns snapshots, revisions, OT, realtime
collaboration, and Worktree protocol contracts. Univer CLI SDK owns the reusable
headless runtime, execution, inspection, and rendering capabilities.
Workspace owns product identity, Spaces, hierarchy, ACLs, sharing, Trash, Recent,
Blob storage policy, remote workflows, and deployment. Client Core shares storage-neutral authentication,
Workspace workflows, local Node-hosted Blob/Asset transfer, and the worker-backed content runtime between
repository applications, including Node-hosted Office exchange, Typst compile/materialize/apply, render Unit
assembly, screenshots, PNG/PDF output, Slide layout lint, the render-page source, and the SVG
compile/measure/apply workflow; the reference-provider package remains Browser-only.
Both are private implementation modules, not additional public applications or SDKs.
## Architecture principles
- **One authoritative Server.** Client-provided users, roles, Resources, Units,
Worktrees, and revisions are never trusted as authority.
- **Separate storage boundaries.** Product data, collaboration state, and Blob bytes
have distinct owners and are coordinated through durable, idempotent operations.
- **Published SDK contracts only.** The repository consumes public package exports and
never depends on adjacent source checkouts.
- **One exact SDK baseline.** Version-coupled `@univer-cli/*`, `@univerjs/*`, and
`@univerjs-pro/*` packages always move together.
- **Contract-first HTTP.** OpenAPI source, generated types, Server routes, Browser, and
CLI must describe the same behavior.
Read the [technical architecture](apps/workspace/docs/architecture.md),
[application design](apps/workspace/docs/application-design.md), and
[data model](apps/workspace/docs/data-model.md) before changing these boundaries.
## Development and verification
Run the smallest relevant check while iterating, then use the repository-level suite
before claiming a complete change:
```bash
pnpm typecheck
pnpm test
pnpm build
pnpm --filter @univerjs/univer-workspace test:production-import
pnpm package:workspace-cli
```
HTTP contract changes also require:
```bash
pnpm --filter @univerjs/univer-workspace api:verify
```
Update every version-coupled Univer dependency and the lockfile with the repository
script rather than editing individual manifests:
```bash
pnpm update:univer-sdk --sdk_version
```
## Delivery model
The CLI and Workspace deployment are delivered independently from the same source:
- Manually dispatch the CLI release workflow on a stable `vX.Y.Z` tag contained in
`main` and explicitly set `dry_run=false` to publish `univer-workspace-cli@X.Y.Z`.
Creating or pushing tags never triggers CI or publication.
- Workspace deployment is a separate manual workflow. It builds either an existing
stable tag or an exact commit as `sha-`. Pushing a release tag does not
deploy the Server.
Stable CLI releases validate the repository-wide SDK baseline and test
the actual package artifact before publication.
## Documentation
| Resource | Scope |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [Univer Runtime documentation](https://docs.univer.ai/) | Browser Runtime, presets, plugins, Facade API, and editor capabilities |
| [Univer Office SDK documentation](https://office.univer.ai/) | Office SDK stack: Runtime, Collaboration, CLI, and Worktree |
| [Workspace application guide](apps/workspace/README.md) | Configuration, authentication, storage, Docker, and upgrades |
| [Workspace CLI guide](apps/cli/README.md) | Installation, login, agent workflows, and package contract |
| [Workspace Agent guide](apps/agent/README.md) | Local profile, browser OAuth, sessions, files, Worktree, and identity switching |
| [Client Core package](packages/client-core/README.md) | Private Node-hosted client capability boundary |
| [Technical architecture](apps/workspace/docs/architecture.md) | Browser, Server, storage, OpenAPI, and module boundaries |
| [HTTP contract](apps/workspace/contracts/http/README.md) | Product API source and generation workflow |
| [Reference-provider package](packages/reference-provider/README.md) | Private Browser referenced-Unit policy |
## Contributing
Issues and pull requests are welcome. Before changing code, read [AGENTS.md](AGENTS.md)
and the README or design document closest to the target. Preserve unrelated changes,
do not edit generated files by hand, and include the verification required by the
affected boundary.
## Runtime development license
The Browser and CLI contain synchronized copies of the approved runtime development
credential for local use. It rotates every 90 days and is not the repository software
license. Set `VITE_UNIVER_LICENSE` for Browser builds or `UNIVER_LICENSE` for the CLI
to override it.
## License
Univer Workspace is licensed under [Apache-2.0](LICENSE).