DingTalk Open-Sources DWS and Brings 1000+ AI Agent Commands to HarmonyOS PC

DingTalk has released DingTalk Workspace CLI (DWS) for HarmonyOS PC and open-sourced its code. Features of the corporate messenger are now standardized command-line commands that can be called not only by a person but also by an AI agent. The scope is large: 25 business modules and more than 1000 commands. An agent gets access to group chats, meeting transcripts, tasks, AI tables, documents, the calendar, the address book and approvals, and no separate integration has to be written for each service. • The target platform is HarmonyOS PC, Huawei's desktop operating system • The repository is open, and third-party agents can connect to DWS • Use cases include the calendar, AI tables and approval workflows

AI-processed from Jiqizhixin (机器之心); edited by Hamidun News
DingTalk Open-Sources DWS and Brings 1000+ AI Agent Commands to HarmonyOS PC
Source: Jiqizhixin (机器之心). Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceJiqizhixin (机器之心) ↗
Editor-in-Chief
Key metric #1The target platform is HarmonyOS PC, Huawei's desktop operating system
Key metric #2The repository is open, and third-party agents can connect to DWS
Key metric #3Use cases include the calendar, AI tables and approval workflows

DingTalk Open Platform has released DingTalk Workspace CLI, or DWS for short, in a version for HarmonyOS PC, and open-sourced the project at the same time. DingTalk's entire product functionality is packaged into a standardized command-line interface: 25 business modules and more than 1000 commands. Through it, AI agents can carry out office operations, not just people working in a graphical interface.

The messenger as a set of commands

Classic enterprise software was built for a person with a mouse: buttons, forms, pop-up windows. None of that is convenient for an agent. Agents need clear calls with predictable input and output. A CLI offers exactly that format: a command, parameters, a result. Agents built on large language models use the command line well, because the training data contains a great deal of it.

DingTalk followed this path and broke its products down into commands. A developer's script, an automation or an autonomous agent can all call the same layer. The interface is shared, while permissions and scenarios are defined by whoever connects to it.

What exactly is available to the agent

The company lists the main office scenarios that DWS covers:

  • group chats — reading and sending messages in work groups;
  • meeting transcripts (会议听记) — access to the recording and text of past calls;
  • tasks (待办) — creating and tracking a to-do list;
  • AI tables — working with structured data in DingTalk tables;
  • documents — creating and editing work materials;
  • calendar — scheduling meetings and events;
  • address book — finding colleagues and contacts;
  • approvals (审批) — launching and processing corporate requests.

This is only part of the 25 modules, but it shows the logic. An agent can take a meeting transcript, pull out action items, create tasks, enter data in a table, schedule the next call in the calendar and send a summary to a chat. Previously, such a chain required several integrations. Now it is a sequence of commands in a single environment.

Why the HarmonyOS PC connection matters

HarmonyOS PC is Huawei's desktop operating system, and the ecosystem is actively filling it with applications. For a platform built from scratch, especially one created for the local market, the app catalog is not the only thing that matters. It also needs tools through which agents will work on it. DWS fills exactly that niche: DingTalk's office capabilities are available in the system in a machine-readable form.

For DingTalk, this is a way to claim a place in the new agent infrastructure on one more platform. If an agent can already work with corporate processes through DWS, it is easier for it to take root in a company. For owners of HarmonyOS PC devices, it is a ready-made set of actions that can be plugged into an assistant without building connectors themselves.

Open source and a bet on third-party agents

Opening the source code changes the role of the product. DWS becomes a common interface that developers of agent systems can embed in their own solutions, rather than a closed DingTalk feature. The code can be studied, adapted to your own needs, and checked to see what permissions an agent receives when it calls a given command. For corporate customers, that last point is often decisive: giving a model access to chats, documents and approvals is frightening without transparent boundaries.

That is why access control and action logging are critical in such projects. Approvals and contacts contain sensitive data, and an agent's mistake here costs more than an inaccurate answer in a chat.

Where developers and IT departments should start

A sensible start is a pilot on low-risk tasks: meeting transcripts, tasks and the calendar. The results are easy to check, and the cost of a mistake is small. Only after that does it make sense to connect documents, tables and approvals, with separate permissions for the agent rather than the account of a live employee.

Those building their own agents should look at the number of commands as a ready-made map of capabilities. More than 1000 calls let them avoid inventing an integration layer and focus on logic: what the agent should do, when, and with what confirmation from a human. Companies on HarmonyOS PC should assess which routine office chains they can assemble from DWS commands right now.

Story

Key Questions Answered

What are the key details on The messenger as a set of commands?

Classic enterprise software was built for a person with a mouse: buttons, forms, pop-up windows. None of that is convenient for an agent. Agents need clear calls with predictable input and output. A CLI offers exactly that format: a command, parameters, a result. Agents built on large language models use the command line well, because the training data contains a great deal of it. DingTalk followed this path and broke its products down into commands. A developer's script, an automation or an autonomous agent can all call the same layer. The interface is shared, while permis

What exactly is available to the agent?

The company lists the main office scenarios that DWS covers: group chats — reading and sending messages in work groups; meeting transcripts (会议听记) — access to the recording and text of past calls; tasks (待办) — creating and tracking a to-do list; AI tables — working with structured data in DingTalk tables; documents — creating and editing work materials; calendar — scheduling meetings and events; address book — finding colleagues and contacts; approvals (审批) — launching and processing corporate requests. This is only part of the 25 modules, but it shows the logic. An agent c

Why the HarmonyOS PC connection matters?

HarmonyOS PC is Huawei's desktop operating system, and the ecosystem is actively filling it with applications. For a platform built from scratch, especially one created for the local market, the app catalog is not the only thing that matters. It also needs tools through which agents will work on it. DWS fills exactly that niche: DingTalk's office capabilities are available in the system in a machine-readable form. For DingTalk, this is a way to claim a place in the new agent infrastructure on one more platform. If an agent can already work with corporate processes through D

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Autonomous AI Agents

Delegate Deep Research, Coding & Workflows to an AI Agent

Deploy autonomous multi-step execution with NomadNet Agent (agent.nomadnet.ai) — automated web research, data synthesis, code generation, and complex task orchestration.

Launch NomadNet Agent →NomadNet AI Platform
What do you think?
Loading comments…