NeMo Data DesignerThe Data Designer CLI provides an interactive interface for creating and managing default model providers and model configurations stored in your Data Designer home directory (default: ~/.data-designer/).
The CLI manages two YAML configuration files:
model_providers.yaml: Model provider configurationsmodel_configs.yaml: Model configurationsAutomatic Configuration If these configuration files don’t already exist, the Data Designer library automatically creates them with default settings at runtime when first initialized.
Custom Directory
You can customize the configuration directory location with the DATA_DESIGNER_HOME environment variable:
The Data Designer CLI provides four main configuration commands:
Getting help See available commands
See available sub-commands
Run the interactive provider configuration command:
Add a new provider: Define a new provider by entering its name, endpoint URL, provider type, and optionally an API key (as plain text or as an environment variable name).
Update an existing provider: Modify an existing provider’s settings. All fields are pre-filled with current values.
Delete a provider: Remove a provider and its associated models.
Delete all providers: Remove all providers and their associated models.
Change default provider: Set which provider is used by default. This option is only available when multiple providers are configured.
The “Change default provider” workflow is deprecated and will be removed in a future release alongside the registry-level default. Specify provider= explicitly on each ModelConfig instead — the workflow now emits a DeprecationWarning when entered. See issue #589.
Run the interactive model configuration command:
Provider Required
You need at least one provider configured before adding models. Run data-designer config providers first if none exist.
Add a new model configuration
Create a new model configuration with the following fields:
nvidia/nemotron-3-nano-30b-a3b)Additional Settings
To configure additional inference parameter settings or use distribution-based inference parameters, edit the model_configs.yaml file directly.
Update an existing model configuration: Modify an existing model’s configuration. All fields are pre-filled with current values.
Delete a model configuration: Remove a single model configuration.
Delete all model configurations: Remove all model configurations. The CLI will ask for confirmation before proceeding.
View all current configurations:
This command displays:
Delete all configuration files:
The CLI will show which configuration files exist and ask for confirmation before deleting them.
Destructive Operation This command permanently deletes all configuration files and resets to the default model providers and configurations. You’ll need to reconfigure your custom configurations from scratch.
ModelProvider class and provider configurationModelConfig