docs: clarify Gemini daemon routes

[willkill07]

Overview

Clarify that the managed daemon does not route Google Gemini or Vertex API requests, and document the compatible-proxy option.

• I confirm this contribution is my own work, or I have the right to submit it under this project's license.
• I searched existing issues and open pull requests, and this does not duplicate existing work.

Details

• Add a general managed-daemon provider-route limitation for Gemini and Vertex.
• Explain the same behavior in the Pi routing guide.
• Record the limitation as a known issue for release 0.9.

Where should the reviewer start?

docs/daemon/configuration.mdx: the new provider-routes section explains the daemon-level limitation and the compatible-proxy path.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Relates to: feat(cli): add high-performance daemon architecture #1000

Summary by CodeRabbit

• Documentation
  • Clarified which provider routes are supported by the managed daemon.
  • Documented that native Google Gemini and Vertex requests bypass Relay and do not produce LLM tracing spans or request-policy coverage.
  • Added guidance for routing Gemini traffic through OpenAI- or Anthropic-compatible providers or proxies.
  • Clarified how the pi integration handles unsupported Gemini and Vertex routes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 754efc24-dc97-4130-b3f7-db1b429e4ade

📥 Commits

Reviewing files that changed from the base of the PR and between 3c44758 and 89931e2.

📒 Files selected for processing (3)

• docs/about-nemo-relay/release-notes/index.mdx
• docs/daemon/configuration.mdx
• docs/nemo-relay-cli/pi.mdx

Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (2)

• GitHub Check: Check / Run
• GitHub Check: Preview docs

🧰 Additional context used

📓 Path-based instructions (4)

Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.

⚙️ CodeRabbit configuration file

Files:

• docs/daemon/configuration.mdx
• docs/nemo-relay-cli/pi.mdx
• docs/about-nemo-relay/release-notes/index.mdx

In MDX files, top-of-file comments must use JSX comment delimiters: `{/*` to open and `*/}` to close.

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Files:

• docs/daemon/configuration.mdx
• docs/nemo-relay-cli/pi.mdx
• docs/about-nemo-relay/release-notes/index.mdx

Run `just docs` when the docs site changed; `./scripts/build-docs.sh html` remains the compatibility wrapper

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Files:

• docs/nemo-relay-cli/pi.mdx
• docs/about-nemo-relay/release-notes/index.mdx

Verify MDX files use JSX delimiters for top-of-file SPDX comments.

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

Files:

• docs/daemon/configuration.mdx
• docs/nemo-relay-cli/pi.mdx
• docs/about-nemo-relay/release-notes/index.mdx

🔇 Additional comments (3)

docs/daemon/configuration.mdx (1)

492-510: LGTM!

docs/nemo-relay-cli/pi.mdx (1)

455-466: LGTM!

docs/about-nemo-relay/release-notes/index.mdx (1)

248-252: 📐 Maintainability & Code Quality

The repository guidance requires just docs when this documentation site changes. However, no evidence shows that the command was skipped or failed. Missing build output alone does not establish a violation, so this is only a generic validation reminder.

---

Walkthrough

The documentation now states that Relay supports OpenAI and Anthropic routes. It explains that native Gemini and Vertex traffic bypasses Relay and describes compatible-provider or proxy routing.

Changes

Provider route documentation

Layer / File(s)	Summary
Document supported provider routes docs/daemon/configuration.mdx, docs/nemo-relay-cli/pi.mdx, docs/about-nemo-relay/release-notes/index.mdx	The documentation lists supported OpenAI and Anthropic routes. It states that native Gemini and Vertex traffic bypasses Relay or is marked unserviceable-api. It provides compatible-provider and proxy routing guidance.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 89931

This documentation-only change accurately describes supported routes and Google-route bypasses, with no concrete merge-blocking risk identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format with the allowed lowercase type "docs". It clearly summarizes the documentation change, uses an imperative summary, contains 34 characters, and has no tra…
Description check	✅ Passed	The description includes all required template sections. It explains the change, identifies the starting point for review, confirms the required contribution checks, and references issue #1000 with th…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Fern docs preview: https://nvidia-preview-pull-request-1088.docs.buildwithfern.com/nemo/relay/dev

[willkill07]

/merge