1. Install One Harness
Ask an agent to review a small Python function through NVIDIA NeMo Fabric. This package-based path uses LangChain Deep Agents and an NVIDIA-hosted model. It requires Python 3.11 or later and an NVIDIA API key; the Installation Overview describes supported platforms.
Run this Quickstart on Linux, macOS, or Windows using WSL2. On Windows, run all commands inside your WSL2 Linux environment.
This is the first of three connected quickstarts and an optional sandbox continuation. Keep first_agent.py and its configuration for the next two guides.
Install One Harness
Create an isolated application environment, then install NeMo Fabric and its supported Deep Agents adapter and dependencies. In your POSIX shell, run:
This example does not require the separate CLI or NeMo Relay.
Provide Model Access
Create an API key at NVIDIA Build and set it in the shell that will run the application:
Keep the key out of the Python file.
Run a Code Review
Save this complete example as first_agent.py in your application directory. The request supplies the function inline and asks for a review without tool use or file changes.
Run it from the application directory:
Check the Outcome
The returned adapter ID should be nvidia.fabric.langchain.deepagents. A successful request has status succeeded and request ID first-code-review. The review should identify that average([]) causes division by zero. The prose and suggested fix can vary; check the status and the finding separately. The request to avoid tools and file changes is an instruction to the agent, not a security boundary.
Fabric.run() starts the runtime, invokes it once, and attempts shutdown. It can return a failed normalized result; configuration and lifecycle failures can instead raise SDK exceptions. Follow Troubleshooting if the run does not succeed.
Next Steps
Change only the input to ask for a test that covers the empty-list case. The same configuration and result-handling code still apply. Then continue to 2. Switch Harnesses to run the review through another harness while retaining your application interface.
For further exploration, see Multi-Turn Runtimes to preserve state between related turns, or the maintained onboarding notebooks for an interactive tour.