A spreadsheet agent should leave you something you can correct before accepting it.

Suppose an agent updates a staffing budget correctly except for one contractor it puts in the wrong department. An “approve” button below its summary is a frustrating place to discover that. The reviewer needs to open the actual sheet, fix the assignment, and see what happens to the totals. Univer has a documented way to build that handoff. It is an SDK for putting spreadsheet, document and slide editors inside an application. Its AI SDK operates on the underlying office content, and its Collaboration SDK adds Worktrees: separate drafts with their own content and revision state, away from the main version. For a budget update, the agent could work in that draft while the existing budget remains available. The reviewer can open the draft in the web editor and inspect or change the cells. There are separate steps for committing edits to the draft, marking a version Ready for review, and merging it into the main version. Ready freezes the review version; Reopen allows more editing if a correction is needed. That separation answers a very practical question: which version did the person actually review? It also means “the agent committed its work” does not have to mean “the budget everyone uses has changed.” This needs an application built around it. the application still controls reviewer identity, permissions and what happens after a merge. And a person can still approve the wrong numbers. The useful part is giving that person the editable work and a defined review version, instead of requiring them to judge everything from the agent’s account of what it did.