NeMo Agent Toolkit
Is there a UI for the NVIDIA NeMo Agent Toolkit?
Yes, a small one. NVIDIA publishes an open-source chat interface for the NeMo Agent Toolkit that lets a developer talk to a running agent and see the steps it takes. The toolkit itself is a library with a command line. It does not include a visual builder, an administration console or a workspace where staff use agents. Those come from a platform built on the toolkit.
Update, November 2026
NVIDIA has deprecated the NeMo Agent Toolkit library as of October 2026, with end of life at the end of 2026, and names NeMo Relay, NeMo Fabric and NeMo Helix as its successors. The NVIDIA Agent Toolkit announced in March 2026 continues. Every agent built in Katonic is a declarative definition that compiles to NVIDIA's open agent software. Today that software is the NeMo Agent Toolkit. When NVIDIA changes the runtime, Katonic changes the compiler and your agents carry over.
What NVIDIA provides
- A command line for running, serving and evaluating an agent.
- A server that exposes an agent so other systems can call it.
- An open-source chat interface for talking to that agent and viewing its intermediate steps.
- Tracing output that can be sent to an observability tool of your choice.
Four interfaces people mean when they ask for a UI
| Interface | Who uses it | What it does | In the toolkit |
|---|---|---|---|
| Test chat | Developers | Talk to one agent and inspect its steps | Yes, open source |
| Builder | Developers and business users | Create and change agents in a browser | No |
| Administration console | IT and risk teams | Access, budgets, guardrail policy, approvals, audit | No |
| Workspace | All staff | Find and use approved agents every day | No |
Why the gap matters
A developer can do everything from the command line. An organisation cannot. Once more than one team builds agents, someone has to decide who may use which agent, what it may spend, which guardrails apply and who approved it. Those decisions need a console, and the people using the agents need somewhere to find them.
How to fill it
- Build the interfaces yourself on the toolkit server. This suits a team with front-end engineers and one or two agents.
- Use an observability product for traces and keep the rest on the command line. This suits developers only.
- Use an agent platform built on the toolkit, which supplies the builder, the console and the workspace together.
Where Katonic fits
Katonic supplies the interfaces around the NeMo Agent Toolkit: a builder for developers and business users, a control console for access, budgets, guardrails, approvals and audit, and a workspace where staff use approved agents. Every agent built in Katonic compiles to NVIDIA's open agent software, and the platform runs on infrastructure you own.
Read next
- Can you build NVIDIA Agent Toolkit agents without writing code? →
- NVIDIA Agent Toolkit vs NeMo Agent Toolkit →
- Running toolkit agents in production →
- NVIDIA Agent Toolkit for enterprise AI →
- NVIDIA NeMo Agent Toolkit is deprecated: what replaces it? →
- NVIDIA migration guide for the NeMo Agent Toolkit →
Questions and answers
Does the NeMo Agent Toolkit have a graphical interface?
NVIDIA publishes an open-source chat interface for testing a running agent. The toolkit has no visual builder or administration console of its own.
Is there a visual builder for the NVIDIA Agent Toolkit?
Not in the toolkit. Agent platforms built on it, such as Katonic, provide one.
Can staff use toolkit agents without a developer?
They need an interface in front of the agent. That is either one you build on the toolkit server or the workspace of a platform.
Where do I manage access and budgets for toolkit agents?
Outside the toolkit. Access control, budgets and approvals are platform functions that sit around the agents.