nemo-relay-get-started

# Get Started With NeMo Relay Guide a new user to visible Relay value with the least complicated applicable trial. Do not begin with production deployment or Relay's full architecture. Keep the first run focused on one observable success path. ## Choose A Try-Now Path Evaluate these paths in order. Use the first one that fits the user's stated goal and existing environment. 1. **CLI try-now (default)**: choose this for a generic "try Relay" request or when the user wants value without modifying application code. Run Codex, Claude Code, or Hermes through the local CLI wrapper. Read [CLI Try-Now](references/cli-try-now.md). 2. **Built-in integrations try-now**: choose this when an existing LangChain, LangGraph, Deep Agents, or OpenClaw application owns the execution boundary. Prefer the maintained supported integration over manual wrapping. Read [Built-In Integrations Try-Now](references/built-in-integrations-try-now.md). 3. **Language-specific manual try-now**: choose this when the user's Python, Node.js, or Rust application directly owns its tool or LLM call sites and no maintained integration is the better boundary. Read [Manual Language Try-Now](references/manual-language-try-now.md). Do not ask the user to choose among all three when their request, manifest, or framework already identifies the boundary. For an unspecified request, use the CLI path. When more than one CLI agent is available, ask one concise question to select the agent. ## R...