Skip to content

v0.5.0

Choose a tag to compare

@AjayThorve AjayThorve released this 15 Oct 17:25
· 101 commits to main since this release
v0.5.0
5574117

NVIDIA NeMo Fabric 0.5.0

NeMo Fabric 0.5.0 adds OpenShell sandbox execution, three new harness adapters, and a lightweight adapter catalog that lays the groundwork for a future adapter registry.

At a Glance

New

  • OpenShell sandbox execution: Enables callers like NeMoClaw to run any Fabric-supported agent in an OpenShell sandbox. A persistent Fabric runtime server and fabric-agent-ctl provide start, invoke, and stop operations across separate sandbox exec calls.
  • Expanding harness support: Added adapters for Factory Droid, OpenHands, and Kilo Code as part of an ongoing rollout of additional harness integrations.
  • Adapter catalog: Inspect bundled adapter and target descriptor snapshots without installing harness SDKs. This is a foundation for a future adapter registry.

Changed

  • Harbor 0.23 integration improves outcome propagation, usage accounting, and finalized trajectory collection. These changes prepare FabricAgent for upstream integration into the Harbor Framework (PR #3528).
  • Pi moves to its 1.0 SDK and adds native MCP support.
  • Relay integrations support NeMo Relay 0.10.
  • Conversation-level Relay correlation groups supported adapter invocations under one session while retaining separate trajectories.
  • Detailed token usage preserves cache, reasoning, peak-request, and per-model accounting when reported by adapters.
  • environment.env_names forwards process variables by name without retaining their values in core configurations and run plans.
  • Claude and Codex honor configured invocation timeouts.

Breaking Changes

  • Relay observability: Explicit v3 configurations are rejected. Set the observability component's version to 4; keep the outer plugin version at 1. Migration details
  • Relay OTLP export: Endpoint environment variables can now enable automatic export, including prompt/response content in automatic traces. Review endpoint and header settings. Migration details
  • Rust callers: Update explicit struct literals for new request, environment, deadline, and usage fields, or use supported constructors/defaults. Migration details

Learn More

New Contributors