From 35ed906aa076445cd8643bb2837e0ed7c8223139 Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 13:50:54 -0700 Subject: [PATCH 1/7] docs: align About pages with tech-docs templates - Convert overview headings to title case and restructure the About overview to the tech-docs About template (Benefits, Use Cases, Core Workflow, Learn More) - Move the source-build Quick Start into a dedicated Getting Started page - Rename nav labels (Install -> Installation, Quickstart -> Beginner Tutorial) and add a Quickstart page; pin slugs so existing URLs are stable - Scaffold the Release Notes page from the tech-docs release-notes template Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/overview.mdx | 211 ++++++++--------------- docs/about-nemo-fabric/release-notes.mdx | 58 ++++++- docs/getting-started/install.mdx | 2 +- docs/getting-started/quick-start.mdx | 66 +++++++ docs/getting-started/quickstart.mdx | 2 +- docs/index.yml | 7 +- 6 files changed, 204 insertions(+), 142 deletions(-) create mode 100644 docs/getting-started/quick-start.mdx diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index ed8711bc5..2996d4b44 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -1,43 +1,83 @@ --- -title: "NVIDIA NeMo Fabric" +title: "NVIDIA NeMo Fabric Documentation" +sidebar-title: "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 -into one configurable, observable execution surface. Applications use the same -versioned config, lifecycle, result, artifact, and telemetry contracts whether -the selected harness is Hermes, Codex SDK, or a custom adapter. +[NVIDIA NeMo Fabric](https://github.com/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, Codex SDK, 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, -and returns normalized evidence without leaking harness-specific control code -into the caller. +configuration, selects an adapter, drives the runtime lifecycle, and returns +normalized evidence without leaking harness-specific control code into the +caller. -## What NeMo Fabric gives you +## Benefits + +NeMo Fabric gives applications one contract across every supported harness. - + Use a versioned `agent.yaml` package or construct the same typed `FabricConfig` in Python. Applications create variants from typed copies; portable file packages can use ordered profiles. - + Plan and invoke different harnesses through one Rust core, CLI, and Python SDK instead of embedding harness launch logic in every consumer. - + Resolve configs, inspect capabilities, run one-shot jobs, and hold multi-turn runtimes with typed requests, plans, handles, and results. - + Collect output, errors, lifecycle events, artifact manifests, and telemetry references in stable contracts suitable for platforms and evaluations. -## How NeMo Fabric fits +## Use Cases + +Teams use NeMo Fabric to run agents through a single contract, hold multi-turn +sessions over a live harness, and integrate agent execution into platforms and +evaluation pipelines. + +| Use Case | Reader Goal | Result | +| --- | --- | --- | +| Application integration | Run one-shot agent jobs from an application that owns its own config. | A normalized `RunResult` with output, artifacts, events, and telemetry references. | +| Multi-turn runtimes | Drive several ordered turns over one live harness runtime. | A stateful runtime handle you start, invoke, and stop through one lifecycle contract. | +| Platform and evaluation harnesses | Plan and invoke many harnesses behind one typed surface. | Stable, harness-neutral evidence suitable for platforms and evaluations. | + +### Application Integration + +An application owns its job config and consumes returned evidence. Configure an +agent package or typed `FabricConfig`, run it through the Python SDK, and read +the normalized `RunResult`. Refer to the [Python SDK guide](/sdk/python) for +typed requests and one-shot run examples. + +### Multi-Turn Runtimes + +When a workflow needs several ordered turns over one live harness, start a +runtime and invoke it turn by turn before stopping it. Refer to the +[Runtime reference](/reference/api/python-library-reference/runtime) for the +start, invoke, and stop lifecycle. + +### Platform And Evaluation Harnesses + +Platforms and evaluation systems plan and invoke different harnesses behind one +typed surface, then consume stable evidence contracts. Use the `fabric` CLI or +committed JSON Schemas to validate packages and build language bindings. + +## Core Workflow + +NeMo Fabric is organized around one flow from configuration to normalized +evidence: ```text Application or evaluation harness @@ -55,125 +95,24 @@ Hermes | Codex SDK | custom harness RunResult + artifacts + events + telemetry references ``` -The CLI and Python SDK are separate interfaces over the same core. File-backed -and typed configs converge on the same resolved config and run-plan contracts. -Adapters own harness-specific preparation and invocation; consumers own the -request and the use of 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 -``` - -Install the Python SDK with its native binding and the 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) -contains the complete Hermes environment recipe. - -Refer to the [Python SDK guide](/sdk/python) for planning, diagnostics, typed -requests, and multi-turn runtime examples. - -## 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/client) | -| Runtime API | You need multiple ordered turns over one live harness runtime | [Runtime](/reference/api/python-library-reference/runtime) | -| `fabric` CLI | You are validating packages, debugging profiles, or running reproducible local/CI jobs | `fabric validate`, `plan`, `doctor`, `run`, and `chat` | -| 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 `agent.yaml` when the agent package is the portable artifact. Use -`FabricConfig` when a platform already owns a larger job or deployment object -and wants to pass only its NeMo Fabric slice in memory. - -## Core workflow - -1. **Configure** an agent package or 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 - observability settings without mutating the base config. File-backed - packages may instead apply ordered profiles. -3. **Plan and diagnose** to resolve the adapter and check capabilities and - requirements before spending work on a runtime. -4. **Run or start a runtime** through the shared start, invoke, and stop - lifecycle contract. -5. **Consume evidence** from `RunResult`: output, structured failure details, - artifacts, events, and telemetry references. - -## Next steps - - - - Resolve, plan, diagnose, run, and start stateful runtimes. - - - Invoke multiple ordered turns and stop runtime handles safely. - - - Explore all mutable config objects and immutable request, plan, result, - artifact, telemetry, and runtime models. - - - Handle config, capability, lifecycle, state, and native-extension failures. - - +- **Configuration**: Use a versioned `agent.yaml` package or a typed + `FabricConfig` to describe the harness adapter, environment, models, tools, + skills, MCP, and telemetry. File-backed and typed configs converge on the same + resolved config and run-plan contracts. +- **Plan and diagnostics**: Resolve the adapter and check capabilities and + requirements before spending work on a runtime. +- **Runtime lifecycle**: Run a one-shot job or start a stateful runtime through + the shared start, invoke, and stop contract. Adapters own harness-specific + preparation and invocation; consumers own the request. +- **Normalized evidence**: Consume `RunResult` for output, structured failure + details, artifacts, events, and telemetry references. + +## Learn More + +Continue exploring NeMo Fabric through these resources. + +- **Installation** — [Installation](/getting-started/install) to set up the runtime and adapters. +- **Quickstart** — [Quickstart](/getting-started/quick-start) to build from source and run the SDK example. +- **Beginner Tutorial** — [Beginner Tutorial](/getting-started/quickstart) to run a simple agent end to end. +- **Python SDK** — [Python SDK](/sdk/python) for planning, diagnostics, typed requests, and multi-turn runtimes. +- **API Reference** — [Client API](/reference/api/python-library-reference/client) to resolve, plan, diagnose, run, and start stateful runtimes. diff --git a/docs/about-nemo-fabric/release-notes.mdx b/docs/about-nemo-fabric/release-notes.mdx index dbfb25b9f..8a68bc6dc 100644 --- a/docs/about-nemo-fabric/release-notes.mdx +++ b/docs/about-nemo-fabric/release-notes.mdx @@ -1,8 +1,60 @@ --- -title: "Release Notes" -description: "Release notes for NVIDIA NeMo Fabric." +title: "Release Notes for NVIDIA NeMo Fabric" +sidebar-title: "Release Notes" +description: "New features, fixed issues, and known issues for each NVIDIA NeMo Fabric release." +template-library-version: "1.0.0" --- {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 */} -To be filled out at release time +This documentation contains the release notes for [NVIDIA NeMo Fabric](/about-ne-mo-fabric/overview). + +## Release `` + +{/* Provide the release summary here. Replace the following paragraph with your own. */} +This release ``... + +### Highlights + +This release contains the following key changes: + +- Item 1. For details, refer to [Link to documentation](doc.mdx). +- Item 2. For details, refer to [Link to documentation](doc.mdx). +- Item 3. For details, refer to [Link to documentation](doc.mdx). + +{/* Optional: include this section if you have support matrix or compatibility updates for this release. */} +### Support Matrix and Compatibility Updates + +- Added support for ``. For details, refer to [Support Matrix](support-matrix.mdx). + +### Fixed Known Issues + +This version fixes the following known issues: + +- Fixed known issue 1. For details, refer to [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). +- Fixed known issue 2. For details, refer to [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). +- Fixed known issue 3. For details, refer to [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). + +For the full list of known issues, refer to [Known Issues](#all-known-issues). + +## All Known Issues + +{/* Provide the known issues list here. Replace the following information with your own, or state that there are no known issues in this release. */} +The known issues for NVIDIA NeMo Fabric are the following: + +- (New in version N.N.0) Known issue 1. [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). +- (New in version N.N.0) Known issue 2. [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). +- Known issue 3. [Link to documentation](doc.mdx) or [Link to troubleshooting](troubleshooting.mdx). + +{/* Optional: include this section if you want to link directly to previous versions of the release notes. */} +## Release Notes for Previous Versions + +- [N.N.N](link.mdx) +- [N.N.N](link.mdx) +- [N.N.N](link.mdx) + +## Related Topics + +{/* Provide a list of links to related topics. Include correct page titles and file names for the links. */} +- [related-topic-1](link.mdx) +- [related-topic-2](link.mdx) diff --git a/docs/getting-started/install.mdx b/docs/getting-started/install.mdx index 301569496..cc0d75144 100644 --- a/docs/getting-started/install.mdx +++ b/docs/getting-started/install.mdx @@ -1,5 +1,5 @@ --- -title: "Install NVIDIA NeMo Fabric" +title: "NVIDIA NeMo Fabric Installation" description: "Install guide." --- {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. diff --git a/docs/getting-started/quick-start.mdx b/docs/getting-started/quick-start.mdx new file mode 100644 index 000000000..40579e2e6 --- /dev/null +++ b/docs/getting-started/quick-start.mdx @@ -0,0 +1,66 @@ +--- +title: "NVIDIA NeMo Fabric Quickstart" +sidebar-title: "Quickstart" +description: "Install NeMo Fabric from a source checkout and run a simple agent through the Python SDK." +--- +{/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. +SPDX-License-Identifier: Apache-2.0 */} + +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 +``` + +Install the Python SDK with its native binding and the 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) +contains the complete Hermes environment recipe. + +Refer to the [Python SDK guide](/sdk/python) for planning, diagnostics, typed +requests, and multi-turn runtime examples. diff --git a/docs/getting-started/quickstart.mdx b/docs/getting-started/quickstart.mdx index 9175445e3..bf617c3c0 100644 --- a/docs/getting-started/quickstart.mdx +++ b/docs/getting-started/quickstart.mdx @@ -1,5 +1,5 @@ --- -title: "NVIDIA NeMo Fabric Quickstart" +title: "NVIDIA NeMo Fabric Beginner Tutorial" description: "Get started with NVIDIA NeMo Fabric." --- {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. diff --git a/docs/index.yml b/docs/index.yml index 025d6bb2f..a56e12edf 100644 --- a/docs/index.yml +++ b/docs/index.yml @@ -10,10 +10,15 @@ navigation: path: ./about-nemo-fabric/release-notes.mdx - section: Getting Started contents: - - page: Install + - page: Installation path: ./getting-started/install.mdx + slug: install - page: Quickstart + path: ./getting-started/quick-start.mdx + slug: quick-start + - page: Beginner Tutorial path: ./getting-started/quickstart.mdx + slug: quickstart - section: SDK contents: - page: Python SDK From a70c3f05bd7e491c566e99c24aedab0cc770e75e Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 13:53:44 -0700 Subject: [PATCH 2/7] docs: use numbered steps for overview Core Workflow Replace the concept bullets with the five-step workflow (Configure, Create variants, Plan and diagnose, Run or start a runtime, Consume evidence) with bold lead-ins. Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/overview.mdx | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index 2996d4b44..33752eb6e 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -95,17 +95,17 @@ Hermes | Codex SDK | custom harness RunResult + artifacts + events + telemetry references ``` -- **Configuration**: Use a versioned `agent.yaml` package or a typed - `FabricConfig` to describe the harness adapter, environment, models, tools, - skills, MCP, and telemetry. File-backed and typed configs converge on the same - resolved config and run-plan contracts. -- **Plan and diagnostics**: Resolve the adapter and check capabilities and - requirements before spending work on a runtime. -- **Runtime lifecycle**: Run a one-shot job or start a stateful runtime through - the shared start, invoke, and stop contract. Adapters own harness-specific - preparation and invocation; consumers own the request. -- **Normalized evidence**: Consume `RunResult` for output, structured failure - details, artifacts, events, and telemetry references. +1. **Configure** an agent package or 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 + observability settings without mutating the base config. File-backed packages + may instead apply ordered profiles. +3. **Plan and diagnose** to resolve the adapter and check capabilities and + requirements before spending work on a runtime. +4. **Run or start a runtime** through the shared start, invoke, and stop + lifecycle contract. +5. **Consume evidence** from `RunResult`: output, structured failure details, + artifacts, events, and telemetry references. ## Learn More From c0a0cc04fe706877413b6e2ea8500189df238a25 Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 14:25:01 -0700 Subject: [PATCH 3/7] docs: refine overview headings and interface section - Lowercase the conjunction in the "Platform and Evaluation Harnesses" subheading for consistent title case - Restore the "Choose Your Interface" comparison table and place it above Core Workflow Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/overview.mdx | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index 33752eb6e..7fc85ecaa 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -68,12 +68,25 @@ runtime and invoke it turn by turn before stopping it. Refer to the [Runtime reference](/reference/api/python-library-reference/runtime) for the start, invoke, and stop lifecycle. -### Platform And Evaluation Harnesses +### Platform and Evaluation Harnesses Platforms and evaluation systems plan and invoke different harnesses behind one typed surface, then consume stable evidence contracts. Use the `fabric` CLI or committed JSON Schemas to validate packages and build language bindings. +## 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/client) | +| Runtime API | You need multiple ordered turns over one live harness runtime | [Runtime](/reference/api/python-library-reference/runtime) | +| `fabric` CLI | You are validating packages, debugging profiles, or running reproducible local/CI jobs | `fabric validate`, `plan`, `doctor`, `run`, and `chat` | +| 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 `agent.yaml` when the agent package is the portable artifact. Use +`FabricConfig` when a platform already owns a larger job or deployment object +and wants to pass only its NeMo Fabric slice in memory. + ## Core Workflow NeMo Fabric is organized around one flow from configuration to normalized From 4e7bfdbef99d59df45723ab7ae16851a52906788 Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 14:29:12 -0700 Subject: [PATCH 4/7] docs: add list lead-in sentences to release notes sections Introduce lead-in sentences before the bullet lists under Support Matrix and Compatibility Updates, Release Notes for Previous Versions, and Related Topics, matching the other release-notes sections. Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/release-notes.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/about-nemo-fabric/release-notes.mdx b/docs/about-nemo-fabric/release-notes.mdx index 8a68bc6dc..bcfa4793c 100644 --- a/docs/about-nemo-fabric/release-notes.mdx +++ b/docs/about-nemo-fabric/release-notes.mdx @@ -25,6 +25,8 @@ This release contains the following key changes: {/* Optional: include this section if you have support matrix or compatibility updates for this release. */} ### Support Matrix and Compatibility Updates +This release includes the following support matrix and compatibility updates: + - Added support for ``. For details, refer to [Support Matrix](support-matrix.mdx). ### Fixed Known Issues @@ -49,6 +51,8 @@ The known issues for NVIDIA NeMo Fabric are the following: {/* Optional: include this section if you want to link directly to previous versions of the release notes. */} ## Release Notes for Previous Versions +Find the release notes for previous versions at the following links: + - [N.N.N](link.mdx) - [N.N.N](link.mdx) - [N.N.N](link.mdx) @@ -56,5 +60,7 @@ The known issues for NVIDIA NeMo Fabric are the following: ## Related Topics {/* Provide a list of links to related topics. Include correct page titles and file names for the links. */} +For more information, refer to the following related topics: + - [related-topic-1](link.mdx) - [related-topic-2](link.mdx) From eb90d144b9ffb9a5f3c06e91338e9942b6270688 Mon Sep 17 00:00:00 2001 From: lvojtku Date: Fri, 17 Jul 2026 14:31:00 -0700 Subject: [PATCH 5/7] Update docs/about-nemo-fabric/overview.mdx Co-authored-by: David Gardner <96306125+dagardner-nv@users.noreply.github.com> --- docs/about-nemo-fabric/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index 7fc85ecaa..22bf540c2 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -11,7 +11,7 @@ SPDX-License-Identifier: Apache-2.0 */} 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, Codex SDK, or a custom adapter. +selected harness is Hermes Agent, 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, and returns From 6eca87718ef7fa9bb05ae796b1ad408f27928e53 Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 14:39:31 -0700 Subject: [PATCH 6/7] docs: add interface table lead-in and align harness names - Add an introductory sentence before the Choose Your Interface table - Align the Core Workflow diagram to use "Hermes Agent" and "Codex", matching the overview intro Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/overview.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index 22bf540c2..57c364598 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -76,6 +76,9 @@ committed JSON Schemas to validate packages and build language bindings. ## 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/client) | @@ -102,7 +105,7 @@ NeMo Fabric Rust core | | resolved adapter contract v -Hermes | Codex SDK | custom harness +Hermes Agent | Codex | custom harness | v RunResult + artifacts + events + telemetry references From 9000936fcac8d28a75b98a28b41ebf78c3fe2967 Mon Sep 17 00:00:00 2001 From: Linette Tang Date: Fri, 17 Jul 2026 15:27:08 -0700 Subject: [PATCH 7/7] docs: link Hermes Agent and Codex harnesses in overview intro Co-Authored-By: Claude Opus 4.8 Signed-off-by: Linette Tang --- docs/about-nemo-fabric/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about-nemo-fabric/overview.mdx b/docs/about-nemo-fabric/overview.mdx index 57c364598..a7a4c0ae4 100644 --- a/docs/about-nemo-fabric/overview.mdx +++ b/docs/about-nemo-fabric/overview.mdx @@ -11,7 +11,7 @@ SPDX-License-Identifier: Apache-2.0 */} 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. +selected harness is [Hermes Agent](https://hermes-agent.nousresearch.com/docs/), [Codex](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, and returns