NVIDIA · GPUtester · May 29, 2026 · May 29, 2026
@@ -3,5 +3,5 @@ SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All
 SPDX-License-Identifier: Apache-2.0
 -->
 
-# NVIDIA NeMo Agent Toolkit Code of Conduct
+# NVIDIA NeMo Relay Code of Conduct
 This project has adopted the [Contributor Covenant Code of Conduct](https://docs.rapids.ai/resources/conduct/).
@@ -227,10 +227,12 @@ Use the stable root-level wrappers:
 `apply-patches.sh` expects clean third-party checkouts. After editing an integration checkout, run `./scripts/generate-patches.sh` to regenerate patch files and verify they apply to a clean detached checkout.
 
 ### Public API-based Integrations
-Some integrations can be implemented using public APIs without patching. Currently the Python based integrations are located under `python/nemo_relay/integrations/` with their own README files and test suites.
+Some integrations can be implemented using public APIs without patching. The Python integrations live under `python/nemo_relay/integrations/`, are documented in `docs/supported-integrations/`, and have test suites under `python/tests/integrations/`.
 
 Current public API-based integrations include:
 - LangChain: `python/nemo_relay/integrations/langchain`
+- LangGraph: `python/nemo_relay/integrations/langgraph`
+- Deep Agents: `python/nemo_relay/integrations/deepagents`
 
 ## Documentation And Contribution Workflow
 

@@ -27,7 +27,7 @@ agent crosses a request, tool, or LLM boundary.
 Agent applications rarely live inside one clean abstraction. A production stack
 might combine NeMo Agent Toolkit, LangChain, LangGraph, provider SDKs, custom
 harness code, NeMo Guardrails, tracing systems, and evaluation pipelines. NeMo
-Flow sits underneath those choices as the shared runtime contract for scopes,
+Relay sits underneath those choices as the shared runtime contract for scopes,
 middleware, plugins, lifecycle events, adaptive behavior, and observability.
 
 Built as a Rust core with primary Rust, Python, and Node.js bindings, NeMo Relay

@@ -49,22 +49,22 @@ flowchart TB
     User[User / Application]
     Framework[Agent Framework or Harness]
     Toolkit[NeMo Agent Toolkit / Framework Integrations]
-    Flow[NeMo Relay Runtime]
+    Relay[NeMo Relay Runtime]
     Provider[Model, Tool, or Provider SDK]
     Obs[Subscribers and Observability Backends]
     Policy[Guardrails, Intercepts, and Plugins]
 
     User --> Framework
     Framework --> Toolkit
-    Toolkit --> Flow
-    Framework -. direct instrumentation .-> Flow
-    Flow --> Provider
-    Policy --> Flow
-    Flow --> Obs
+    Toolkit --> Relay
+    Framework -. direct instrumentation .-> Relay
+    Relay --> Provider
+    Policy --> Relay
+    Relay --> Obs
 
     class Framework yellow-lightest;
     class Toolkit blue-lightest;
-    class Flow green-light;
+    class Relay green-light;
     class Provider purple-lightest;
     class Obs grey-light;
     class Policy green-lightest;

@@ -7,3 +7,36 @@ position: 5
 SPDX-License-Identifier: Apache-2.0 */}
 
 Choose the Quick Start guide for the primary binding that you plan to use.
+
+<CardGroup cols={3}>
+<Card
+  title="Python Quick Start"
+  icon="brands python"
+  iconPosition="left"
+  href="/getting-started/quick-start/python"
+>
+
+Smallest Python workflow that emits scope, tool, and LLM events.
+</Card>
+
+<Card
+  title="Node.js Quick Start"
+  icon="brands node-js"
+  iconPosition="left"
+  href="/getting-started/quick-start/nodejs"
+>
+
+Smallest Node.js workflow that emits scope, tool, and LLM events.
+</Card>
+
+<Card
+  title="Rust Quick Start"
+  icon="brands rust"
+  iconPosition="left"
+  href="/getting-started/quick-start/rust"
+>
+
+Smallest Rust workflow that emits scope, tool, and LLM events.
+</Card>
+
+</CardGroup>
@@ -54,7 +54,7 @@ Codex, Cursor, and Hermes Agent support.
 
 Start by identifying the framework's stable tool and LLM boundaries. Prefer
 managed execution wrappers wherever the framework exposes a callback that NeMo
-Flow can own. Use explicit API calls only when the framework owns invocation
+Relay can own. Use explicit API calls only when the framework owns invocation
 internally but exposes reliable start and finish hooks.
 
 Validate that application-visible framework behavior does not change. Then

@@ -28,7 +28,7 @@ NeMo Relay middleware surfaces operate on JSON-compatible data. Frameworks do no
 ## Recommended Strategies
 
 These strategies keep provider and framework data JSON-compatible before it reaches NeMo
-Flow.
+Relay.
 
 - Convert provider payloads into a stable request shape before NeMo Relay sees them.
 - Preserve opaque framework objects outside the middleware path and pass only the serializable projection into the runtime.

@@ -132,7 +132,7 @@ ls .nemo-relay/atif
 The gateway writes or updates an ATIF snapshot when it receives
 `on_session_end`, `on_session_finalize`, or `on_session_reset`.
 `on_session_end` is a per-turn snapshot boundary: it does not close the NeMo
-Flow session and does not emit a visible trajectory mark. `on_session_finalize`
+Relay session and does not emit a visible trajectory mark. `on_session_finalize`
 and `on_session_reset` close the session.
 
 ## Troubleshoot LLM Lifecycle

@@ -82,7 +82,7 @@ plugins.
 
 ### Why The Name "NeMo Relay"?
 
-"NeMo" places the project in the NVIDIA NeMo ecosystem. "Flow" refers to the
+"NeMo" places the project in the NVIDIA NeMo ecosystem. "Relay" refers to the
 runtime flow of agent work through scopes, middleware, events, subscribers,
 plugins, and exporters.
 

@@ -32,8 +32,6 @@ environment variables, or shared TOML config.
 - Hermes does not require a static bundle in this directory. The setup wizard
   (`nemo-relay config`) merges hook commands into `.hermes/config.yaml` when
   hermes is selected.
-- `hermes/` contains a native Hermes Python plugin prototype that writes ATIF
-  from Hermes plugin middleware without running the gateway HTTP process.
 
 ## Transparent Setup