NVIDIA · dagardner-nv · Jul 31, 2026 · Jul 31, 2026 · Jul 31, 2026 · Jul 31, 2026
@@ -112,7 +112,7 @@ config = FabricConfig(
     models={
         "default": ModelConfig(
             provider="nvidia",
-            model="nvidia/nemotron-3-nano-30b-a3b",
+            model="nvidia/nemotron-3-nano-omni-30b-a3b-reasoning",
             api_key_env="NVIDIA_API_KEY",
             base_url="https://integrate.api.nvidia.com/v1",
         )

@@ -24,7 +24,7 @@ The following table shows which components each installation provides:
 
 For split runtime and adapter environments, configure `ADAPTER_PYTHON` and use
 matching NeMo Fabric release versions. Refer to the
-[installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
+[installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
 
 The `full` extra is equivalent to `harness`. Relay is optional for ordinary
 runs. Relay telemetry and `Runtime.invoke_stream()` require the external CLI
@@ -58,7 +58,7 @@ Unset unused `ANTHROPIC_API_KEY` and `ANTHROPIC_AUTH_TOKEN` variables before
 using WIF. Anthropic credential resolution treats an empty variable as selected,
 so an empty API credential prevents fallback to a federation profile.
 
-Refer to the [Claude adapter authentication guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/integrations/harness/claude)
+Refer to the [Claude adapter authentication guide](https://docs.nvidia.com/nemo/fabric/integrations/harness-integrations/claude-code)
 for mode selection, required WIF variables, and the Relay boundary. Package
 installation is verified by the adapter wheel and module-entrypoint tests.
 
@@ -122,7 +122,7 @@ by the SDK and is not persisted as a NeMo Fabric artifact.
 
 Relay requires a separately installed NeMo Relay 0.6.x CLI on `PATH`; the Python
 `nemo-relay` package does not provide the executable. Follow the
-[NeMo Relay installation instructions](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-nemo-relay).
+[NeMo Relay installation instructions](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-nemo-relay).
 
 Enable Relay through the normalized NeMo Fabric configuration:
 

@@ -25,6 +25,6 @@ Installation can be performed using the `nemo-fabric` meta package with the `cla
 
 The `full` extra is equivalent to `harness`. NeMo Relay is optional for ordinary
 runs. NeMo Relay telemetry and streaming require the `nemo-relay` CLI tool.
-Refer to the [NeMo Relay installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#nemo-relay-cli) for instructions.
+Refer to the [NeMo Relay installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#nemo-relay-cli) for instructions.
 
-Refer to the [installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install) for more details.
+Refer to the [installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install) for more details.
@@ -41,7 +41,7 @@ full = [
 Repository = "https://github.com/NVIDIA/NeMo-Fabric"
 Homepage = "https://github.com/NVIDIA/NeMo-Fabric"
 Issues = "https://github.com/NVIDIA/NeMo-Fabric/issues"
-Documentation = "https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric"
+Documentation = "https://docs.nvidia.com/nemo/fabric"
 
 [tool.setuptools.packages.find]
 where = ["src"]

@@ -23,7 +23,7 @@ The following table shows which components each installation provides:
 For an environment-managed SDK, use `openai-codex==0.144.4`. For split runtime
 and adapter environments, configure `ADAPTER_PYTHON` and use matching NeMo
 Fabric release versions. Refer to the
-[installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
+[installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
 
 The `full` extra is equivalent to `harness`. Relay is optional for ordinary
 runs. Relay telemetry and `Runtime.invoke_stream()` require the external CLI
@@ -147,7 +147,7 @@ Codex state variables, the selected model's `api_key_env`, and explicit
 
 Relay requires a separately installed NeMo Relay 0.6.x CLI on `PATH`; the Python
 `nemo-relay` package does not provide the executable. Follow the
-[NeMo Relay installation instructions](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-nemo-relay).
+[NeMo Relay installation instructions](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-nemo-relay).
 
 Enable Relay with `FabricConfig.enable_relay(...)`. The adapter starts the
 installed `nemo-relay` CLI as a supervised sidecar; do not start the gateway

@@ -25,6 +25,6 @@ Installation can be performed using the `nemo-fabric` meta package with the `cod
 
 The `full` extra is equivalent to `harness`. NeMo Relay is optional for ordinary
 runs. NeMo Relay telemetry and streaming require the `nemo-relay` CLI tool.
-Refer to the [NeMo Relay installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#nemo-relay-cli) for instructions.
+Refer to the [NeMo Relay installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#nemo-relay-cli) for instructions.
 
-Refer to the [installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install) for more details.
+Refer to the [installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install) for more details.
@@ -41,7 +41,7 @@ full = [
 Repository = "https://github.com/NVIDIA/NeMo-Fabric"
 Homepage = "https://github.com/NVIDIA/NeMo-Fabric"
 Issues = "https://github.com/NVIDIA/NeMo-Fabric/issues"
-Documentation = "https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric"
+Documentation = "https://docs.nvidia.com/nemo/fabric"
 
 [tool.setuptools.packages.find]
 where = ["src"]

@@ -15,7 +15,7 @@ Install the package directly when developing an adapter:
 pip install nemo-fabric-adapters-common
 ```
 
-Refer to the [NeMo Fabric documentation](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric)
+Refer to the [NeMo Fabric documentation](https://docs.nvidia.com/nemo/fabric)
 for adapter and configuration guidance. Source code is available in the
 [NVIDIA NeMo Fabric repository](https://github.com/NVIDIA/nemo-fabric/).
 

@@ -23,6 +23,6 @@ Install the package directly when developing an adapter:
 pip install nemo-fabric-adapters-common
 ```
 
-Refer to the [NeMo Fabric documentation](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric)
+Refer to the [NeMo Fabric documentation](https://docs.nvidia.com/nemo/fabric)
 for adapter and configuration guidance. Source code is available in the
 [NVIDIA NeMo Fabric repository](https://github.com/NVIDIA/NeMo-Fabric).
@@ -29,7 +29,7 @@ requires-python = ">=3.11"
 Repository = "https://github.com/NVIDIA/NeMo-Fabric"
 Homepage = "https://github.com/NVIDIA/NeMo-Fabric"
 Issues = "https://github.com/NVIDIA/NeMo-Fabric/issues"
-Documentation = "https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric"
+Documentation = "https://docs.nvidia.com/nemo/fabric"
 
 [tool.setuptools.packages.find]
 where = ["src"]

@@ -26,7 +26,7 @@ For an environment-managed stack, use `deepagents>=0.6.12,<0.7.0`,
 `langchain>=1.3,<2.0`, and `langgraph>=1.2,<2.0`. For split runtime and adapter
 environments, configure `ADAPTER_PYTHON` and use matching NeMo Fabric release
 versions. Refer to the
-[installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
+[installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
 
 ## Model and Authentication
 

@@ -30,4 +30,4 @@ NeMo Relay is optional for ordinary runs. NeMo Relay telemetry and streaming
 require one of the installations in the table that includes the NeMo Relay
 Python package.
 
-Refer to the [installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install) for more details.
+Refer to the [installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install) for more details.
@@ -53,7 +53,7 @@ full = [
 Repository = "https://github.com/NVIDIA/NeMo-Fabric"
 Homepage = "https://github.com/NVIDIA/NeMo-Fabric"
 Issues = "https://github.com/NVIDIA/NeMo-Fabric/issues"
-Documentation = "https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric"
+Documentation = "https://docs.nvidia.com/nemo/fabric"
 
 [tool.setuptools.packages.find]
 where = ["src"]

@@ -24,7 +24,7 @@ table shows which components each installation provides:
 For an environment-managed harness, use `hermes-agent>=0.17.0`. For split
 runtime and adapter environments, configure `ADAPTER_PYTHON` and use matching
 NeMo Fabric release versions. Refer to the
-[installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
+[installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install#install-an-adapter-and-harness-without-the-runtime).
 
 Relay is optional for ordinary runs. Relay telemetry and
 `Runtime.invoke_stream()` require one of the installations in the table that

@@ -31,4 +31,4 @@ NeMo Relay is optional for ordinary runs. NeMo Relay telemetry and streaming
 require one of the installations in the table that includes the NeMo Relay
 Python package.
 
-Refer to the [installation guide](https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric/getting-started/install) for more details.
+Refer to the [installation guide](https://docs.nvidia.com/nemo/fabric/getting-started/install) for more details.
@@ -45,7 +45,7 @@ full = [
 Repository = "https://github.com/NVIDIA/NeMo-Fabric"
 Homepage = "https://github.com/NVIDIA/NeMo-Fabric"
 Issues = "https://github.com/NVIDIA/NeMo-Fabric/issues"
-Documentation = "https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric"
+Documentation = "https://docs.nvidia.com/nemo/fabric"
 
 [tool.setuptools.packages.find]
 where = ["src"]

@@ -184,7 +184,7 @@ fn hermes() -> FabricConfig {
         "nvidia.fabric.hermes",
         Some(model(
             "nvidia",
-            "nvidia/nemotron-3-nano-30b-a3b",
+            "nvidia/nemotron-3-nano-omni-30b-a3b-reasoning",
             Some("NVIDIA_API_KEY"),
             Some(NVIDIA_API_CATALOG_BASE_URL),
         )),
@@ -240,7 +240,7 @@ fn deepagents() -> FabricConfig {
         "nvidia.fabric.langchain.deepagents",
         Some(model(
             "nvidia",
-            "nvidia/nemotron-3-nano-30b-a3b",
+            "nvidia/nemotron-3-nano-omni-30b-a3b-reasoning",
             Some("NVIDIA_API_KEY"),
             Some(NVIDIA_API_CATALOG_BASE_URL),
         )),

@@ -431,7 +431,7 @@ mod tests {
             };
             let source = fs::read_to_string(launcher).expect("read launcher");
             assert!(source.contains("nvidia.fabric.hermes"));
-            assert!(source.contains("nvidia/nemotron-3-nano-30b-a3b"));
+            assert!(source.contains("nvidia/nemotron-3-nano-omni-30b-a3b-reasoning"));
             assert!(source.contains("https://integrate.api.nvidia.com/v1"));
             if language == Language::Rust {
                 let manifest =

@@ -1,15 +1,17 @@
 ---
-title: "NVIDIA NeMo Fabric"
+title: "NVIDIA NeMo Fabric Documentation"
 slug: "/about-nemo-fabric/overview"
 description: "Configure, plan, run, and observe agent harnesses through one typed execution contract."
+template-library-version: "1.0.0"
 ---
 {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 SPDX-License-Identifier: Apache-2.0 */}
 
-NeMo Fabric is the harness-management layer that turns multiple agent runtimes
+NVIDIA NeMo Fabric is the harness-management layer that turns multiple agent runtimes
 into one configurable, observable execution surface. Applications use the same
 versioned config, lifecycle, result, artifact, and telemetry contracts whether
-the selected harness is Hermes Agent, Codex, or a custom adapter.
+the selected harness is [Hermes Agent](https://hermes-agent.nousresearch.com/docs/),
+[Codex SDK](https://openai.com/codex/), or a custom adapter.
 
 NeMo Fabric owns the seam between an application and its harness. It resolves
 configuration, selects an adapter, drives the runtime lifecycle,
@@ -19,25 +21,42 @@ into the caller.
 ## What NeMo Fabric Gives You
 
 <CardGroup cols={2}>
-  <Card title="Typed configuration">
+  <Card title="Typed Configuration">
     Construct a complete, versioned `FabricConfig` in Python. Applications
     create variants with ordinary functions and typed copies.
   </Card>
-  <Card title="Harness-neutral execution">
+  <Card title="Harness-Neutral Execution">
     Plan and invoke different harnesses through one Rust core, CLI, and Python
     SDK instead of embedding harness launch logic in every consumer.
   </Card>
-  <Card title="Typed lifecycle contracts">
+  <Card title="Typed Lifecycle Contracts">
     Resolve configs, inspect capabilities, run single-invocation jobs, and hold
     multi-turn runtimes with typed requests, plans, handles, and results.
   </Card>
-  <Card title="Normalized evidence">
+  <Card title="Normalized Evidence">
     Collect output, errors, lifecycle events, artifact manifests, and telemetry
     references in stable contracts suitable for platforms and evaluations.
   </Card>
 </CardGroup>
 
-## How NeMo Fabric Fits
+
+## Choose Your Interface
+
+Use the following table to choose the NeMo Fabric interface that best fits how
+your application works with harnesses:
+
+| Interface | Use it when | Start with |
+| --- | --- | --- |
+| Python SDK | Your application owns job config, runtime lifecycle, or multi-turn state | [Client API](../reference/api/python-library-reference/nemo_fabric.client.md) |
+| Runtime API | You need multiple ordered turns over one live harness runtime | [Runtime](../reference/api/python-library-reference/nemo_fabric.runtime.md) |
+| Streaming API | You need live ATOF records generated by NeMo Relay during a runtime turn | [Streaming](../reference/api/python-library-reference/nemo_fabric.streaming.md) |
+| `nemo-fabric` CLI | You are experimenting with harnesses, running maintained examples, or troubleshooting configs | [Experimentation CLI](../experimentation/cli.mdx) |
+| JSON Schema | You are building editors, validation, code generation, or another language binding | Committed schemas in the [repository](https://github.com/NVIDIA/NeMo-Fabric/tree/main/schemas) |
+
+Use `FabricConfig` as the canonical configuration contract. CLI selectors
+obtain complete typed configs from built-in presets or maintained examples.
+
+## Core Workflow
 
 ```text
 Application or evaluation harness
@@ -55,87 +74,6 @@ Hermes Agent | Codex | custom harness
 RunResult + artifacts + events + telemetry references
 ```
 
-The experimentation CLI and its catalogs live in the Rust `fabric-cli` crate
-and are installed separately from the Python SDK. Built-in presets and
-maintained examples produce a complete `FabricConfig` before using the same
-run-plan contract. Adapters own harness-specific preparation and invocation;
-consumers own the request and returned evidence.
-
-## Quick Start
-
-Install `just` 1.50.0+ if it is not already available.
-
-```bash
-cargo install just --locked
-```
-
-Refer to the [official installation guide](https://just.systems/man/en/installation.html)
-for more details.
-
-Ensure that the Cargo bin directory is in your `PATH`:
-
-```bash
-export PATH="$HOME/.cargo/bin:$PATH"
-```
-
-Create a Python virtual environment and activate it (replace `3.13` with your preferred Python version):
-
-```bash
-uv venv -p 3.13 --seed .venv
-source .venv/bin/activate
-```
-
-Build the Python SDK and install the Rust CLI from a source checkout:
-
-```bash
-just build-all
-```
-
-Run the example through the Python SDK:
-
-```python
-import asyncio
-from examples.code_review_agent import BASE_DIR, hermes_config
-from nemo_fabric import Fabric
-
-
-async def main() -> None:
-    config = hermes_config()
-    client = Fabric()
-    result = await client.run(
-        config,
-        base_dir=BASE_DIR,
-        input="Reply with exactly: fabric works",
-    )
-
-    print(result.status)
-
-
-asyncio.run(main())
-```
-
-Harness installation and credential requirements differ by adapter. The
-[repository quick start](https://github.com/NVIDIA/NeMo-Fabric#quick-start-hermes-agent)
-contains the complete Hermes Agent environment recipe.
-
-Refer to the [Python SDK guide](../sdk/python.mdx) for planning,
-diagnostics, typed requests, multi-turn runtimes, and NVIDIA NeMo Relay streaming.
-
-## Choose Your Interface
-
-| Interface | Use it when | Start with |
-| --- | --- | --- |
-| Python SDK | Your application owns job config, runtime lifecycle, or multi-turn state | [Client API](../reference/api/python-library-reference/nemo_fabric.client.md) |
-| Runtime API | You need multiple ordered turns over one live harness runtime | [Runtime](../reference/api/python-library-reference/nemo_fabric.runtime.md) |
-| Streaming API | You need live ATOF records generated by NeMo Relay during a runtime turn | [Streaming](../reference/api/python-library-reference/nemo_fabric.streaming.md) |
-| `nemo-fabric` CLI | You are experimenting with harnesses, running maintained examples, or troubleshooting configs | [Experimentation CLI](../experimentation/cli.mdx) |
-| JSON Schema | You are building editors, validation, code generation, or another language binding | Committed schemas in the [repository](https://github.com/NVIDIA/NeMo-Fabric/tree/main/schemas) |
-
-Use `FabricConfig` as the canonical configuration contract. CLI selectors
-obtain complete typed configs from built-in presets or maintained examples.
-
-## Core Workflow
-
 1. **Configure** a typed `FabricConfig` with a harness adapter,
    environment, models, tools, skills, MCP, and telemetry.
 2. **Create variants** from deep copies to vary harness, model, environment, or
@@ -148,38 +86,14 @@ obtain complete typed configs from built-in presets or maintained examples.
 5. **Consume evidence** from `RunResult`: output, structured failure details,
    artifacts, events, and telemetry references.
 
-## Next Steps
+## Learn More
 
-<CardGroup cols={2}>
-  <Card
-    title="Client API"
-    href="/reference/api/python-library-reference/client"
-  >
-    Resolve, plan, diagnose, run, and start stateful runtimes.
-  </Card>
-  <Card
-    title="Runtime"
-    href="/reference/api/python-library-reference/runtime"
-  >
-    Invoke multiple ordered turns and stop runtime handles safely.
-  </Card>
-  <Card
-    title="Streaming"
-    href="/reference/api/python-library-reference/streaming"
-  >
-    Consume live, raw NeMo Relay ATOF records and retrieve the terminal run result.
-  </Card>
-  <Card
-    title="Types"
-    href="/reference/api/python-library-reference/types"
-  >
-    Explore all mutable config objects and immutable request, plan, result,
-    artifact, telemetry, and runtime models.
-  </Card>
-  <Card
-    title="Errors"
-    href="/reference/api/python-library-reference/errors"
-  >
-    Handle config, capability, lifecycle, state, and native-extension failures.
-  </Card>
-</CardGroup>
+Continue exploring NeMo Fabric through these resources.
+
+- **Installation** — [Installation](../getting-started/install.mdx) to set up the runtime and adapters.
+- **Quickstart** — [Quickstart](../getting-started/quickstart.mdx) to build from
+  source and run the maintained SDK example.
+- **Python SDK** — [Python SDK](../sdk/python.mdx) for planning, diagnostics,
+  typed requests, and multi-turn runtimes.
+- **API Reference** — [Client API](../reference/api/python-library-reference/nemo_fabric.client.md)
+  to resolve, plan, diagnose, run, and start stateful runtimes.