Reference

Support Matrix

View as Markdown

This matrix describes the support scope for the current NVIDIA NeMo Relay release. It distinguishes published, prebuilt release artifacts from components that you build and package for the host yourself. CI coverage indicates where the repository runs validation; it does not by itself create a separate support commitment. For release-specific changes and known limitations, refer to Release Notes.

Platforms and Architectures

SurfaceLinux x86_64Linux ARM64macOS x86_64macOS ARM64Windows x86_64Windows ARM64Limitations
Core LibraryRequired CI coverageRequired CI coverageNot in the current CI matrixRequired CI coverageNon-blocking CI coverageNon-blocking CI coverageRust is the source of truth. Python and Node.js packages require their supported runtimes; Go and raw C FFI remain experimental and source-first.
CLI ApplicationPublished x86_64-unknown-linux-musl assetPublished aarch64-unknown-linux-musl assetNo published release assetPublished aarch64-apple-darwin assetPublished x86_64-pc-windows-msvc assetPublished aarch64-pc-windows-msvc assetIntel macOS has no prebuilt CLI asset. Use a source install on unsupported platforms.
Native PluginsBuild for the host ABIBuild for the host ABIBuild and validate locallyBuild for the host ABIBuild for the host ABI; CI is non-blockingBuild for the host ABI; CI is non-blockingNative plugins run in-process and are not sandboxed. Rebuild for the host ABI and compatible Relay version.
gRPC Worker PluginsDepends on the selected worker runtimeDepends on the selected worker runtimeBuild and validate locallyDepends on the selected worker runtimeDepends on the selected worker runtimeDepends on the selected worker runtimeWorkers run as local child processes over grpc-v1, not as a security sandbox. Python workers are unsupported on Windows ARM64. Refer to the worker runtime matrix for runtime-specific requirements.

Linux Distribution Notes

The published Linux CLI binaries use musl targets and are not tied to a distribution-specific package manager. Linux CI uses Ubuntu runners. NeMo Relay does not publish distribution-specific DEB or RPM packages or certify individual Ubuntu, Debian, RHEL-compatible, or Fedora releases. On an unsupported CPU, unsupported operating system, or a system whose local requirements prevent the release asset from running, install from source with Cargo.

Worker Runtime Compatibility

gRPC worker plugins run as local processes. Package and test each worker for its Relay host platform. This matrix does not make a compatibility claim for emulated or cross-architecture worker execution.

Worker runtimeLinux x86_64Linux ARM64macOS x86_64macOS ARM64Windows x86_64Windows ARM64Requirements and limitations
PythonWorker E2E CI coverageNot separately worker E2E validatedBuild and validate locallyWorker E2E CI coverageWorker E2E CI coverage; CI is non-blockingUnsupported: no usable grpcio wheelUse runtime = "python", a module:function entrypoint, and source.manifest_root. nemo-relay plugins add creates and retains the managed Python environment. Package dependencies for the target host.
RustHost-compatible executable; core CI coverageHost-compatible executable; core CI coverageBuild and validate locallyHost-compatible executable; core CI coverageHost-compatible executable; core CI is non-blockingHost-compatible executable; core CI is non-blockingUse runtime = "rust" and provide an executable that implements grpc-v1.
CommandHost-compatible executable; core CI coverageHost-compatible executable; core CI coverageBuild and validate locallyHost-compatible executable; core CI coverageHost-compatible executable; core CI is non-blockingHost-compatible executable; core CI is non-blockingUse runtime = "command" for another local executable that implements grpc-v1. Its runtime, dependencies, and compatibility are the operator’s responsibility.

The process boundary isolates crashes and dependencies, but it is not a security sandbox. Refer to gRPC Worker Plugin Concepts for manifests, lifecycle, and trust requirements.

Coding Agents Supported by the CLI

The CLI supports local coding-agent sessions where agent hooks and provider traffic can reach the local Relay gateway. It rejects prerelease, malformed, and older CLI versions during installation, diagnostics, and transparent runs.

AgentMinimum versionSupported CLI capabilitiesCurrent limitations
Claude Code2.1.121Persistent install, transparent run, lifecycle hooks, local gateway routing, and pre-tool securityClaude desktop, web, and application sessions are unsupported unless they expose the same local hook and gateway controls. Optimization requires gateway-routed LLM traffic and available hooks.
Codex CLI0.143.0Persistent install, transparent run, 10 supported plugin hooks, local gateway routing, and pre-tool securityCloud or remote tasks that bypass the local machine have partial or no LLM capture. The plugin hook schema has no SessionEnd; Relay finalizes the cumulative session snapshot at Stop. Encrypted Codex multi-agent v2 payloads cannot be decrypted or reliably linked.
Hermes Agent0.18.2Persistent MCP integration, transparent run, lifecycle hooks, local gateway routing, and pre-tool securityOptimization depends on Hermes shell and API-request hook coverage. Hook-observed and gateway-observed LLM spans can both be present when both paths are enabled.

For installation, diagnostics, and host-specific behavior, refer to Coding Agent Installation, Claude Code, Codex, and Hermes Agent.

Framework and Agent Harness Integrations

IntegrationObservabilitySecurityOptimizationNotes
LangChainYesYesYesWrapped tool and LLM calling.
LangGraphYesYesYesWrapped tool and LLM calling.
Deep AgentsYesYesYesWrapped tool and LLM calling.
OpenClawYesPartialNoPublic hook-backed telemetry with pre-tool guardrails. Public hooks do not expose managed execution rewrites.

Install the maintained Python integrations with the langchain, langgraph, and deepagents extras. Install the OpenClaw integration as the nemo-relay-openclaw plugin. Refer to Supported Integrations for setup and guide links.