dream-num/openclaw-univer-office/univer-office

Univer Office

Use the univer_office_* tools for Office artifact work. The remote Workspace is authoritative; do not replace this workflow with a local spreadsheet, document, or slide writer.

Identity and isolation

• Keep space_id, node_id, resource_id, unit_id, and worktree_id distinct.
• Start every new user task in a new Worktree.
• Reuse a Worktree only for rework on that same known task. Reopen a ready Worktree before editing.
• Never reuse a merged or discarded Worktree.
• Find an existing file by stable Resource identity before staging it. Do not pick an ambiguous name.

Collaboration mode

• For live multi-user work, use a Team Space Worktree with scope: "space" and

visibility: "space". This requires OpenClaw approval because it expands who can see the draft.

• For a private Agent draft, use scope: "user" or keep Team Space visibility private.
• Use set_visibility only for an existing Team Space Worktree. Changing it to space also requires

approval.

• Space visibility does not create anonymous access. Collaborators must sign in and belong to the

owning Team Space; a shared URL alone grants nothing.

• review_url may be used while the Worktree is draft for live co-editing. Before final

verification, coordinate with collaborators, inspect the latest content, and avoid marking Ready while someone is still editing.

• The plugin's configured viewerUrl supplies the shareable Web base URL. It must point at the

complete Univer Workspace application, not a standalone editor or review shell. It does not start a server, change workspace.origin, or expose the OpenClaw Gateway.

Workflow

1. Call univer_office_connect with status. If unauthenticated, call start_login, show the URL

and code, and stop. Call complete_login only after the user confirms browser approval.

1. Discover the target Space and file with univer_office_files.
2. Create a Worktree with univer_office_worktree. Stage an existing resource_id, create a new

Unit, or import an Office file from the active OpenClaw workspace.

1. Before authoring, call univer_office_content with guidance for core and the Unit type.

Use api_find or api_show instead of guessing Facade methods.

1. Edit with execute. Read back with inspect; recalculate or lint where relevant.
2. Use univer_office_handoff with screenshot for visual verification. Inspect Sheet layout,

Doc pagination, every Slide page, and the relevant Base or Board view.

1. For live collaboration, request review_url after the Unit exists and share it with authorized

Team Space members. For final handoff, mark the Worktree ready, read it back, then return the same URL together with the Worktree and Unit ids. The URL opens Univer Workspace on phone and PC.

1. Reopen for requested changes. Merge or discard only after an explicit user request and the

OpenClaw approval prompt.

1. Export only when the user needs an .xlsx, .csv, .tsv, .docx, or .pptx deliverable.

Send the returned local path through OpenClaw's normal message/file delivery surface.

Approval boundary

• Univer ready means ready for review; it does not modify the current file version.
• Univer merge/discard controls the Office content lifecycle.
• OpenClaw plugin approval controls consequential agent actions such as merge, discard, or

completing sign-in. Normal channel delivery remains owned by OpenClaw.

• Never treat one approval as permission for the other layer.

Result quality

Command success is not correctness evidence. A completed artifact needs structural readback plus visual inspection when layout matters. Return useful next steps and stable ids, not a bare success.