Run configuration and presets
Per-node arguments for a run, saved as named presets you can duplicate, export, and seed from the last run.
The Run cfg panel collects the values a run needs without changing the graph: the graph input, per-node arguments, and the level to run or validate at. Each graph keeps its own named presets in your browser, seeded with a Default preset the first time you open it.
Working with presets
- New, Duplicate, and Rename live in the panel header.
- Export and Import move a preset as a versioned JSON bundle — the way to hand a configuration to a teammate.
- "Use last run values" merges the previous successful run's values into the active preset.
Which fields appear
Run cfg and the inspector share one catalog of node fields. The inspector hides run-only fields (secrets are run-only by default); the Run panel shows them with a "Per run" badge. A node's Run panel fields are chosen by the checkbox allow-list in its inspector.
Related
- Configure a node in the inspectorGraph editorThe inspector holds a selected node's identity, configuration, connection and authorization settings, and its run defaults.
- Reference secrets instead of inlining themCredentials & modelsenv: and ${ENV:VAR} references resolve at run time, so no key is ever written into a graph or preset.
- Validate a graph and fix problemsGraph editorWhere validation errors come from, where they surface, and why Run can be disabled.
- Run a graphRunning & debuggingSupply the input, clear validation, start the run, and find it afterwards.
More in Running & debugging · Search all help