Skip to main content
The /execute command lets you run a task directly from a YAML configuration file. Instead of entering parameters interactively, you define everything in a config file and execute it in one step. This is useful for reproducible experiments, batch processing, and reusing task configurations.

​
Usage

eigendata> /execute /path/to/config.yaml
Only .yaml and .yml files are supported. You must provide exactly one file path with no additional key=value arguments.

​
Configuration File Structure

The configuration file is a YAML mapping that must include a task field and any required parameters for that task.

​
Required Field

FieldDescription
taskThe task to execute. Supported values: data-generate, data-repair, data-audit, schema-polish, resample, schema-triggered-patch

​
Task-Specific Parameters

The remaining fields depend on the task type. Refer to each task’s documentation for required and optional parameters:

​
Example Configuration

Here is an example configuration file for a generate task: 
task: data-generate
domain: airline customer service
request: Generate multi-turn function-calling dialogs with multiple and diverse tool calls.
final_samples: 10
mcp_server_url: http://127.0.0.1:8009
data_language: English[100%]
reference_doc: ./inputs/domain_doc.md

​
Validation

Before executing, the CLI validates your configuration file:
  1. File format - Must be a valid .yaml or .yml file
  2. Required task field - The task field must be present and set to a supported task
  3. Unknown fields - Any field not recognized for the specified task causes an error
  4. Required parameters - All required parameters for the task must be provided
  5. Schema source exclusivity - If both schema_file and mcp_server_url are provided, the CLI reports a conflict

​
Validation Error Examples

Missing task field: 
Missing required field: task
Supported tasks: data-generate, data-repair, data-audit, schema-polish, resample, schema-triggered-patch
Unknown fields: 
Unknown fields in config for task 'generate':
  • unknown_param
Schema source conflict: 
Schema source fields are mutually exclusive:
  • schema_file or mcp_server_url

​
Confirmation Flow

After validation passes, the /execute command enters the same interactive confirmation flow as any other task. You can review the configuration, modify parameters, or confirm execution.