NEMO RELAY ADDS EXPERIMENTAL CURSOR HOOKS FOR AGENT OBSERVABILITY (MANUAL MODEL ROUTING REQUIRED)
NVIDIA NeMo Relay can now observe Cursor agent lifecycle events via experimental hooks and a local wrapper, but LLM traffic routing remains manual. NVIDIA’s be...
NVIDIA NeMo Relay can now observe Cursor agent lifecycle events via experimental hooks and a local wrapper, but LLM traffic routing remains manual.
NVIDIA’s beta docs describe a Cursor integration that installs or temporarily patches hooks so you can see agent, subagent, tool, shell, MCP, file, and response lifecycle events, with caveats around subagents and model routing that may bypass the gateway if not configured docs.
A "Transparent Run" wrapper (nemo-relay cursor) starts a local gateway and merges hook entries into .cursor/hooks.json, then restores them after exit. CLI support differs: it needs "version": 1 and direct commands; headless builds emit fewer events docs.
Separate thread: a Cursor forum bug shows model selection snapping from Opus 4.8 back to Composer 2.5, which could skew routing tests forum.
Gives teams a path to observe Cursor agent lifecycles locally without invasive setup.
Full LLM trace coverage hinges on provider/proxy routing, surfacing gaps in current Cursor configurations.
-
terminal
Run
nemo-relay cursor -- agent --resume <session-id>and confirm agent/subagent/tool events show up; then enable provider/proxy routing and verify LLM request/response events appear. -
terminal
For CLI, set
.cursor/hooks.jsonto"version": 1with direct commands, runcursor-agent, and compare event coverage vs IDE; treat missing events as CLI limitations.
Legacy codebase integration strategies...
- 01.
Add NeMo Relay as a gateway and patch hooks in existing Cursor projects; audit subagents that might bypass the gateway.
- 02.
Freeze Cursor versions while testing; the model selection bug may affect routing and metrics consistency.
Fresh architecture paradigms...
- 01.
Standardize on NeMo Relay for Cursor from day one: define provider/proxy routing, logging schema, and retention.
- 02.
Use the wrapper for no-install trials, then codify
.cursor/hooks.jsonand gateway config in repo templates.
Get daily NVIDIA + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday