Presets
These commands require the separately installed experimental CLI.
Experiment With Presets
Presets are complete, embedded FabricConfig values intended for quick
experiments:
The scripted preset does not call a model. It returns a deterministic response
through the same NeMo Fabric runtime and adapter contract, which makes it useful for
checking CLI installation, request flow, and result formatting without network
access or credentials.
The four external-harness presets use NVIDIA_API_KEY. Hermes Agent and Deep Agents
target the public NVIDIA API Catalog at https://integrate.api.nvidia.com/v1.
Export the credential before running them:
Claude and Codex require the base URL for an NVIDIA endpoint that serves the selected frontier model and supports the harness protocol. Set it explicitly:
NeMo Fabric does not provide a default frontier URL because the correct endpoint depends on the model and the user’s access.
List the complete configurations maintained by the CLI:
Inspect a preset’s purpose and required environment variables:
Resolve the preset to inspect its complete run plan, including its typed configuration and adapter descriptor:
To display only the authored FabricConfig, filter the plan with jq:
Diagnose adapter availability, credentials, and other requirements before running the preset:
Run the preset with an input:
Override the preset’s default model and temperature for a quick experiment:
These flags preserve the preset’s provider, credential environment variable,
endpoint, and harness settings. Use a model that is available from the preset’s
provider and compatible with the selected harness. For example, a Claude preset
still requires an Anthropic Messages-compatible model, while a Codex preset
requires a Responses-compatible model. The plan and doctor commands accept
the same overrides.