Preface

In the DSH plugin ecosystem, when agents need to generate and edit Office files, the common challenge is not “whether they can be generated,” but whether the field structure, document operations, and result verification are clear. The DSH-Office plugin is designed to solve this problem: it uses the local zagens-office to generate and edit PPTX / DOCX / XLSX / PDF, and provides a set of tools that allow the model to first retrieve the contract, then execute writing or editing.

What This Is

DSH-Office is maintained by didclawapp-ai and is licensed under MIT. It is designed for scenarios where PPTX / DOCX / XLSX / PDF read/write operations need to be integrated into DSH workflows, with the core dependency being the local zagens-office.

Core Features

The plugin provides four tools:

Tool Purpose
office_schema Retrieve the JSON contract; call this before writing or editing
office_write Create new documents
office_edit Modify existing documents using operations
office_read Read back documents for verification

The recommended flow is: first office_schema, then office_write or office_edit, and finally office_read.

Installation and Activation

Installation command:

dsh plugin --profile web add github:didclawapp-ai/DSH-Office

Startup:

dsh web

The plugin is loaded successfully when the following appears in the startup logs:

[zagens-office] plugin loaded

Node.js engine requirement:

^22.19.0 || >=24.0.0

If the engine is missing, the model will download it automatically to:

~/.zagens-pro/bin

To pin to a specific commit:

dsh plugin --profile web add github:didclawapp-ai/DSH-Office#<commit-sha>

Uninstallation:

dsh plugin --profile web remove dsh-zagens-office

Typical Usage

A reproducible workflow is as follows:

  1. Call office_schema to retrieve the JSON contract.
  2. When creating a new document, call office_write.
  3. When modifying an existing document, call office_edit and apply the operations.
  4. Call office_read to read back the document for verification.

Calling office_schema before writing or editing is intended to prevent generating or modifying documents before the fields are confirmed.

Applicable Scenarios and Notes

Suitable for: workflows where DSH agents need to process PPTX / DOCX / XLSX / PDF according to explicit JSON contracts.

Notes:

  • The plugin runs with the permissions of the current dsh process.
  • Check the source code and license before installation.
  • The plugin is licensed under MIT.
  • It uses the local zagens-office; if the engine is missing, it will be downloaded to ~/.zagens-pro/bin.

Conclusion

DSH-Office consolidates Office document generation and editing into four tools: retrieve contract, create, edit, and read back for verification. Repository: https://github.com/didclawapp-ai/DSH-Office