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

# About

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.

The NeMo Relay CLI is installed by the `nemo-relay-cli` Cargo package. It 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.

## Start Here When

Use these guides when you need to:

* Observe Claude Code, Codex, Cursor, 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 or Codex host plugins 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](/instrument-applications/about) or
[Integrate into Frameworks](/integrate-into-frameworks/about) 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.

| Agent        | Observability | Security | Optimization | Notes                                                                                                                                                        |
| ------------ | ------------- | -------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Claude Code  | Yes           | Yes      | Partial      | Pre-tool hook responses are supported. LLM optimization uses gateway-routed traffic; full coverage depends on loaded Claude Code hooks.                      |
| Codex        | Yes           | Yes      | Partial      | Hook forwarding and gateway-routed LLM optimization are supported after hooks are reviewed and activated. The missing session-end hook limits full coverage. |
| Hermes Agent | Yes           | Yes      | Partial      | Hook forwarding, pre-tool guardrails, and Hermes API-request telemetry are supported. Optimization depends on Hermes shell and API-request hook coverage.    |
| Cursor       | Partial       | Limited  | No           | Hook forwarding is supported. Gateway observability is limited. Missing hooks under `cursor-agent` limit full feature coverage.                              |

## Guides

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

* [Basic Usage](/nemo-relay-cli/basic-usage) explains gateway routes, transparent runs,
  shared configuration, hook forwarding, and runtime mapping.
* [Plugin Installation](/nemo-relay-cli/plugin-installation) covers persistent
  Claude Code and Codex plugin setup through host marketplaces.
* [Claude Code](/nemo-relay-cli/claude-code) covers transparent Claude Code
  runs, Anthropic gateway routing, ATIF verification, and unsupported Claude
  application modes.
* [Codex](/nemo-relay-cli/codex) covers transparent Codex CLI runs, local
  GUI/app caveats, model provider routing, and remote-task limits.
* [Cursor](/nemo-relay-cli/cursor) covers transparent Cursor runs, temporary
  hook patching, GUI and CLI smoke tests, and gateway routing limits.
* [Hermes Agent](/nemo-relay-cli/hermes) covers Hermes shell hook installation,
  dynamic gateway URL handling, session-finalize behavior, and hook consent
  caveats.

Start with [Basic Usage](/nemo-relay-cli/basic-usage), then use the guide for the coding
agent that you want to observe.