[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-nemo-relay-install":3,"mdc-p0zu4b-key":58,"related-org-nvidia-nemo-relay-install":590,"related-repo-nvidia-nemo-relay-install":747},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":29,"repoUrl":30,"updatedAt":31,"license":32,"forks":33,"topics":34,"repo":53,"sourceUrl":56,"mdContent":57},"nemo-relay-install","install NeMo Relay for various environments","Use this skill when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or quick-start setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"nvidia","NVIDIA","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fnvidia.png",[12,16,19,20,23,26],{"name":13,"slug":14,"type":15},"CLI","cli","tag",{"name":17,"slug":18,"type":15},"Deployment","deployment",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Python","python",{"name":24,"slug":25,"type":15},"Rust","rust",{"name":27,"slug":28,"type":15},"Node.js","nodejs",75,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Relay","2026-07-17T05:30:31.443244","Apache-2.0",41,[35,36,37,38,39,40,41,42,43,44,45,8,46,47,48,49,50,51,52],"agents","ai","atif","atof","claude-code","codex","deepagents","hermes-agent","langchain","langgraph","middleware","observability","openclaw","openinference","optimization","otel","runtime","security",{"repoUrl":30,"stars":29,"forks":33,"topics":54,"description":55},[35,36,37,38,39,40,41,42,43,44,45,8,46,47,48,49,50,51,52],"Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Relay\u002Ftree\u002FHEAD\u002Fskills\u002Fnemo-relay-install","---\nname: nemo-relay-install\ndescription: Use this skill when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, Hermes, or maintained framework integrations before runtime configuration or quick-start setup.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Corporation and Affiliates\n---\n\n# Install NeMo Relay\n\nChoose the package or executable from the user's desired outcome. Stop after\ninstallation and basic availability checks. Do not configure runtime behavior,\nwrite `plugins.toml`, create scopes, register middleware, or build a first app\nexample from this skill.\nKeep installation separate from first-use instrumentation.\n\n## Choose The Install Path\n\nIf the user asks to install NeMo Relay but does not identify a target or\ndesired outcome, ask one short clarifying question before giving commands:\n\n> Which install path do you want: CLI for coding-agent\u002Flocal gateway use,\n> language package for a Python\u002FNode.js\u002FRust app, or framework integration for\n> LangChain, LangGraph, Deep Agents, OpenClaw, or Hermes?\n\nDo not ask when the user already names a CLI, language, framework, harness,\nsource checkout, or target project file such as `pyproject.toml`, `package.json`,\nor `Cargo.toml`.\n\nUse this order from least to most application-specific:\n\n1. **CLI** for a generic \"try Relay\" request, a temporary coding-agent run, the\n   local gateway, or explicit persistent host-plugin setup. Read\n   [CLI Installation](references\u002Fcli-install.md).\n2. **Maintained integration** when the user already uses OpenClaw, Hermes,\n   LangChain, LangGraph, or Deep Agents. Read\n   [Maintained Integration Installation](references\u002Fmaintained-integrations.md).\n3. **Language package** when a Python, Node.js, or Rust application directly\n   owns its tool or model call sites. Read\n   [Language Package Installation](references\u002Flanguage-packages.md).\n4. **Source checkout** only for contributors or unpublished changes. Follow the\n   repository development guide instead of published package commands.\n\nFor \"try Relay\" requests, default to the CLI and temporary transparent run.\nDo not make persistent host-plugin installation the default.\n\n## Protect Codex Desktop Continuity\n\nBefore persistent Codex installation, determine whether the user is operating\nfrom Codex Desktop. Persistent `nemo-relay install codex` changes the active\nCodex provider and can make the current or older Desktop threads appear missing\nafter restart because of an upstream provider-filtering bug. The threads are\nnot deleted.\n\nFor Codex Desktop users:\n\n1. Recommend temporary transparent run first.\n2. If the user still wants persistent installation, read the Codex Desktop\n   section in [CLI Installation](references\u002Fcli-install.md).\n3. Preview the install and proposed recovery-note location.\n4. Obtain confirmation before writing either the recovery note or global Codex\n   configuration.\n5. Render `assets\u002Fcodex-desktop-recovery.md` as\n   `NEMO_RELAY_CODEX_DESKTOP_RECOVERY.md` in the user's workspace root before\n   running the persistent installer.\n6. Do not restart Codex Desktop until the user has the recovery-file path.\n\nDo not directly inspect, copy, delete, edit, or rewrite Codex session files,\nprivate application configuration, or SQLite state to work around the\nvisibility bug. Supported `nemo-relay` install, uninstall, and doctor commands\nmay manage the Relay-generated provider and hook configuration.\n\n## Install And Verify\n\n1. Inspect the target manifest, environment, operating system, architecture,\n   and existing installation before changing anything.\n2. Load only the reference for the selected path.\n3. Preserve the project's existing package manager and virtual environment.\n4. Use the latest compatible release unless the user or project requires an\n   exact version.\n5. Show the exact install command before running a remote installer or changing\n   a project manifest.\n6. Run only the selected path's basic availability check.\n7. Report what was installed, where it was installed, and the verification\n   result. Then stop.\n\nThe primary documented language paths are Rust, Python, and Node.js. Treat Go\nand raw FFI as source-first advanced surfaces, not normal package installs.\nDo not treat a first scope, subscriber, gateway, plugin config, or LLM call as\ninstallation verification.\n\n## Use Doctor For CLI Readiness And Configuration Issues\n\nKnow about `nemo-relay doctor`, but use it in the right scope:\n\n- Run `nemo-relay doctor` when the user installed the CLI and reports config,\n  gateway, agent-readiness, plugin, exporter, or model-pricing issues.\n- Use `nemo-relay doctor --json` when structured output will help an agent\n  inspect checks programmatically.\n- Use `nemo-relay doctor --plugin claude-code`, `nemo-relay doctor --plugin\n  codex`, or `nemo-relay doctor --plugin all` only for persistent host-plugin\n  installations.\n- Do not require plugin doctor for transparent runs. Transparent-run setup does\n  not require persistent host-plugin state.\n- Do not use doctor as proof that a Python, Node.js, or Rust package dependency\n  was installed. Verify those with the language package manager\u002Fimport checks.\n\nWhen doctor reports failures, summarize the failed checks and the specific\nremediation it suggests. Do not loop back to reinstalling every package unless\nthe failed check points to a broken or missing install.\n\n## Hand Off After Install\n\nChoose the next workflow from the user's immediate outcome:\n\n- Use `nemo-relay-get-started` for a first working scope, tool call, LLM call,\n  or trial plugin setup.\n- Use the NeMo Relay CLI documentation or host-specific setup for a local CLI\n  host-plugin workflow, not application runtime setup.\n- Use the matching plugin or instrumentation skill for runtime configuration,\n  plugin files, observability, or adaptive behavior.\n\n## Common Mistakes\n\nAvoid these installation-scope mistakes:\n\n- Using repository development setup when the user only needs a published\n  package.\n- Installing the CLI when the user needs an application binding, or installing a\n  binding when the user only needs the local `nemo-relay` executable.\n- Treating persistent host-plugin installation as the default way to try Relay,\n  instead of starting with temporary transparent run.\n- Pinning old versions unless the user or project explicitly requires that\n  version.\n- Continuing into `plugins.toml`, middleware registration, scopes, or quick-start\n  examples before the install step has been verified.\n\n## Public Docs To Reference\n\nUse these public entry points to confirm current installation guidance:\n\n- [Installation](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Finstallation)\n- [Prerequisites](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Fprerequisites)\n- [CLI transparent run](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fnemo-relay-cli\u002Fbasic-usage#transparent-run)\n- [Configuration and setup handoff](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Fconfiguration)\n",{"data":59,"body":62},{"name":4,"description":6,"license":32,"metadata":60},{"author":61},"NVIDIA Corporation and Affiliates",{"type":63,"children":64},"root",[65,74,89,96,101,110,139,144,211,216,222,235,240,294,307,313,351,356,362,375,441,446,452,457,482,488,493,535,541,546],{"type":66,"tag":67,"props":68,"children":70},"element","h1",{"id":69},"install-nemo-relay",[71],{"type":72,"value":73},"text","Install NeMo Relay",{"type":66,"tag":75,"props":76,"children":77},"p",{},[78,80,87],{"type":72,"value":79},"Choose the package or executable from the user's desired outcome. Stop after\ninstallation and basic availability checks. Do not configure runtime behavior,\nwrite ",{"type":66,"tag":81,"props":82,"children":84},"code",{"className":83},[],[85],{"type":72,"value":86},"plugins.toml",{"type":72,"value":88},", create scopes, register middleware, or build a first app\nexample from this skill.\nKeep installation separate from first-use instrumentation.",{"type":66,"tag":90,"props":91,"children":93},"h2",{"id":92},"choose-the-install-path",[94],{"type":72,"value":95},"Choose The Install Path",{"type":66,"tag":75,"props":97,"children":98},{},[99],{"type":72,"value":100},"If the user asks to install NeMo Relay but does not identify a target or\ndesired outcome, ask one short clarifying question before giving commands:",{"type":66,"tag":102,"props":103,"children":104},"blockquote",{},[105],{"type":66,"tag":75,"props":106,"children":107},{},[108],{"type":72,"value":109},"Which install path do you want: CLI for coding-agent\u002Flocal gateway use,\nlanguage package for a Python\u002FNode.js\u002FRust app, or framework integration for\nLangChain, LangGraph, Deep Agents, OpenClaw, or Hermes?",{"type":66,"tag":75,"props":111,"children":112},{},[113,115,121,123,129,131,137],{"type":72,"value":114},"Do not ask when the user already names a CLI, language, framework, harness,\nsource checkout, or target project file such as ",{"type":66,"tag":81,"props":116,"children":118},{"className":117},[],[119],{"type":72,"value":120},"pyproject.toml",{"type":72,"value":122},", ",{"type":66,"tag":81,"props":124,"children":126},{"className":125},[],[127],{"type":72,"value":128},"package.json",{"type":72,"value":130},",\nor ",{"type":66,"tag":81,"props":132,"children":134},{"className":133},[],[135],{"type":72,"value":136},"Cargo.toml",{"type":72,"value":138},".",{"type":66,"tag":75,"props":140,"children":141},{},[142],{"type":72,"value":143},"Use this order from least to most application-specific:",{"type":66,"tag":145,"props":146,"children":147},"ol",{},[148,167,184,201],{"type":66,"tag":149,"props":150,"children":151},"li",{},[152,157,159,166],{"type":66,"tag":153,"props":154,"children":155},"strong",{},[156],{"type":72,"value":13},{"type":72,"value":158}," for a generic \"try Relay\" request, a temporary coding-agent run, the\nlocal gateway, or explicit persistent host-plugin setup. Read\n",{"type":66,"tag":160,"props":161,"children":163},"a",{"href":162},"references\u002Fcli-install.md",[164],{"type":72,"value":165},"CLI Installation",{"type":72,"value":138},{"type":66,"tag":149,"props":168,"children":169},{},[170,175,177,183],{"type":66,"tag":153,"props":171,"children":172},{},[173],{"type":72,"value":174},"Maintained integration",{"type":72,"value":176}," when the user already uses OpenClaw, Hermes,\nLangChain, LangGraph, or Deep Agents. Read\n",{"type":66,"tag":160,"props":178,"children":180},{"href":179},"references\u002Fmaintained-integrations.md",[181],{"type":72,"value":182},"Maintained Integration Installation",{"type":72,"value":138},{"type":66,"tag":149,"props":185,"children":186},{},[187,192,194,200],{"type":66,"tag":153,"props":188,"children":189},{},[190],{"type":72,"value":191},"Language package",{"type":72,"value":193}," when a Python, Node.js, or Rust application directly\nowns its tool or model call sites. Read\n",{"type":66,"tag":160,"props":195,"children":197},{"href":196},"references\u002Flanguage-packages.md",[198],{"type":72,"value":199},"Language Package Installation",{"type":72,"value":138},{"type":66,"tag":149,"props":202,"children":203},{},[204,209],{"type":66,"tag":153,"props":205,"children":206},{},[207],{"type":72,"value":208},"Source checkout",{"type":72,"value":210}," only for contributors or unpublished changes. Follow the\nrepository development guide instead of published package commands.",{"type":66,"tag":75,"props":212,"children":213},{},[214],{"type":72,"value":215},"For \"try Relay\" requests, default to the CLI and temporary transparent run.\nDo not make persistent host-plugin installation the default.",{"type":66,"tag":90,"props":217,"children":219},{"id":218},"protect-codex-desktop-continuity",[220],{"type":72,"value":221},"Protect Codex Desktop Continuity",{"type":66,"tag":75,"props":223,"children":224},{},[225,227,233],{"type":72,"value":226},"Before persistent Codex installation, determine whether the user is operating\nfrom Codex Desktop. Persistent ",{"type":66,"tag":81,"props":228,"children":230},{"className":229},[],[231],{"type":72,"value":232},"nemo-relay install codex",{"type":72,"value":234}," changes the active\nCodex provider and can make the current or older Desktop threads appear missing\nafter restart because of an upstream provider-filtering bug. The threads are\nnot deleted.",{"type":66,"tag":75,"props":236,"children":237},{},[238],{"type":72,"value":239},"For Codex Desktop users:",{"type":66,"tag":145,"props":241,"children":242},{},[243,248,258,263,268,289],{"type":66,"tag":149,"props":244,"children":245},{},[246],{"type":72,"value":247},"Recommend temporary transparent run first.",{"type":66,"tag":149,"props":249,"children":250},{},[251,253,257],{"type":72,"value":252},"If the user still wants persistent installation, read the Codex Desktop\nsection in ",{"type":66,"tag":160,"props":254,"children":255},{"href":162},[256],{"type":72,"value":165},{"type":72,"value":138},{"type":66,"tag":149,"props":259,"children":260},{},[261],{"type":72,"value":262},"Preview the install and proposed recovery-note location.",{"type":66,"tag":149,"props":264,"children":265},{},[266],{"type":72,"value":267},"Obtain confirmation before writing either the recovery note or global Codex\nconfiguration.",{"type":66,"tag":149,"props":269,"children":270},{},[271,273,279,281,287],{"type":72,"value":272},"Render ",{"type":66,"tag":81,"props":274,"children":276},{"className":275},[],[277],{"type":72,"value":278},"assets\u002Fcodex-desktop-recovery.md",{"type":72,"value":280}," as\n",{"type":66,"tag":81,"props":282,"children":284},{"className":283},[],[285],{"type":72,"value":286},"NEMO_RELAY_CODEX_DESKTOP_RECOVERY.md",{"type":72,"value":288}," in the user's workspace root before\nrunning the persistent installer.",{"type":66,"tag":149,"props":290,"children":291},{},[292],{"type":72,"value":293},"Do not restart Codex Desktop until the user has the recovery-file path.",{"type":66,"tag":75,"props":295,"children":296},{},[297,299,305],{"type":72,"value":298},"Do not directly inspect, copy, delete, edit, or rewrite Codex session files,\nprivate application configuration, or SQLite state to work around the\nvisibility bug. Supported ",{"type":66,"tag":81,"props":300,"children":302},{"className":301},[],[303],{"type":72,"value":304},"nemo-relay",{"type":72,"value":306}," install, uninstall, and doctor commands\nmay manage the Relay-generated provider and hook configuration.",{"type":66,"tag":90,"props":308,"children":310},{"id":309},"install-and-verify",[311],{"type":72,"value":312},"Install And Verify",{"type":66,"tag":145,"props":314,"children":315},{},[316,321,326,331,336,341,346],{"type":66,"tag":149,"props":317,"children":318},{},[319],{"type":72,"value":320},"Inspect the target manifest, environment, operating system, architecture,\nand existing installation before changing anything.",{"type":66,"tag":149,"props":322,"children":323},{},[324],{"type":72,"value":325},"Load only the reference for the selected path.",{"type":66,"tag":149,"props":327,"children":328},{},[329],{"type":72,"value":330},"Preserve the project's existing package manager and virtual environment.",{"type":66,"tag":149,"props":332,"children":333},{},[334],{"type":72,"value":335},"Use the latest compatible release unless the user or project requires an\nexact version.",{"type":66,"tag":149,"props":337,"children":338},{},[339],{"type":72,"value":340},"Show the exact install command before running a remote installer or changing\na project manifest.",{"type":66,"tag":149,"props":342,"children":343},{},[344],{"type":72,"value":345},"Run only the selected path's basic availability check.",{"type":66,"tag":149,"props":347,"children":348},{},[349],{"type":72,"value":350},"Report what was installed, where it was installed, and the verification\nresult. Then stop.",{"type":66,"tag":75,"props":352,"children":353},{},[354],{"type":72,"value":355},"The primary documented language paths are Rust, Python, and Node.js. Treat Go\nand raw FFI as source-first advanced surfaces, not normal package installs.\nDo not treat a first scope, subscriber, gateway, plugin config, or LLM call as\ninstallation verification.",{"type":66,"tag":90,"props":357,"children":359},{"id":358},"use-doctor-for-cli-readiness-and-configuration-issues",[360],{"type":72,"value":361},"Use Doctor For CLI Readiness And Configuration Issues",{"type":66,"tag":75,"props":363,"children":364},{},[365,367,373],{"type":72,"value":366},"Know about ",{"type":66,"tag":81,"props":368,"children":370},{"className":369},[],[371],{"type":72,"value":372},"nemo-relay doctor",{"type":72,"value":374},", but use it in the right scope:",{"type":66,"tag":376,"props":377,"children":378},"ul",{},[379,391,404,431,436],{"type":66,"tag":149,"props":380,"children":381},{},[382,384,389],{"type":72,"value":383},"Run ",{"type":66,"tag":81,"props":385,"children":387},{"className":386},[],[388],{"type":72,"value":372},{"type":72,"value":390}," when the user installed the CLI and reports config,\ngateway, agent-readiness, plugin, exporter, or model-pricing issues.",{"type":66,"tag":149,"props":392,"children":393},{},[394,396,402],{"type":72,"value":395},"Use ",{"type":66,"tag":81,"props":397,"children":399},{"className":398},[],[400],{"type":72,"value":401},"nemo-relay doctor --json",{"type":72,"value":403}," when structured output will help an agent\ninspect checks programmatically.",{"type":66,"tag":149,"props":405,"children":406},{},[407,408,414,415,421,423,429],{"type":72,"value":395},{"type":66,"tag":81,"props":409,"children":411},{"className":410},[],[412],{"type":72,"value":413},"nemo-relay doctor --plugin claude-code",{"type":72,"value":122},{"type":66,"tag":81,"props":416,"children":418},{"className":417},[],[419],{"type":72,"value":420},"nemo-relay doctor --plugin codex",{"type":72,"value":422},", or ",{"type":66,"tag":81,"props":424,"children":426},{"className":425},[],[427],{"type":72,"value":428},"nemo-relay doctor --plugin all",{"type":72,"value":430}," only for persistent host-plugin\ninstallations.",{"type":66,"tag":149,"props":432,"children":433},{},[434],{"type":72,"value":435},"Do not require plugin doctor for transparent runs. Transparent-run setup does\nnot require persistent host-plugin state.",{"type":66,"tag":149,"props":437,"children":438},{},[439],{"type":72,"value":440},"Do not use doctor as proof that a Python, Node.js, or Rust package dependency\nwas installed. Verify those with the language package manager\u002Fimport checks.",{"type":66,"tag":75,"props":442,"children":443},{},[444],{"type":72,"value":445},"When doctor reports failures, summarize the failed checks and the specific\nremediation it suggests. Do not loop back to reinstalling every package unless\nthe failed check points to a broken or missing install.",{"type":66,"tag":90,"props":447,"children":449},{"id":448},"hand-off-after-install",[450],{"type":72,"value":451},"Hand Off After Install",{"type":66,"tag":75,"props":453,"children":454},{},[455],{"type":72,"value":456},"Choose the next workflow from the user's immediate outcome:",{"type":66,"tag":376,"props":458,"children":459},{},[460,472,477],{"type":66,"tag":149,"props":461,"children":462},{},[463,464,470],{"type":72,"value":395},{"type":66,"tag":81,"props":465,"children":467},{"className":466},[],[468],{"type":72,"value":469},"nemo-relay-get-started",{"type":72,"value":471}," for a first working scope, tool call, LLM call,\nor trial plugin setup.",{"type":66,"tag":149,"props":473,"children":474},{},[475],{"type":72,"value":476},"Use the NeMo Relay CLI documentation or host-specific setup for a local CLI\nhost-plugin workflow, not application runtime setup.",{"type":66,"tag":149,"props":478,"children":479},{},[480],{"type":72,"value":481},"Use the matching plugin or instrumentation skill for runtime configuration,\nplugin files, observability, or adaptive behavior.",{"type":66,"tag":90,"props":483,"children":485},{"id":484},"common-mistakes",[486],{"type":72,"value":487},"Common Mistakes",{"type":66,"tag":75,"props":489,"children":490},{},[491],{"type":72,"value":492},"Avoid these installation-scope mistakes:",{"type":66,"tag":376,"props":494,"children":495},{},[496,501,513,518,523],{"type":66,"tag":149,"props":497,"children":498},{},[499],{"type":72,"value":500},"Using repository development setup when the user only needs a published\npackage.",{"type":66,"tag":149,"props":502,"children":503},{},[504,506,511],{"type":72,"value":505},"Installing the CLI when the user needs an application binding, or installing a\nbinding when the user only needs the local ",{"type":66,"tag":81,"props":507,"children":509},{"className":508},[],[510],{"type":72,"value":304},{"type":72,"value":512}," executable.",{"type":66,"tag":149,"props":514,"children":515},{},[516],{"type":72,"value":517},"Treating persistent host-plugin installation as the default way to try Relay,\ninstead of starting with temporary transparent run.",{"type":66,"tag":149,"props":519,"children":520},{},[521],{"type":72,"value":522},"Pinning old versions unless the user or project explicitly requires that\nversion.",{"type":66,"tag":149,"props":524,"children":525},{},[526,528,533],{"type":72,"value":527},"Continuing into ",{"type":66,"tag":81,"props":529,"children":531},{"className":530},[],[532],{"type":72,"value":86},{"type":72,"value":534},", middleware registration, scopes, or quick-start\nexamples before the install step has been verified.",{"type":66,"tag":90,"props":536,"children":538},{"id":537},"public-docs-to-reference",[539],{"type":72,"value":540},"Public Docs To Reference",{"type":66,"tag":75,"props":542,"children":543},{},[544],{"type":72,"value":545},"Use these public entry points to confirm current installation guidance:",{"type":66,"tag":376,"props":547,"children":548},{},[549,560,570,580],{"type":66,"tag":149,"props":550,"children":551},{},[552],{"type":66,"tag":160,"props":553,"children":557},{"href":554,"rel":555},"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Finstallation",[556],"nofollow",[558],{"type":72,"value":559},"Installation",{"type":66,"tag":149,"props":561,"children":562},{},[563],{"type":66,"tag":160,"props":564,"children":567},{"href":565,"rel":566},"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Fprerequisites",[556],[568],{"type":72,"value":569},"Prerequisites",{"type":66,"tag":149,"props":571,"children":572},{},[573],{"type":66,"tag":160,"props":574,"children":577},{"href":575,"rel":576},"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fnemo-relay-cli\u002Fbasic-usage#transparent-run",[556],[578],{"type":72,"value":579},"CLI transparent run",{"type":66,"tag":149,"props":581,"children":582},{},[583],{"type":66,"tag":160,"props":584,"children":587},{"href":585,"rel":586},"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fgetting-started\u002Fconfiguration",[556],[588],{"type":72,"value":589},"Configuration and setup handoff",{"items":591,"total":746},[592,610,624,635,647,661,674,688,701,712,726,735],{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":607,"repoUrl":608,"updatedAt":609},"nemoclaw-user-guide","retrieve NemoClaw documentation and configuration","Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[598,601,604],{"name":599,"slug":600,"type":15},"Documentation","documentation",{"name":602,"slug":603,"type":15},"MCP","mcp",{"name":605,"slug":606,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":611,"name":611,"fn":612,"description":613,"org":614,"tags":615,"stars":621,"repoUrl":622,"updatedAt":623},"mcore-build-and-dependency","manage Megatron-LM development environments","Container-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[616,619,620],{"name":617,"slug":618,"type":15},"Containers","containers",{"name":17,"slug":18,"type":15},{"name":21,"slug":22,"type":15},17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":625,"name":625,"fn":626,"description":627,"org":628,"tags":629,"stars":621,"repoUrl":622,"updatedAt":634},"mcore-bump-base-image","update NVIDIA PyTorch base images","Bump the NVIDIA PyTorch base image (`nvcr.io\u002Fnvidia\u002Fpytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker\u002F.ngc_version.dev` and GitLab CI in `.gitlab\u002Fstages\u002F01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[630,633],{"name":631,"slug":632,"type":15},"CI\u002FCD","ci-cd",{"name":17,"slug":18,"type":15},"2026-07-14T05:25:59.97109",{"slug":636,"name":636,"fn":637,"description":638,"org":639,"tags":640,"stars":621,"repoUrl":622,"updatedAt":646},"mcore-cicd","manage CI\u002FCD pipelines for Megatron-LM","CI\u002FCD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request\u002FBRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[641,642,643],{"name":631,"slug":632,"type":15},{"name":17,"slug":18,"type":15},{"name":644,"slug":645,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":648,"name":648,"fn":649,"description":650,"org":651,"tags":652,"stars":621,"repoUrl":622,"updatedAt":660},"mcore-create-issue","investigate CI failures and create issues","Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[653,656,657],{"name":654,"slug":655,"type":15},"Debugging","debugging",{"name":644,"slug":645,"type":15},{"name":658,"slug":659,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":662,"name":662,"fn":663,"description":664,"org":665,"tags":666,"stars":621,"repoUrl":622,"updatedAt":673},"mcore-linting-and-formatting","lint and format Megatron-LM code","Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[667,670],{"name":668,"slug":669,"type":15},"Best Practices","best-practices",{"name":671,"slug":672,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":675,"name":675,"fn":676,"description":677,"org":678,"tags":679,"stars":621,"repoUrl":622,"updatedAt":687},"mcore-migrate-gpt-to-hybrid","migrate Megatron-LM models to HybridModel","Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[680,683,686],{"name":681,"slug":682,"type":15},"Machine Learning","machine-learning",{"name":684,"slug":685,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":689,"name":689,"fn":690,"description":691,"org":692,"tags":693,"stars":621,"repoUrl":622,"updatedAt":700},"mcore-onboard-gb200-1node-tests","onboard functional tests for GB200","Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[694,697],{"name":695,"slug":696,"type":15},"QA","qa",{"name":698,"slug":699,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":702,"name":702,"fn":703,"description":704,"org":705,"tags":706,"stars":621,"repoUrl":622,"updatedAt":711},"mcore-run-on-slurm","launch distributed training jobs on SLURM","How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[707,708],{"name":17,"slug":18,"type":15},{"name":709,"slug":710,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":713,"name":713,"fn":714,"description":715,"org":716,"tags":717,"stars":621,"repoUrl":622,"updatedAt":725},"mcore-split-pr","split pull requests to reduce review load","Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[718,721,722],{"name":719,"slug":720,"type":15},"Code Review","code-review",{"name":644,"slug":645,"type":15},{"name":723,"slug":724,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":727,"name":727,"fn":728,"description":729,"org":730,"tags":731,"stars":621,"repoUrl":622,"updatedAt":734},"mcore-testing","run and manage Megatron-LM tests","Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[732,733],{"name":695,"slug":696,"type":15},{"name":698,"slug":699,"type":15},"2026-07-14T05:25:54.928983",{"slug":736,"name":736,"fn":737,"description":738,"org":739,"tags":740,"stars":621,"repoUrl":622,"updatedAt":745},"nightly-sync","manage nightly main-to-dev sync workflows","Domain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[741,744],{"name":742,"slug":743,"type":15},"Automation","automation",{"name":631,"slug":632,"type":15},"2026-07-30T05:29:03.275638",496,{"items":748,"total":840},[749,763,775,784,797,810,825],{"slug":750,"name":750,"fn":751,"description":752,"org":753,"tags":754,"stars":29,"repoUrl":30,"updatedAt":762},"nemo-relay-debug-runtime-integration","debug NeMo Relay runtime integrations","Use this skill when NeMo Relay is installed or imported but application-side runtime behavior is missing or incorrect, including load failures, inactive scopes, missing events, and plugin or adaptive wiring problems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[755,756,759,761],{"name":654,"slug":655,"type":15},{"name":757,"slug":758,"type":15},"Engineering","engineering",{"name":760,"slug":45,"type":15},"Middleware",{"name":9,"slug":8,"type":15},"2026-07-17T05:30:27.286964",{"slug":469,"name":469,"fn":764,"description":765,"org":766,"tags":767,"stars":29,"repoUrl":30,"updatedAt":774},"get started with NeMo Relay","Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[768,769,770,773],{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"name":771,"slug":772,"type":15},"Onboarding","onboarding",{"name":21,"slug":22,"type":15},"2026-07-23T05:43:39.488827",{"slug":4,"name":4,"fn":5,"description":6,"org":776,"tags":777,"stars":29,"repoUrl":30,"updatedAt":31},{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[778,779,780,781,782,783],{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},{"name":27,"slug":28,"type":15},{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},{"name":24,"slug":25,"type":15},{"slug":785,"name":785,"fn":786,"description":787,"org":788,"tags":789,"stars":29,"repoUrl":30,"updatedAt":796},"nemo-relay-instrument-calls","instrument LLM calls with NeMo Relay","Use this skill when an application owns tool or LLM\u002Fprovider call sites and needs to wrap them with NeMo Relay scopes and managed execution APIs for lifecycle events, middleware, or guardrails.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[790,791,794,795],{"name":742,"slug":743,"type":15},{"name":792,"slug":793,"type":15},"LLM","llm",{"name":760,"slug":45,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T05:30:29.31214",{"slug":798,"name":798,"fn":799,"description":800,"org":801,"tags":802,"stars":29,"repoUrl":30,"updatedAt":809},"nemo-relay-instrument-context-isolation","isolate NeMo Relay execution contexts","Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[803,806,807,808],{"name":804,"slug":805,"type":15},"Concurrency","concurrency",{"name":757,"slug":758,"type":15},{"name":760,"slug":45,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T05:30:33.080543",{"slug":811,"name":811,"fn":812,"description":813,"org":814,"tags":815,"stars":29,"repoUrl":30,"updatedAt":824},"nemo-relay-instrument-typed-wrappers","instrument NeMo Relay typed wrappers","Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[816,819,822,823],{"name":817,"slug":818,"type":15},"API Development","api-development",{"name":820,"slug":821,"type":15},"JSON","json",{"name":760,"slug":45,"type":15},{"name":9,"slug":8,"type":15},"2026-07-23T05:43:40.456621",{"slug":826,"name":826,"fn":827,"description":828,"org":829,"tags":830,"stars":29,"repoUrl":30,"updatedAt":839},"nemo-relay-migrate-from-flow","migrate applications from NeMo Flow to Relay","Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[831,834,835,836,837,838],{"name":832,"slug":833,"type":15},"Go","go",{"name":684,"slug":685,"type":15},{"name":27,"slug":28,"type":15},{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},{"name":24,"slug":25,"type":15},"2026-07-17T05:30:28.259456",10]