build-and-dependency
Skill1k starsChanged 20 days agoApache-2.0View on GitHub
Dev environment setup for NeMo AutoModel — container-based development, uv package management, installation options, environment variables, and common build pitfalls. Use when setting up a dev environment, adding or removing dependencies, switching container images, configuring environment variables, 'uv sync fails', 'ModuleNotFoundError', 'TransformerEngine version mismatch', stale .venv issues.
- Reads credentials
- Installs packages
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 109
Always use uv. Do not introduce pip install commands in scripts or docs.
- Distinctive: line 111
When upgrading dependencies, review compatibility backports and their version gates.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build and Dependency
Quick Start
Clone and install:
git clone https://github.com/NVIDIA-NeMo/Automodel.git && cd Automodel
uv sync --locked --all-groups --extra allOr use the NeMo-AutoModel 26.10 container from NVIDIA NGC:
docker pull nvcr.io/nvidia/nemo-automodel:26.10.00
docker run --gpus all -it nvcr.io/nvidia/nemo-automodel:26.10.00Installation Options
Option 1: NeMo-AutoModel Container (NGC)
The container ships with all dependencies pre-installed at /opt/Automodel
(WORKDIR) with the venv at /opt/venv. Run as-is:
docker run --gpus all --network=host -it --rm --shm-size=32g \
nvcr.io/nvidia/nemo-automodel:26.10.00 /bin/bashMounting your local checkout into the container
To develop against your host checkout, bind-mount it over /opt/Automodel to
override the installed source:
docker run --gpus all --network=host -it --rm --shm-size=32g \
-v <local-Automodel-path>:/opt/Automodel \
nvcr.io/nvidia/nemo-automodel:26.10.00 /bin/bashInside the container, patch pyproject.toml / uv.lock for the PyTorch base
image, then re-sync:
cd /opt/Automodel
bash docker/common/update_pyproject_pytorch.sh /opt/Automodel
uv sync --locked --all-groups --extra allWarning: the
update_pyproject_pytorch.shstep is required. Without it,uv syncwill try to reinstalltorch, which leads to CUDA version mismatches and TE import failures — uv cannot recognize the torch baked into the PyTorch base container.
Option 2: uv (Recommended for Local Development)
--all-groups pulls the build, docs, and test dev groups (defined in
pyproject.toml); drop it for a runtime-only install.
uv sync --locked --all-groups # base + dev groups
uv sync --locked --all-groups --extra cuda # CUDA support
uv sync --locked --all-groups --extra fa # flash-attention
uv sync --locked --all-groups --extra moe # mixture-of-experts
uv sync --locked --all-groups --extra vlm # vision-language models (core)
uv sync --locked --all-groups --extra vlm-media # + video/Qwen/Mistral decode (opencv, decord, qwen-utils; FFmpeg-bearing)
uv sync --locked --all-groups --extra diffusion # diffusion models
uv sync --locked --all-groups --extra diffusion-media # + diffusion preprocessing/export (imageio-ffmpeg, opencv)
uv sync --locked --all-groups --extra media # vlm-media + diffusion-media (union)
uv sync --locked --all-groups --extra delta-databricks # Delta Lake / Databricks
uv sync --locked --all-groups --extra msa # MiniMax M3 MSA sparse prefill (official MiniMax-AI/MSA with the model-private compatibility patch; Linux + SM100; run via `uv run` so torch finds `ninja`)
uv sync --locked --all-groups --extra all # all standard extras (EXCLUDES media — FFmpeg kept opt-in)The media extras (vlm-media, diffusion-media, media) bundle FFmpeg and are
deliberately excluded from all and from the container image — add them
explicitly for video/image decode.
Option 3: uv pip
Full install (matches uv sync --extra all):
uv venv
source .venv/bin/activate
uv pip install -e ".[all]"To add NeMo Run submission support to the base package:
uv venv
source .venv/bin/activate
uv pip install "nemo-automodel[cli]"The cli extra is additive: it adds nemo-run but does not remove the base
package's core training dependencies, including PyTorch.
Package Management
Always use uv. Do not introduce pip install commands in scripts or docs.
When upgrading dependencies, review compatibility backports and their version gates. Verify the candidate release contains the upstream fix before removing or bypassing a backport; never assume a future or patch release is fixed. If a backport remains necessary, validate it on the candidate release before extending its gate. Run the affected regression tests with the actual dependency and required backends; mocked version strings and skipped tests are not compatibility evidence. Record the release evidence and test results in the upgrade PR.
| Task | Command |
| Install from lockfile | uv sync --locked |
| Add a new dependency | uv add <package> |
| Add an optional dependency | uv add --optional --extra <group> <package> |
| Regenerate the lockfile | uv lock |
Environment Variables
export HF_TOKEN="hf_..." # Hugging Face token for gated models
export WANDB_API_KEY="..." # Weights & Biases logging
export HF_HOME="/path/to/hf_cache" # Hugging Face cache directoryCLI Usage
The entry point is automodel (defined at nemo_automodel.cli.app:main).
Pattern: uv run automodel <config.yaml> [--nproc-per-node N] [--key.subkey value ...]
# The YAML's recipe field selects LLM, VLM, diffusion, or retrieval behavior.
uv run automodel examples/llm_finetune/llama3_2/llama3_2_1b_squad.yaml --nproc-per-node 8Override any config value from the CLI:
uv run automodel examples/llm_finetune/llama3_2/llama3_2_1b_squad.yaml \
--model.pretrained_model_name_or_path meta-llama/Llama-3.2-1BCommon Pitfalls
| Problem | Cause | Fix |
Stale .venv after switching branches | Cached environment out of sync | Delete .venv and re-run uv sync --locked |
| Import errors for optional features (TE, flash-attn, MoE) | Missing extras | Install the matching uv extra (--extra fa, --extra moe, etc.) |
Import errors for media (cv2, decord, qwen_vl_utils, imageio_ffmpeg) | Media extras are opt-in (not in all) | Install --extra vlm-media (VLM/Qwen/Mistral) or --extra diffusion-media (diffusion) |
| TransformerEngine version mismatch | The TE installed by uv sync takes precedence over the version baked into the container | Set the desired TE version in pyproject.toml / uv.lock and re-run uv sync — the venv's TE wins, not the container's |
Trending
More talk lately.about the whole repository
Who's talking about NVIDIA-NeMo/Automodel
- NVIDIA/Megatron-LM“DeepSeek-V4 training support”GitHub · Apr 24, 2026 · 27 reactions
- THUDM/slime“[Roadmap][Megatron, VLM] Support VLM”GitHub · Dec 12, 2025 · 6 reactions
- NVIDIA-NeMo/RL“Automodel bump up + Refactor to use the generic CP interface to be provided by Automodel”GitHub · Jul 23, 2026 · 1 reactions
- NVIDIA-NeMo/Megatron-Bridge“[model] Add verified Nemotron 3 Nano 4B CPT support”GitHub · Jul 20, 2026 · 1 reactions
- NVIDIA-NeMo/RL“chore: major version bump (torch 2.8, vllm 0.11, ray 2.49) & SP fixes”GitHub · Oct 10, 2025 · 1 reactions
The biggest 5 of 43 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 43
Talked about on GitHub (43 times).
On GitHub · 43
- Apr 24, 2026DeepSeek-V4 training support — NVIDIA/Megatron-LM27 reactions · 5 comments
- Dec 12, 2025[Roadmap][Megatron, VLM] Support VLM — THUDM/slime6 reactions · 2 comments
- Jul 23, 2026Automodel bump up + Refactor to use the generic CP interface to be provided by Automodel — NVIDIA-NeMo/RL1 reaction · 1 comment
- Jul 20, 2026[model] Add verified Nemotron 3 Nano 4B CPT support — NVIDIA-NeMo/Megatron-Bridge1 reaction · 1 comment
- Oct 10, 2025chore: major version bump (torch 2.8, vllm 0.11, ray 2.49) & SP fixes — NVIDIA-NeMo/RL1 reaction · 41 comments
38 more on GitHub
- Oct 16, 2026fix(automodel): release MoE dispatcher state before colocated offload — NVIDIA-NeMo/RL0 reactions · 4 comments
- Oct 15, 2026feat(speechlm): add native Automodel GSPO ASR recipe — NVIDIA-NeMo/RL0 reactions · 13 comments
- Oct 15, 2026feat(speechlm): support native RL checkpoints and frozen CTC export — NVIDIA-NeMo/Speech0 reactions · 20 comments
- Oct 15, 2026feat(audio): align ASR scoring and support explicit Ray launches — NVIDIA-NeMo/Skills0 reactions · 1 comment
- Oct 14, 2026fix(cutedsl): support CUTLASS DSL 4.4.2 and 4.6.2 — SandAI-org/MagiAttention0 reactions · 2 comments
- Oct 13, 2026An old, unused torchao install makes every LoRA/OFT injection fail with ImportError (e.g. on Colab and Kaggle) — huggingface/peft0 reactions · 6 comments
- Sep 28, 2026fix(build): use C++20 for PyTorch extensions — SandAI-org/MagiAttention0 reactions · 3 comments
- Sep 28, 2026Fix SpeechLM Automodel precision and vLLM audio handling — NVIDIA-NeMo/Speech0 reactions · 8 comments
- Sep 23, 2026chore(customizer): add magi_attention dependency in automodel — NVIDIA-NeMo/nemo-helix0 reactions · 2 comments
- Sep 16, 2026docs: reference NeMo AutoModel and bring the recipe notes up to date — mraad/feln-lora0 reactions · 5 comments
- Sep 16, 2026fix(customizer): install seed deps in grpo env + dtensor v2 ckpt crash — NVIDIA-NeMo/nemo-helix0 reactions · 2 comments
- Sep 16, 2026feat(speechlm2): add DFlash and DFlash2 training for SALM — NVIDIA-NeMo/Speech0 reactions · 9 comments
- Sep 9, 2026build(deps-dev): bump nvidia-modelopt from 0.44.0 to 0.46.0 — HuipengHuang/verl-baseline0 reactions
- Sep 1, 2026[Feature Request] Add text-only GRPO support for Qwen3.8-Flash-Next (qwen4_exp) — verl-project/verl0 reactions
- Aug 4, 2026Add training submodules for RunPod environment — witchking999/muramasaIII0 reactions
- Aug 1, 2026[feature] Support DSpark speculative decoding draft training — NVIDIA-NeMo/Megatron-Bridge0 reactions · 5 comments
- Jul 31, 2026[feature] DeepSeekV4 + FP8 RL — NVIDIA-NeMo/labs-molt0 reactions
- Jul 30, 2026Integrate NeMo Automodel Qwen3.5-35B-A3B recipe with MFSDP v2 — NVIDIA/Megatron-LM0 reactions
- Jul 17, 2026cuDNN fused-MHA SDPA backend intermittently fails with "mha_graph.execute(...).is_good() == false" during Qwen3-VL image+text inference on H200 / cuDNN 9.20 — pytorch/pytorch0 reactions · 5 comments
- Jul 16, 2026[DSpark] Add dspark dense draft model — sgl-project/sglang0 reactions · 2 comments
- Jun 11, 2026feat(speechlm2): add Multi-Token Prediction (MTP) training support to SALMAutomodel — NVIDIA-NeMo/Speech0 reactions · 2 comments
- May 14, 2026CUDA codegen LogFatals on `boolx8` from sparse-MLA bwd kernel on B300/sm_103 (TileLang 0.1.9) — tile-ai/tilelang0 reactions · 1 comment
- May 10, 2026fix(automodel): support combined projection tensor sync — NVIDIA-NeMo/RL0 reactions · 1 comment
- Apr 24, 2026Track DeepSeek V4 upstream dependency blockers — zpqiu/RL0 reactions · 3 comments
- Apr 24, 2026Support DSV4 Flash — NVIDIA-NeMo/RL0 reactions · 1 comment
- Apr 23, 2026Qwen3.5 Automodel path is slower than MCore because flash-linear-attention (FLA) is not installed by default — NVIDIA-NeMo/RL0 reactions · 5 comments
- Apr 23, 2026Qwen3.5 MoE Automodel path does not use FP32 master weights by default, causing slower convergence — NVIDIA-NeMo/RL0 reactions
- Apr 20, 2026fix(pre-commit): preserve matched filenames in `no-underscore-md` hook — NVIDIA-NeMo/FW-CI-templates0 reactions
- Apr 17, 2026Track Qwen3.5-related issues — NVIDIA-NeMo/RL0 reactions
- Feb 10, 2026Support transformers v5 — ByteDance-Seed/VeOmni0 reactions · 1 comment
- Jan 11, 2026feat: Add NVIDIA Embed Nemotron embedding model support — paiml/trueno-rag0 reactions · 1 comment
- Dec 25, 2025ImportError: cannot import name 'TransformersKwargs' from 'transformers.utils' — iqiancheng/llms-cookbook0 reactions · 1 comment
- Dec 25, 2025ImportError: /opt/hpcx/ucc/lib/libucc.so.1: undefined symbol: ucs_config_doc_nop — iqiancheng/llms-cookbook0 reactions · 1 comment
- Nov 12, 2025layer-by-layer comparison tool between policy/generation — NVIDIA-NeMo/RL0 reactions
- Sep 25, 2025Use scale and clip grads utilties from Automodel for DTensor v2 — NVIDIA-NeMo/RL0 reactions
- Sep 8, 2025gemma 27b slow on v2 — NVIDIA-NeMo/RL0 reactions · 1 comment
- Sep 5, 2025Gemma3 27B crashes on 8 nodes with Sequence Parallel — NVIDIA-NeMo/RL0 reactions
- Sep 5, 2025Gemma3 27B crashes on 16 nodes w/ FSDP — NVIDIA-NeMo/RL0 reactions · 1 comment
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- NVIDIA-NeMo/RL★ 2.1ksame name
- NVIDIA-NeMo/Megatron-Bridge★ 960same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cicdSkill
- fern-docsSkill
- linting-and-formattingSkill
- parity-testingSkill
- testingSkill
- nemo-automodel-distributed-trainingSkill
- nemo-automodel-launcher-configSkill
- nemo-automodel-model-onboardingSkill
- nemo-automodel-recipe-developmentSkill
- pr-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

