Accelerate Configuration and CLI
Use this sub-skill to create, validate, update, and reason about Accelerate config files and command-line invocations.
When to Use
- Build or debug
accelerate launchcommands for scripts, modules, non-Python executables, multi-node jobs, or SLURM wrappers. - Create or adapt
default_config.yamlor custom--config_fileYAML for local CPU, single accelerator, multi-GPU, multi-XPU, or multi-node runs. - Explain or safely run
accelerate config,config default,config update,env,test,estimate-memory,merge-weights, orto-fsdp2. - Diagnose missing configs, invalid YAML, unknown keys, conflicting launcher flags, rendezvous mistakes, subprocess tracebacks, and training-script argument separation.
Routing Boundaries
- For training-loop code changes such as
Accelerator.prepare, dataloaders, gradient accumulation, trackers, and checkpoint hooks, use../training-loop-integration/. - For DeepSpeed, FSDP, Megatron-LM, TPU, and backend-specific semantics beyond CLI flag placement, use
../distributed-training-backends/. - For
estimate-memoryinterpretation and big-model device-map loading workflows, use../big-model-inference/.
Start Here
- Read
references/cli-reference.mdfor command inventory, safe command patterns, and which commands mutate files. - Read
references/configuration.mdbefore editing YAML or choosing top-level config keys. - Read
references/launching.mdbefore composingaccelerate launch, multi-node, module, no-Python, or SLURM commands. - Read
references/troubleshooting.mdwhen a config or launch command fails.
Bundled Helpers
scripts/validate_accelerate_config.py: validates YAML syntax, known top-level keys, required fields, and common local/multi-node conflicts without importing Accelerate.scripts/print_accelerate_help_summary.py: invokes installedaccelerate --helpsubcommands when available and prints a compact availability summary.
Run helpers with python path/to/script.py --help for usage.


