NeMo Relay CLI
A transparent wrapper for Claude Code and Codex: a local gateway records run events and trajectories without changing the agent.
- 234 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The gateway sits between the agent and the model provider and writes the session record to disk.
- A persistent install adds hooks to Codex or Claude Code.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/nemo-relayDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The gateway sits between the agent and the model provider and writes the session record to disk.
- A persistent install adds hooks to Codex or Claude Code.
This is third-party code. Review the repository files before installing.
What it does
NVIDIA NeMo Relay is a shared runtime for observing and controlling agent runs: scopes, lifecycle events, and middleware on tool and model calls. The `nemo-relay` CLI launches Codex or Claude Code through a local gateway. The commands `nemo-relay claude -- "..."` and `nemo-relay codex -- exec "..."` start the gateway for the session and inject hooks and provider settings only for the launched process, then stop the gateway when the agent exits. Raw ATOF events in JSONL and ATIF trajectories land on disk; the same data can go out as OpenTelemetry traces, logs and metrics. The repository ships user skills in `skills/` (install, first run, call instrumentation, integration debugging) and a Claude Code plugin.
Who it is for. Agent builders and teams that need a record of real Claude Code and Codex sessions for debugging and evaluation.
Good fit when
- You want to see which tool and model calls Codex made during a session.
- Claude Code session trajectories feed quality evaluation in ATIF format.
- Agent telemetry goes to an OpenTelemetry stack.
- An agent works out how to attach Relay to an application using the `nemo-relay-get-started` skill.
Not a fit when
- You only need a terminal recording without events split per call.
- Sessions run in the Claude app, web or Claude Desktop: only Claude Code is supported.
- Session records must not be stored on disk.
Example request
Run Claude Code through nemo-relay with local ATOF and ATIF export and show which files appeared.Limitations
The Claude Code plugin requires Claude Code 2.1.121 or newer. A persistent Codex install trusts only the hooks of the `nemo-relay-plugin@nemo-relay-local` plugin; restart the Codex app afterwards. On Windows a restrictive host Job Object can tie the gateway to the host process lifetime. Event and trajectory files describe the real session, so review them before sharing.
How to disable. Stop launching the agent through `nemo-relay`; for a persistent install remove the plugin in Codex or Claude Code. A script-installed CLI is removed following the documentation.
FAQ
How do I record a Claude Code session?
Enable ATOF and ATIF output in `nemo-relay plugins edit` and run `nemo-relay claude -- "..."`. After the agent exits, events are in `.nemo-relay/atof` and trajectories in `.nemo-relay/atif` when you set those directories.
How does ATOF differ from ATIF?
ATOF is the raw stream of events Relay actually captured. ATIF is a normalized trajectory for analysis and evaluation; start by checking ATOF.
Do I need Relay separately for Hermes Agent?
No. NeMo Relay is built into Hermes Agent, so no separate observability plugin or CLI setup is required.
Which languages does the runtime support?
Python and Node.js install through `uv add nemo-relay` and `npm install`, and Rust crates exist. This is a separate path for applications that call models and tools themselves.
Which skills does the repository contain?
`skills/` holds user skills including `nemo-relay-install`, `nemo-relay-get-started`, `nemo-relay-instrument-calls`, `nemo-relay-integrate-upstream`, `nemo-relay-plugin-observability` and `nemo-relay-debug-runtime-integration`.
Discussion
No questions or reviews yet.
Related
CLI toolsOpenTelemetry-based CLI tracing for Claude Code, Cursor and Codex sessions, showing what the agent actually did and what it cost
The official Coralogix CLI with 19 skills: an agent reads production logs, traces and metrics and triages incidents
A local dashboard for Claude Code and Codex sessions: who is working, who waits for you, plus a 3D aquarium and Stream Deck
A self-hosted control center for coding agents: Claude Code, Codex, Copilot, OpenCode and Pi from your phone, desktop and terminal
A CLI and Kubernetes operator that runs Claude Code, Codex, Gemini, OpenCode and Cursor as tasks and sessions inside a cluster
A local dashboard for Claude Code, Codex CLI, Gemini CLI, Copilot and OpenCode that shows tokens, cost, latency and errors
README in short
Relay is a shared layer for coding agents, applications, frameworks and observability backends. Integrations exist for Codex, Claude Code, LangChain, LangGraph, Deep Agents, Google ADK and OpenClaw; Hermes Agent has built-in support.