NeMo Agent Toolkit end of life
NVIDIA NeMo Agent Toolkit end of life: the date and what to do before it
NVIDIA deprecated the NeMo Agent Toolkit as of October 2026 and says it will reach end of life by the end of 2026. After that date you should not expect fixes, including security fixes. The library is open source, so what you run today keeps running, but new work should move to the three replacements: NeMo Relay, NeMo Fabric and NeMo Helix.
The dates
| When | What |
|---|---|
| October 2026 | NVIDIA marks the NeMo Agent Toolkit as deprecated |
| End of 2026 | End of life. NVIDIA asks users to finish migrating before this |
| November 2026 | The three replacements are all before version 1.0 |
What keeps working and what stops
- Keeps working: an installed version of the library, because it is open source under the Apache 2.0 licence.
- Stops: fixes and new releases, including security fixes.
- Not affected: the wider NVIDIA Agent Toolkit announced in March 2026, NVIDIA NIM, NVIDIA Dynamo and NeMo Guardrails.
- Not affected: agent logic written in LangGraph, LangChain, CrewAI or Google ADK.
A checklist before the date
- List what you use the toolkit for: configuration, tracing, profiling, evaluation, serving.
- Pin the version you run today, and record it.
- Move tracing to NeMo Relay first. It attaches to an existing agent and does not change what the agent does.
- Move running agents to NeMo Fabric. Your own agent needs an adapter.
- Move evaluation to NeMo Helix.
- Pin the versions of the replacements, because all three are changing quickly.
- Test on a clean machine. We found the install path of the replacements needed fixes, and reported them to NVIDIA.
How much work is it?
It depends on how much of the toolkit you used. Tracing is a small change. Running agents through Fabric means writing an adapter, which was about 350 lines for NVIDIA's smallest example. Evaluation means setting up Helix and moving your test sets. Teams that used only the toolkit's configuration format have the most to move, because that format has no direct successor.
Where Katonic fits
Every agent built in Katonic is a declarative definition that compiles to NVIDIA's open agent software. When NVIDIA changes the runtime, Katonic changes the compiler and your agents carry over. Katonic has installed and tested all three replacements and has built a NeMo Fabric adapter for its agent definitions, which is that change under way.
Read next
- How to migrate from the NVIDIA NeMo Agent Toolkit →
- NeMo Agent Toolkit is deprecated: what replaces it? →
- NVIDIA NeMo Helix, Relay and Fabric: field guide →
- How to use NeMo Relay with LangGraph →
- How to write a NeMo Fabric adapter →
- NVIDIA migration guide →
Questions and answers
When is the NVIDIA NeMo Agent Toolkit end of life?
By the end of 2026. NVIDIA deprecated it as of October 2026.
Will the NeMo Agent Toolkit stop working at end of life?
No. An installed version keeps running, but you should not expect fixes after that date.
What should I move to?
NeMo Relay for tracing and governance, NeMo Fabric for running agents, and NeMo Helix for evaluation.
Is the NVIDIA Agent Toolkit also ending?
No. Only the NeMo Agent Toolkit library was deprecated. The wider NVIDIA Agent Toolkit announced in March 2026 continues.
What should I migrate first?
Tracing, to NeMo Relay. It attaches to an existing agent and does not change its behaviour.
Do agents built in Katonic need migrating?
No. They are declarative definitions, and Katonic changes the compiler when NVIDIA changes the runtime.