01
Overview
ZCode 3.14 introduces Dynamic Workflows, a new way to coordinate multiple sub-agents around a complex task. According to Z.ai's September 19, 2026 changelog, one workflow script can orchestrate several sub-agents and users can start a workflow from the plus menu in the input box or with the /workflow command. The same release also adds separate Office and Coding modes.
02
What changed in ZCode 3.14
The important change is orchestration. Earlier ZCode capabilities already covered long-running agent tasks, scheduled automation, browser control and remote interaction. Dynamic Workflows adds an explicit multi-agent coordination layer: a script can define work that multiple sub-agents collaborate on instead of treating the entire job as one continuous agent thread.
Z.ai's public changelog confirms the feature but the currently indexed documentation does not yet publish a complete Dynamic Workflows scripting reference. That means exact workflow DSL syntax, every supported primitive, limits and plan gating should not be inferred from the short release note.
03
How to start a Dynamic Workflow
Z.ai documents two launch surfaces in the 3.14 changelog: the plus menu in the input box and the /workflow command. The release note says these start a workflow, but does not currently provide a complete public click-by-click or scripting tutorial. Treat any more detailed syntax from community examples as community material until it appears in first-party documentation.
04
Dynamic Workflows vs Goal mode
Goal mode is ZCode's existing long-running single-objective execution mode. The official Goal documentation says /goal sets an objective and ZCode keeps iterating until the goal is met, automatically starting another round when necessary. Dynamic Workflows solves a different problem: coordinating multiple sub-agents around complex work. A practical mental model is Goal mode for persistent pursuit of one objective and Dynamic Workflows for explicit multi-agent orchestration. Z.ai has not stated that one universally replaces the other.
05
Dynamic Workflows vs ZCode Automations
ZCode Automations are trigger and cadence mechanisms. The official documentation describes scheduled tasks that run at a chosen time/repeat rule and idle-time tasks that can run when spare capacity is available. Dynamic Workflows describes how multiple sub-agents collaborate inside a workflow. These concepts can be complementary, but do not assume a scheduled task can invoke every Dynamic Workflow pattern until Z.ai documents that integration explicitly.
06
Office and Coding modes
Version 3.14 also adds switching between Office and Coding modes. ZCode's broader product positioning remains development-focused, while the new mode switch suggests a wider work surface. The changelog does not yet provide enough detail to claim different model entitlements, tool permissions or workflow syntax for each mode.
07
Other capabilities around the workflow
ZCode's documented environment includes Goal mode for long-horizon work, scheduled and idle-time automations, a browser panel the agent can operate, remote control from a phone, bot channels, file and terminal context, and model connections through Z.ai/BigModel plans or API keys. These are separate documented capabilities and should not all be described as features of Dynamic Workflows itself.
08
Models and plans
ZCode supports GLM models through Z.ai and BigModel connections and can also be configured with model-service access. Z.ai's current global page lists GLM Coding Lite, Pro and Max tiers, while its FAQ says the ZCode application itself is free and model/API access is still required. Pricing and quota details can change, so they should be rechecked immediately before publication rather than hard-coded as permanent facts.
09
Platform availability
ZCode provides desktop installers for macOS, Windows and Linux. The 3.14 changelog establishes the Dynamic Workflows release, but the current public documentation does not explicitly document feature parity for Dynamic Workflows on every OS. Avoid claiming identical behavior across platforms until verified.
Likely uses
Multi-agent workflow orchestration is most useful when a task can be decomposed into specialist roles or parallel subtasks: repository research plus implementation plus verification; migration planning plus code changes plus tests; or multi-part analysis where separate agents can investigate independent components. These are inferred use patterns based on the feature's documented multi-sub-agent design, not official guarantees about a specific workflow template.
10
Limitations to know
The biggest current limitation is documentation depth. Z.ai confirms the feature and launch mechanisms but has not yet exposed a complete indexed Dynamic Workflows scripting reference. Do not invent commands, schemas, concurrency limits, supported sub-agent counts or plan requirements. ZCode 3.14.1, released September 21, is a bug-fix release and does not materially change the Dynamic Workflows announcement.
FAQ
What are ZCode Dynamic Workflows? Z.ai describes them as workflows where one script orchestrates multiple sub-agents collaborating on complex tasks.
Which ZCode version added Dynamic Workflows? ZCode 3.14.0, released September 19, 2026.
How do I launch a workflow? Z.ai says from the input-box plus menu or with /workflow.
Is ZCode free? Z.ai's FAQ says the ZCode application is free, while model usage requires an API key or model service plan.
Are Dynamic Workflows the same as scheduled tasks? No. Scheduled tasks define when work runs; Dynamic Workflows describe multi-agent orchestration. First-party docs do not yet establish every possible integration between the two.
Does ZCode support Windows and Linux? Yes, ZCode has installers for macOS, Windows and Linux. Dynamic Workflow feature parity should still be reverified before publication.
Sources: ZCode official changelog and documentation for Automations, Goal mode, Browser Automation, model configuration and the ZCode product page.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.