Office Copilot
Build your own Office copilot with a collaborative web app, native editors, and bring-your-own-key AI.
Univer Office Copilot is an open-source reference web app built with Univer Office SDK, LangChain, React, and TypeScript. It places editable spreadsheets, documents, slides, relational tables, and canvases beside a conversation assistant. Use the runnable code sample to build your own Office copilot.
Run locally · Editable examples · Source repository
What you can build
| Product | Applications to build |
|---|---|
| Sheets | Financial models, scenario analysis, formulas, and charts. |
| Docs | Research reports and memos in Modern or Paged Docs. |
| Slides | Editable investor decks and project presentations. |
| Base | Linked records, operations trackers, and live dashboards. |
| Board | Decision maps, workflows, and connected diagrams. |
Run the reference app locally
Use Node.js 24+ and pnpm 10.33.4:
git clone https://github.com/dream-num/univer-office-copilot.gitcd univer-office-copilotpnpm install --frozen-lockfilepnpm devOpen http://127.0.0.1:5173. A new local demo account receives six private, editable examples covering all five products and both document modes. Browsing and manual editing require no model key, Docker, or external database.
To use Copilot, open the model menu in chat and choose Add model or Manage models. Configure your provider, model ID, and API key. The app supports OpenAI, Anthropic, Google Gemini, DeepSeek, OpenRouter, and custom OpenAI-compatible HTTPS endpoints. Choose Ask to inspect a file or Edit to change the current file directly.
AI text measurement and rendered checks require local Chrome, Chromium, or Edge. See the local development guide for model configuration, attachments, import/export, and browser setup.
The application source is Apache-2.0. Embedded Univer Pro features have separate SDK licensing terms; the app does not grant a Pro license. See SDK licensing.
How Office SDK powers it
The React workspace provides the editors and chat interface. The Node backend runs the LangChain tool loop, product Skills, and bounded editing scripts against a headless Univer client. Confirmed edits reach the browser through the same collaboration channel used by people; native readback and rendered checks provide verification feedback.
Modern Docs use Markdown, Paged Docs use Typst, and Slides use SVG compiled into editable elements. The app also includes multiple conversations per file, attachment context, per-turn change inspection, native file history, owner-controlled restore, and separate file/conversation sharing.
Build on the architecture and extension guide, or explore the underlying content operations, collaboration, and history capabilities.
How is this guide?