NVIDIA/NeMo-Relay

Adaptive Tuning configures NeMo Relay’s adaptive plugin to adjust telemetry, state, hints, tool parallelism, and rollout behavior from runtime signals. Use it after baseline instrumentation when you want to evaluate measured changes against known traffic.

Add Binding Feature adds or changes a public NeMo Relay API across the Rust core, FFI, and language bindings. Use it when a change must stay in parity across surfaces and needs coordinated validation.

Add Middleware adds a new guardrail or intercept type to the NeMo Relay middleware pipeline. Use it when introducing a new registration surface or a middleware behavior at a new pipeline stage.

Context Isolation helps keep NeMo Relay scope stacks separate across concurrent requests, async tasks, threads, workers, and agents. Use it when you need correct ancestry propagation and request-local middleware boundaries.

Contribute API helps add or change a public NeMo Relay API with binding parity, validation, and docs in mind. Use it when a runtime or binding surface changes and you need to keep affected bindings aligned.

Contribute Docs Or Examples guides docs-only or example-heavy changes that match NeMo Relay’s public API and docs structure. Use it when updating user-facing docs, examples, or entry-point paths without changing implementation behavior.

Debug Runtime Integration helps identify why NeMo Relay loads but runtime behavior is missing or incorrect, including scope, event, plugin, and export wiring issues. Use it when integration works partially but the expected callbacks or telemetry do not appear.

Draft Release Notes compares release branches and uses verified repository evidence to update the documentation-site release notes. Use it when preparing release summaries, checking changes between releases, or updating the current release pages.

Dynamic Plugins covers NeMo Relay’s native and worker plugin loaders, manifests, SDKs, and protocol boundaries. Use it when maintaining plugin compatibility, lifecycle behavior, tests, or release workflows.

Framework Integration Contribution guides adding or updating a third-party framework or plugin integration for NeMo Relay. Use it when wiring Relay into public APIs for frameworks like LangChain or LangGraph while preserving default behavior when Relay is absent.

Karpathy Guidelines reduce common LLM coding mistakes when writing, reviewing, or refactoring code. It encourages explicit assumptions, minimal changes, and verifiable success criteria.

Maintain Adaptive Surfaces keeps NeMo Relay’s adaptive config, plugin lifecycle, bindings, and docs aligned. Use it when changing the canonical adaptive model or when users still say optimizer.

Maintain CI reviews and updates GitHub Actions workflows for NeMo Relay. Use it when changing `.github/workflows` to enforce permissions, pin actions, validate caching, and check reusable workflow boundaries.

Maintain Observability keeps NeMo Relay event fields, exporter behavior, and binding config aligned across ATIF and typed OpenTelemetry projections. Use it when changing observability lifecycle, endpoint handling, or docs for subscriber/exporter behavior.

Maintain Packaging keeps NeMo Relay's package metadata, module paths, generated artifacts, and release-facing build surfaces consistent. Use it when changes affect how the project is built, packaged, named, or consumed outside the source tree.

NeMo Relay Get Started helps first-time users pick the simplest supported way to try Relay and confirm initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation. It is used before production setup to verify the attachment boundary and first observable events.

NeMo Relay Install guides installing NeMo Relay for the CLI, language packages, or maintained framework integrations. Use it when choosing an install path or checking basic availability after installation.

NeMo Relay Instrument Calls wraps existing tool and LLM/provider calls with Relay scopes and managed execution APIs. Use it when an app needs lifecycle events, middleware, guardrails, or metadata without changing the callable’s business logic.

NeMo Relay Integration helps assess, implement, or qualify Relay support in an agent harness or framework. It maps host boundaries to Relay attachment methods and verifies coverage for tools, model calls, subagents, and lifecycle events.

NeMo Relay Migration converts NeMo Flow code, docs, configs, and examples to NeMo Relay with mechanical renames and language-specific cleanup. Use it when updating Python, Rust, Node.js, Go, C FFI, CLI, or observability surfaces.

NeMo Relay Observability configures Relay 0.6 or 0.7 observability with the built-in plugin, subscribers, and exporters. Use it to capture ATOF, ATIF, OpenTelemetry, OpenInference, or custom event streams.

NeMo Relay Plugin Build packages reusable Relay runtime behavior as embedded components or manifest-backed native and worker plugins. Use it when you need deterministic config validation and rollback-safe registration for shared behavior.

NeMo Relay Typed Wrappers adds typed value and provider codecs for NeMo Relay integrations. Use it when you want stronger domain models while preserving JSON middleware semantics and caller-visible behavior.

Prepare Code Freeze creates a NeMo Relay release branch, updates nightly alpha branch config, bumps main to the next version, and opens the required PR. Use it when starting or automating a code freeze.

Prepare PR formats NeMo Relay pull requests with the repository template, conventional titles, and required validation notes. Use it when creating or updating a PR body and before opening a contributor change.