DingTalk’s DingTalk Workspace CLI (DWS) is an open-source, Apache-2.0 command-line tool built for people and AI agents. Reports published October 27–29, 2026 describe its HarmonyOS PC adaptation and a scope of 25 business modules and more than 1,000 commands. The announcement is about making DingTalk workflows accessible through a CLI—not replacing a graphical office suite.
18
19
8
What DWS lets agents do
DWS packages DingTalk capabilities behind standardized command-line interfaces. The reported modules include group chats, meeting notes, to-dos, AI tables, documents, calendars, contacts and approvals. Agents can use those interfaces, within user-authorized access, to help carry out tasks rather than only return text responses.
18
19
For example, launch coverage describes an agent extracting key points and to-dos from meeting notes, checking calendars to help arrange a follow-up meeting, or organizing information in an AI table. These are reported use cases, not a guarantee that every workflow is available in every deployment.
18
19
The project documentation describes structured JSON responses and built-in agent skills. For people using the CLI directly, it also documents help, request previews with --dry-run, and table, JSON or raw output formats.
33
Access controls and security claims
The project describes OAuth device-flow authentication, domain allowlisting and least-privilege permission scopes as parts of its security approach. Its documentation also says operations are subject to authentication and auditing. Separately, launch coverage says agents act within user-authorized access.
2
33
19
Those descriptions do not independently confirm every safeguard raised in the announcement’s wider coverage. The available sources do not verify details such as device-bound encrypted token storage, enforced HTTPS, path-traversal or Unicode-spoofing protections, or specific controls for skipping confirmations and filtering fields to reduce token use. Treat those details as unverified rather than assuming they are part of the implementation.
HarmonyOS PC support—and a SafeChat documentation conflict
The repository supports an openharmony/arm64 target using a Go 1.26.7 OpenHarmony toolchain. Release notes describe a static, self-signed package, a deterministic archive and SHA-256 checksum, and publication of the archive with beta and stable releases. The project says the binary has been verified on a HarmonyOS PC.
1
3
4
The available documentation is inconsistent about SafeChat, DWS’s message-encryption backend on this target. The OpenHarmony build guide says release builds enable SafeChat through a pinned OpenHarmony NDK while retaining a static binary; other package documentation says a CGO_ENABLED=0 build leaves SafeChat unavailable and that native payloads are unsupported on OpenHarmony. The sources provided do not resolve the difference, so support may depend on the build or package path. A static executable alone does not establish that every feature requiring native support is available.
1
16
43
What the “open-source” announcement establishes
Coverage on October 27 and 28 reports DWS’s HarmonyOS PC adaptation and open-source release, while an October 29 roundup also describes the tool as Apache-2.0 licensed. The dates support the timing of that coverage, but do not establish October 29 as the project’s original open-source date.
18
19
8
One launch report calls DWS the first open-source Office CLI adapted for HarmonyOS PCs. That should be read as a reported characterization, not as an independently verified market-wide comparison. The clearest practical point is that DWS offers a programmable route for people and agents to access DingTalk office workflows, subject to the project’s authentication and permission model.
18
19
2