Office-editing tool calls need file, worktree and unit: lessons from dsh-univer-office
FunDistribution6537 · reddit · 2026-10-16
A Reddit post examines why a vague "edit spreadsheet" tool call hides too much: which file, which version, which sheet, and where the change becomes reviewable.
Univer's dsh-univer-office plugin for DeepSeek Harness makes these explicit: its execution tool takes file, worktreeId and unitId, ships its own Gateway, viewer and workers, and exposes 14 structured tools instead of a globally installed CLI.
The proposed integration contract:
- Resolve the target file and unit before editing; put proposed changes in a draft worktree.
- Read back affected content from that worktree — a successful call only means execution completed.
- Present the result for review before accepting; merge/discard paths invoke DSH's approval hook.
The author notes worktrees and approval hooks organize editing and review but don't make the JS runtime a security sandbox. The key design question for agent builders: which operations should stay explicit tool arguments even when the model can write arbitrary editing code.
More from coding & agent
- Why company AI agents go stale: adoption needs in-house knowledge, not just better agents — EdenEmarco177 · 2026-10-16
- Cheng Lou open-sources Handwired: hand-written weights turn code into training-free neural nets — dotey · 2026-10-16
- Building a portable context vault in Notion so every AI agent knows you from day one — ivanhzhao · 2026-10-16
- Lovable apps can now talk to customers on WhatsApp with inbox, reminders and templates — AlexandrePesant · 2026-10-16
- FDE-Gym benchmark: best agent fully solves only 14 of 95 real customer-delivery tasks — dair_ai · 2026-10-16
- Deep Research API showdown: OpenAI, Perplexity, Parallel, Tavily, Gemini, Valyu compared — bar_raiser333 · 2026-10-16