Why Long-Running Agents Need a New Kind of Model
Autonomous AI agents are no longer just prototypes. They're running around the clock, handling thousands of tool calls, validating outputs, and delegating subtasks. But here's the problem: using a massive frontier reasoning model for every single step is like using a freight train to deliver a pizza. It's expensive, slow, and overkill.
That's where NVIDIA Nemotron 3.5 Lightning comes in. This open 30B mixture-of-experts (MoE) model with only 3B active parameters is specifically designed for the execution layer of always-on agents. It's the workhorse that handles the high-volume, low-latency tasks that keep agents running efficiently.
Think of it as the difference between a strategist and a soldier. The strategist (frontier model) plans the mission, but the soldier (Lightning) executes it. And with model routing becoming more accessible, you can now have both working in harmony.

Under the Hood: Speed and Accuracy Without Compromise
Nemotron 3.5 Lightning achieves its impressive performance through two key innovations:
1. Speculative Decoding
Traditional models generate one token at a time, which is slow. Lightning uses multi-token prediction (MTP) to draft multiple tokens at once, which are then verified in parallel. This drastically speeds up inference.
# Example: Using speculative decoding with a draft model
from transformers import AutoModelForCausalLM, AutoTokenizer
# Load the main model and the draft model (DSpark or DFlash)
model = AutoModelForCausalLM.from_pretrained("nvidia/Nemotron-3.5-Lightning")
draft_model = AutoModelForCausalLM.from_pretrained("nvidia/Nemotron-DSpark")
# Generate with speculative decoding (pseudo-code)
output = model.generate_with_draft(
draft_model=draft_model,
prompt="Call the weather API for Tokyo",
max_new_tokens=128,
num_draft_tokens=5 # Number of tokens to draft
)
print(output)
2. Quantization (NVFP4)
Lightning ships with an NVFP4 checkpoint alongside BF16, allowing it to run efficiently on consumer GPUs like the RTX 5090 and DGX Spark without sacrificing accuracy.

Model Routing: The Secret to Cost Efficiency
One of the most exciting parts of this release is NVIDIA NeMo Switchyard. This library intelligently routes each request to the best model for the job. High-level planning goes to a frontier model like Nemotron 3 Ultra, while routine execution tasks (like git pull, formatting, validation) go to Lightning. This ensures your token budget is spent wisely.
Accuracy vs. Speed Pareto Frontier
| Model | Output Speed | Accuracy (AAII) | Best For |
|---|---|---|---|
| Nemotron 3 Ultra | Low | 92 | Complex planning |
| Nemotron 3.5 Lightning | 4x faster | 88 | High-volume execution |
| Qwen3.6 35B | 1x | 86 | General tasks |
Caveats and Considerations
- Not a replacement for frontier models: Lightning is optimized for execution, not deep reasoning. Don't expect it to solve novel research problems.
- Draft model selection: DSpark vs. DFlash performance varies with concurrency. Test both to find the best fit.
- Ecosystem maturity: While the partner list is impressive, some integrations are new and may have rough edges.

Conclusion: Start Building with Lightning
Nemotron 3.5 Lightning is a game-changer for developers building scalable AI agents. It's open, customizable, and deployable anywhere from a DGX Spark to a data center. If you're serious about agent efficiency, this is the model to try.
Next Steps:
- Try it on build.nvidia.com or OpenRouter.
- Download weights from Hugging Face.
- Set up routing with NeMo Switchyard.
For more on production AI coding, check out Beyond Prototypes: How Vercel's New v0 Brings AI Coding to Production. And if you're curious about CSS pseudo-elements, don't miss Styling Highlight Pseudo-Elements: A Deep Dive.
Keep building, and let your agents run smarter.