What happened
DingTalk-Real-AI released stable version 1.0.66 of the DingTalk Workspace CLI, or dws, on GitHub on 28 October 2026. The release promotes the previously delivered v1.0.66-beta.2 work into a formal release, incorporates improvements from both betas, and adds changes made after beta.2. The release notes describe dws as a command-line surface with schemas, Help, Skills, structured agent output, and MCP-facing operations across DingTalk workspace products.
The most consequential addition is third-party OIDC login. The release notes list provider hooks, staged token exchange, and credential refresh isolation by application and source. Login failures preserve public error codes and a Trace ID, while filtering credentials and internal diagnostic details. The core provides the hook; real SDK adapters are expected to be connected through overlays. That distinction matters: the release establishes an integration mechanism, but does not claim that every identity provider already has a ready adapter.
Version 1.0.66 also expands operational controls for AI Table and forms. AI Table gains commands to append or replace role members, copy roles, and query effective user-role assignments with validated member payloads and unified agent output. Its orchestration features include bounded batch reads, plans, chart templates and layout diagnostics, resumable waits for AI tasks, reports, AI-field configuration, and field-group operations. Form-sharing operations now validate returned permissions, anonymity, viewing scope, notifications, timing, and cover configuration against MCP readback. When returned values conflict, or the service cannot provide enough evidence, dws reports a partial failure or an explicitly unverified result rather than treating the operation as complete.
The release adds dws mcp market search, which searches DingTalk's published MCP marketplace by name keyword. Results include an MCP ID, name, description, service name, provider, official status, and whether the service is paid. The output can feed the existing published-tools and URL lookup commands. Search supports a per-page --limit and cursor continuation, but only covers marketplace-listed MCPs; enterprise-published MCPs that are not listed are excluded. Other additions include independent mind-map creation and topic management, group-join workflows with pending states, and application-scope get/set commands that preserve failed, pending, and unknown outcomes.
The release also makes certain risk boundaries more explicit. Calendar-event deletion, attendee deletion, room deletion, group-member removal, minutes text replacement, and document-permission updates now require explicit confirmation. Non-interactive scripts must pass --yes only after user approval; otherwise they receive confirmation_required and no remote call is made. Finally, the release contains a breaking input change for a digital-employee type: scripts using open_code must switch to qwenwork. The notes caution that users must separately verify public-service and older-client compatibility; a passing CI run does not establish server-side compatibility.
What the archive adds
This is a new release event, but it belongs beside Univer Workspace, which framed an office workspace as a shared change surface for people and AI agents. Dws approaches that shared surface from the command line: it exposes discrete workspace operations, their schemas, and their result states rather than presenting a conventional editor with an assistant.
Trend signal
The release supports Agent-ready software exposes capabilities. Its meaningful unit is not a generic chat assistant but permissioned operations: query roles, update sharing, search published MCP services, inspect application scope, or request a destructive mutation with explicit approval. The repeated use of readback, partial-failure states, and recovery facts also shows why an agent-facing capability needs observable outcomes, not merely a callable endpoint.
Connections to other events
The archive's Univer Workspace note describes another workspace product positioning people and agents around a common work surface. Dws adds a different implementation direction: command, schema, and MCP interfaces that can let an external agent operate parts of that surface under explicit constraints.
Why it matters
Teams building workplace agents often hit the hard part after they can generate text: safely acting on shared resources whose permissions, lifecycle state, and service responses may be ambiguous. This release is notable because it treats those ambiguities as product-level output. A form update can remain unverified; contradictory state becomes a partial failure; unavailable capability does not justify a write probe or blind replay; destructive actions stop before the remote service without confirmation.
That does not make dws a universal integration layer. It does offer a useful design reference for builders connecting agents to enterprise systems: expose operations in small units, document their schemas, distinguish success from evidence of success, and make approval requirements machine-visible. The MCP-market search function adds a discovery layer, while its stated exclusion of unlisted enterprise services makes the coverage boundary legible.
What happens next
- Dws is likely to add or document more concrete identity-provider adapters around its OIDC hook model (6 months, 60%). Watch for: named SDK adapters or provider-specific setup instructions.
- More workspace mutations will likely gain explicit verification and recovery semantics (6 months, 70%). Watch for: additional commands reporting partial, pending, or unverified terminal states.
Limits and uncertainty
The release notes are a project account of changes, not an independent test of the CLI, its service compatibility, or its operational reliability. They explicitly say that public-service compatibility for the renamed digital-employee type requires separate verification, and that CI success does not prove server compatibility. The notes describe an OIDC hook and token-flow features but do not enumerate production-ready third-party provider adapters. MCP-market search is limited to listed services, so it should not be read as a complete inventory of enterprise MCP deployments. The release also mentions OpenHarmony archive synchronization, but does not establish broad production support for that platform.
Skill to build now
Audit one agent-facing write operation in your own product this week. Define its required approval state, the exact evidence that confirms the remote system applied it, and the output for pending, contradictory, or unverifiable results. Then ensure an automated retry cannot replay a mutation when the first attempt's final state is unknown. This is more actionable than adding another natural-language instruction: it gives the harness a bounded contract around a real capability.
Reader takeaway
Dws v1.0.66 is not important because it adds one more workplace CLI command. Its stronger signal is the operating model behind the release: agent-accessible workspace functions should expose permissions, confirmation gates, verification evidence, and incomplete outcomes as first-class interface states.
Open question
Will the OIDC hook system acquire broadly usable provider adapters, and will its verification-oriented command model remain consistent as more DingTalk services are exposed?