> This page is for NeMo Fabric, version v0.3.0.
> For other versions, use one of these documentation indexes:
> - Latest (v0.4.0) (default): https://docs.nvidia.com/nemo/fabric/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/fabric/dev/llms.txt
> - v0.5.0: https://docs.nvidia.com/nemo/fabric/v0.5.0/llms.txt
> - v0.4.0: https://docs.nvidia.com/nemo/fabric/v0.4.0/llms.txt
> - v0.3.0: https://docs.nvidia.com/nemo/fabric/v0.3.0/llms.txt
> - v0.2.0: https://docs.nvidia.com/nemo/fabric/v0.2.0/llms.txt
> - v0.1.1: https://docs.nvidia.com/nemo/fabric/v0.1.1/llms.txt
> - v0.1.0: https://docs.nvidia.com/nemo/fabric/v0.1.0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/fabric/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/fabric/_mcp/server.

# Release Notes

> Review the current NVIDIA NeMo Fabric release status and find the official release history.

This page summarizes the current documentation-visible release state. GitHub
Releases remain the source of truth for complete release history and
tag-specific notes.

## Current Release

NVIDIA NeMo Fabric 0.3 adds packaged integrations for
[Pi](https://pi.dev/docs/latest), remote HTTP agents, and
[NVIDIA-labs Object Oriented Agents (NOOA)](https://github.com/nvidia-nemo/labs-OO-Agents).
It also expands [NVIDIA NeMo Relay](https://docs.nvidia.com/nemo/relay/about-nemo-relay/overview)
streaming with a standalone collector, explicit request correlation, and
additional adapter telemetry.

For release artifacts and the complete PR-by-PR history, refer to
[GitHub Releases](https://github.com/NVIDIA/NeMo-Fabric/releases).

## Release Highlights

### New Harness Integrations

The [Pi adapter](/nemo/fabric/v0.3.0/integrations/harness-integrations/pi) runs the Pi SDK in a persistent
Node.js process and is distributed as `nemo-fabric-adapters-pi` on npm. It maps
normalized models, replacement system instructions, tool policy, custom tool
modules, skills, and explicit local extensions into one in-memory Pi session.
Pi requires Node.js 22.19.0 or newer.

The [Remote Agent adapter](/nemo/fabric/v0.3.0/integrations/harness-integrations/remote-agent) invokes an
independently deployed service through OpenAI Responses, OpenAI Chat
Completions, or Anthropic Messages-compatible HTTP APIs. It retains the
completed user and assistant transcript across ordered invocations in one
runtime and can consume correlated records in Agent Trajectory Observability Format (ATOF)
from a collector shared with the
remote deployment.

The packaged
[NOOA adapter](https://github.com/NVIDIA/NeMo-Fabric/tree/v0.3.0/adapters/python/nooa)
integrates [NVIDIA-labs Object Oriented Agents (NOOA)](https://github.com/nvidia-nemo/labs-OO-Agents)
and supports shared `InteractiveAgent` targets and dedicated `BenchAgent` tasks,
including CodingAgent, ARC Solver, and Harbor evaluation workflows. The package
supports Python 3.12 and 3.13.

### Collector-Backed Relay Streaming

The new `nemo-fabric-collector` package receives ATOF over HTTP, routes records
to per-request queues, and supports multiple Fabric runtimes when request IDs
are unique. Install `nemo-fabric[streaming]` to use the default embedded
collector. Applications can instead set `launch_collector=False` and connect
to an externally managed collector.

Relay-enabled in-process adapters propagate UUID request IDs into Relay scope
context and preserve other request IDs as metadata. mini-SWE-agent now emits
agent, function, model, and tool telemetry for live ATOF streaming and ATIF,
OpenTelemetry, and OpenInference outputs.

For collector setup, correlation behavior, backpressure limits, and stream
lifecycle requirements, refer to the
[Python SDK guide](/nemo/fabric/v0.3.0/sdk/python-sdk#nemo-relay-streaming).

### Explicit System Instruction Modes

The normalized contract now distinguishes `replace` and `append` system
instruction modes. `replace` remains the default. Adapter descriptors declare
the modes they support, and planning rejects unsupported modes before adapter
startup. Claude supports both modes; the other bundled adapters support
`replace` only.

NeMo Agent Toolkit configurations that set `instructions.system` must now set
`mode="append"`, because that adapter maps the value to additive instructions
and cannot implement replacement semantics.

## Current Limitations

The current release has the following limitations:

* Provider-backed third-party adapter registries are not included.
* The automated adapter conformance suite is not included. Adapter authors can
  use the maintained verification checklist for the required profile and
  declared capabilities.
* Cancellation, live updates, and service lifecycle flags are reserved until a
  runtime binding exposes and tests the corresponding adapter operations.
* The Remote Agent adapter does not normalize remote MCP, skills, tool policy,
  or subagent configuration. The remote service owns those capabilities and
  its lifecycle. Relay streaming requires an independently instrumented remote
  service and a collector reachable by both the service and Fabric.
* The Pi adapter does not expose Relay, MCP, native streaming, caller-driven
  cancellation, or remote-service execution.