DataWorks Agent lets you complete complex data integration, development, and governance tasks by describing what you need in plain language. Powered by a large language model (LLM), it breaks down your request, plans the execution, and delivers results end-to-end — no manual step-by-step configuration required.
Unlike the DataWorks Agent with third-party clients, DataWorks Agent is built into DataWorks. No additional software or setup is needed.
How it works
DataWorks Agent operates inside Copilot Chat in Data Studio. Open the agent, pick the agent type that matches your task (or let DataWorks pick it automatically), describe what you need, and the agent handles the rest.
Context-aware activation: In each DataWorks module, the agent automatically activates the capabilities relevant to your current task. When you're in Data Integration, the Data Integration Agent is selected automatically. You don't need to choose manually unless you want to switch.
For complex tasks, the agent:
Breaks the work into a To-do list and shows real-time status as each step completes.
Compiles an execution summary at the end, listing all completed operations and generated resources.
Reports task duration and token consumption so you can assess efficiency.
Intelligent model scheduling: By default, DataWorks Agent uses the DataWorks default model, which automatically dispatches the best-fit model for each sub-task and switches between models within a single conversation. To use a specific model instead, select it from the model menu at the bottom of the dialog box.
Access the agent
Log on to the DataWorks console. In the left-side navigation pane, choose Data Development and O&M > DataStudio. Select your workspace and open Data Studio.
Click the
icon in the upper-right corner of the Data Studio page to open Copilot Chat. Ask mode is enabled by default. In the lower-left corner of the dialog box, switch to Agent mode.
Quick start
Step 1: Switch to Agent mode
Click the
icon in the upper-right corner of Data Studio to open Copilot Chat, then switch to Agent mode in the lower-left corner.
Step 2: Select an agent
Enter / in the input box to open the agent menu and select the agent that matches your task:
| Agent | Best for |
|---|---|
| Data Integration Agent | Describing sync tasks in natural language |
| Data Studio Agent | ETL development, code generation, and workflow setup |
| Data Governance Agent | Configuring quality rules and resolving governance issues |
| Data Map Agent | Searching and exploring metadata |
| Data O&M Agent | Diagnosing task instance health issues |
In each DataWorks product module, the agent is selected automatically based on your current context.

Step 3: Add context (optional)
Enter @ in the dialog box or click @ in the lower-right corner to attach context. Adding context helps the agent understand your data model and produce more accurate results.

| Context type | What it provides |
|---|---|
| Table | Metadata from one or more tables |
| Node/Code Files | Code from a specific node |
| Data Album | A data album from Data Map |
| Rules | One or more governance rules applied to the current conversation |
| Upload File | A local document |
Step 4: Switch the LLM (optional)
By default, Copilot uses the DataWorks default model, which intelligently allocates models based on task requirements. To use a different model, click the
icon at the bottom of the dialog box and select a model.

| Model | Supported regions |
|---|---|
| DataWorks default model | China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo) |
| Qwen3-Coder | China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo) |
| Qwen3-Max | China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Chengdu) |
| GLM4.7 | China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Chengdu) |
Step 5: Refine with multi-turn conversation
Enter your request in the dialog box. Ask follow-up questions or provide more details to refine the result across multiple turns until the agent produces what you need.
Use cases
Data Integration Agent
Describe a data synchronization requirement in natural language (Chinese or English). The agent parses your intent and automatically generates the full task configuration — source and target data source types, table structure mappings, column filtering conditions, partitioning strategies, and scheduling parameters.
What the agent does:
Parses your description to extract sync requirements and populate source, target, and mapping configuration automatically.
Creates a data synchronization node that you can review and modify before saving.
Steps:
Enter
/and select Data Integration Agent.Describe your sync requirements, including source, target, table names, and sync method.
The agent creates a data synchronization node. Click the node to view or modify the configuration.
Example prompt:
Create an offline synchronization task to sync the ods_user_info_d table from MySQL to the ods_user_info_d table in MaxCompute.Data Studio Agent
Build ETL workflows through natural language. The agent covers the full development cycle: requirements analysis, code generation, dependency configuration, and release.
What the agent does:
Breaks the task into sub-steps (create nodes, generate code, configure dependencies) and shows a To-do list with real-time status.
Generates node code that you can review, keep, or discard before it's applied.
Compiles an execution summary when the workflow is complete.
Steps:
Describe your data development requirement in natural language and attach context with
@as needed.The agent breaks the task into steps and executes them. Review generated code at each step.
Choose to keep or discard each change before the agent moves to the next step.
Example prompt:
Build a user profile analysis workflow.Storage management: The agent creates nodes and files in project or personal directories. To set the default path, configure The default storage path for generating code files in the Copilot settings center. For details, see Personal settings. If the node type conflicts with the target directory rules (for example, creating a data integration node in a personal directory), the agent prompts for confirmation before proceeding.
Data Governance Agent
Manage data governance through natural language commands instead of manual form-based configuration. The agent analyzes your data, recommends actions, and executes governance operations automatically.
What the agent does:
Quality rule configuration: Analyzes column types, business semantics, and table importance to recommend and configure monitoring rules — including primary key uniqueness, non-null constraints, and enumeration range checks.
Quality issue resolution: Identifies governance issues (such as frequently accessed tables without quality rules) and performs remediation automatically.
Steps:
Enter
/and select Data Governance Agent.Describe your governance requirement. The agent analyzes the relevant tables and proposes an action plan.
Confirm the plan. The agent configures and executes the governance operations.
Example prompts:
Automatically generate quality rules for the core user dimension table dim_user_info.
Configure quality rules related to table row counts for all tables starting with ods_.
Find frequently accessed tables that don't have quality rules, then recommend and configure rules for them.
Help me resolve all open issues in the data quality dimension.Data Map Agent
Search and explore metadata across your data assets using natural language — no precise keywords needed.
What the agent does:
Natural language search: Finds tables based on your business intent rather than exact names.
Scope-aware filtering: Understands when you specify a project or domain and narrows results accordingly.
Deep data exploration: Answers follow-up questions about data lineage, ownership, and column definitions for a specific table.
Example prompts:
Find summary tables related to user activity.
In the adm_bi project, find tables related to business operations.
@dws_bi_metric_di What are the direct downstream dependencies of this table? Who are the owners that would be affected by changes?Data O&M Agent
Get a comprehensive health assessment and root-cause diagnosis for task instances. The agent integrates analysis across dependency chains, resource levels, historical run trends, change impacts, log anomalies, and data quality — then outputs a structured diagnostic report.
For details, see AI-powered O&M.
What's next
To use DataWorks Agent with your own tools and workflows, see DataWorks Agent with third-party clients.