NVIDIA NeMo Relay CLI

About

View as Markdown

Use this section when you want the nemo-relay binary to observe local coding agent sessions through hooks, a passthrough LLM gateway, and NVIDIA NeMo Relay observability exporters.

Install the NeMo Relay CLI with the curl-based installer described in Installation. The installer provides the nemo-relay binary without requiring a Rust toolchain. The CLI can run supported coding agents through a managed local gateway, forward agent hook payloads into NeMo Relay lifecycle events, route OpenAI-compatible or Anthropic-compatible model traffic through the gateway, and diagnose local configuration. The nemo-relay-cli Cargo package remains available for source-based installation and unsupported platforms.

Persistent integrations use one lifecycle path:

Codex / Claude Code / Hermes Agent → nemo-relay mcp → shared Relay gateway

The host-specific layer installs and emits canonical lifecycle hooks. The MCP process is host-neutral and keeps the shared user-level gateway available.

Start Here When

Use these guides when you need to:

  • Observe Claude Code, Codex, or Hermes Agent sessions locally.
  • Configure coding-agent hooks for NeMo Relay lifecycle events.
  • Route model-provider traffic through the local NeMo Relay gateway.
  • Install persistent Claude Code, Codex, or Hermes Agent integrations without wrapping the agent command.
  • Validate and install model pricing catalog sources for local cost estimates.
  • Export local sessions to Agent Trajectory Interchange Format (ATIF), Agent Trajectory Observability Format (ATOF) JSONL, OpenTelemetry, or OpenInference.
  • Diagnose hook loading, gateway routing, and exporter output.

If you are instrumenting an application or framework directly, use Instrument Applications or Integrate into Frameworks instead.

Agent Harness Support

The NeMo Relay CLI is a supported surface for local coding-agent observability and hook-backed security. Optimization remains partial and host-dependent because each agent exposes different hooks, provider routes, and execution controls.

AgentObservabilitySecurityOptimizationNotes
Claude CodeYesYesPartialPre-tool hook responses are supported. LLM optimization uses gateway-routed traffic; full coverage depends on loaded Claude Code hooks.
CodexYesYesPartialPersistent install verifies all 10 hooks in the supported schema. Each Stop finalizes a turn snapshot because the plugin schema does not expose SessionEnd.
Hermes AgentYesYesPartialUser config installs the shared native MCP gateway lifecycle plus exact trusted hooks. Optimization depends on Hermes shell and API-request hook coverage.

Guides

Use these guide links to move from CLI setup into agent-specific instructions.

  • Basic Usage explains gateway routes, transparent runs, shared configuration, hook forwarding, and runtime mapping.
  • Coding Agent Installation covers persistent Claude Code, Codex, and Hermes Agent setup.
  • Claude Code covers transparent Claude Code runs, Anthropic gateway routing, ATIF verification, and unsupported Claude application modes.
  • Codex covers transparent Codex CLI runs, local GUI/app caveats, model provider routing, and remote-task limits.
  • Hermes Agent covers Hermes MCP lifecycle setup, exact hook trust, provider routing, and session-finalize behavior.

Start with Basic Usage, then use the guide for the coding agent that you want to observe.