Skip to content

docs: simplify README and make landing docs agent-agnostic#4552

Merged
miyoungc merged 3 commits into
mainfrom
docs/agent-agnostic
May 29, 2026
Merged

docs: simplify README and make landing docs agent-agnostic#4552
miyoungc merged 3 commits into
mainfrom
docs/agent-agnostic

Conversation

@miyoungc
Copy link
Copy Markdown
Collaborator

@miyoungc miyoungc commented May 29, 2026

Summary

Simplifies the GitHub README into a short landing page and updates the docs site intro pages to describe NemoClaw as an agent-agnostic sandbox stack. OpenClaw and Hermes are both listed as supported agents, and Hermes is no longer labeled experimental.

Related Issue

None.

Changes

  • Rewrite README.md to point at docs for prerequisites, quickstarts, and deep topics instead of duplicating them inline.
  • Update docs/index.mdx, docs/about/overview.mdx, and docs/about/how-it-works.mdx with agent-agnostic framing and links to both OpenClaw and Hermes quickstarts.
  • Remove the experimental Hermes warning from docs/get-started/quickstart-hermes.mdx.
  • Move Model Router pool-config and routing-flow details from the old README into docs/inference/inference-options.mdx.
  • Retarget platform-matrix sync from README.md to docs/get-started/prerequisites.mdx using MDX {/* */} sentinels so Fern builds cleanly.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Verification

  • npx prek run --all-files passes (pre-commit hooks on commit)
  • npm test passes
  • Tests added or updated for new or changed behavior
  • No secrets, API keys, or credentials committed
  • Docs updated for user-facing behavior changes
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Miyoung Choi miyoungc@nvidia.com

Summary by CodeRabbit

  • Documentation

    • Streamlined README with clearer entry points and updated resource links
    • Rebranded architecture docs to emphasize NemoClaw/OpenShell and support for multiple agents
    • Removed the experimental warning from the Hermes quickstart
    • Added prerequisites page embedding for the platform matrix and clarified supported platforms
    • Added detailed Model Router guidance with YAML examples and tolerance explanation
    • Updated quickstart navigation to offer both OpenClaw and Hermes paths
  • Chores

    • Updated docs generation and pre-commit staging to target generated MDX prerequisites and related outputs

Review Change Stack

Move duplicated quickstart and Model Router content into the docs site,
retire the experimental Hermes label, and sync the platform matrix to
prerequisites.mdx with MDX-safe sentinels.
@miyoungc miyoungc added the documentation Improvements or additions to documentation label May 29, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 29, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 083088b5-f73f-4c97-a457-e73eb2b60ec4

📥 Commits

Reviewing files that changed from the base of the PR and between c5f186f and a39b68b.

📒 Files selected for processing (1)
  • README.md

📝 Walkthrough

Walkthrough

This PR rebrands docs from OpenClaw to NemoClaw/OpenShell, adds explicit OpenClaw and Hermes quickstarts, relocates the generated platform matrix into prerequisites.mdx (with script and pre-commit updates), removes the Hermes experimental warning, and expands Model Router inference guidance with examples and credential-flow notes.

Changes

Documentation Rebranding and Structure Updates

Layer / File(s) Summary
Platform matrix relocation and generation script updates
.pre-commit-config.yaml, scripts/generate-platform-docs.py, docs/get-started/prerequisites.mdx
Platform matrix moved from README to prerequisites.mdx wrapped with platform-matrix MDX sentinel comments. scripts/generate-platform-docs.py documented MDX sentinels and retargeted its patch to prerequisites.mdx. Pre-commit hook updated to run the generator and stage the MDX outputs.
NemoClaw/OpenShell branding and dual-agent quickstart support
README.md, docs/index.mdx, docs/about/overview.mdx, docs/about/how-it-works.mdx, docs/get-started/quickstart-hermes.mdx
Rebranded copy from OpenClaw to NemoClaw/OpenShell across site docs and homepage; added explicit quickstart links for OpenClaw (default) and Hermes; removed the Hermes “Experimental Feature” warning; updated about pages to reference supported agents and first-boot policies.
Model Router inference documentation expansion
docs/inference/inference-options.mdx
Added YAML router pool configuration example (prefill, checkpoint, tolerance, encoder, model entries), documented tolerance semantics, clarified the host-side router/request path, and noted that credentials flow through the OpenShell provider so sandboxes never see raw API keys.

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly Related PRs

Suggested Labels

Getting Started

Suggested Reviewers

  • ericksoa
  • cv
  • jyaunches

Poem

🐰
NemoClaw hops into OpenShell light,
Two quickstarts ready, both paths bright,
Tables moved to find their home,
Router notes now clearly roam,
Docs refreshed — the rabbit's delight.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: simplifying README and making landing docs agent-agnostic, which aligns with the core objectives of reducing README scope and rebranding docs away from OpenClaw-specific language.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/agent-agnostic

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 29, 2026

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. No E2E is recommended because this PR only changes documentation plus documentation-generation/pre-commit plumbing. It does not touch runtime CLI code, installer/onboarding logic, sandbox lifecycle, credentials handling, network policies, inference routing implementation, deployment code, or real assistant workflow code.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 29, 2026

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

  • None. Changes are documentation, pre-commit hook configuration for docs generation, and a docs table generation script. They do not modify scenario E2E workflows, scenario metadata, expected-state contracts, suite definitions, runtime/runner code, onboarding/install helpers, or suite scripts under test/e2e-scenario/.

Optional scenario E2E

  • None.

Relevant changed files

  • None.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 29, 2026

PR Review Advisor

Findings: 0 needs attention, 3 worth checking, 0 nice ideas
Since last review: 1 prior item resolved, 2 still apply, 0 new items found

Review findings

🛠️ Needs attention

  • None.

🔎 Worth checking

  • Source-of-truth review needed: Platform matrix generated documentation: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: `scripts/generate-platform-docs.py` targets `docs/get-started/prerequisites.mdx` and `docs/inference/inference-options.mdx`; `.pre-commit-config.yaml` stages those same files; `ci/platform-matrix.json:2` still names README generation.
  • Hermes warning removed without equivalent risk/status signal (docs/get-started/quickstart-hermes.mdx:13): The PR removes the top-level Hermes experimental warning while the same quickstart still documents security-sensitive operation: a forwarded OpenAI-compatible API on port 8642, optional dashboard forwarding on port 9119, bearer-token client authentication, remote CHAT_UI_URL exposure, and Hermes-specific policy allowances. That is not a code-level auth bypass, but it weakens operator awareness for an externally reachable agent API path unless Hermes maturity and production-readiness expectations are documented elsewhere with comparable prominence.
    • Recommendation: Keep a concise Hermes status/risk note in the quickstart, or link near the top to authoritative release/status guidance that covers Hermes support maturity, API exposure, dashboard exposure, credential handling, and production-readiness expectations.
    • Evidence: The diff deletes the `<Warning title="Experimental Feature">` block from `docs/get-started/quickstart-hermes.mdx`. The current page still documents `CHAT_UI_URL`, `http://127.0.0.1:8642/v1\`, optional dashboard forwarding on `9119`, bearer-token API auth, and an agent-specific baseline policy allowing Hermes runtime egress.
  • Platform matrix source comment still names README generation (ci/platform-matrix.json:2): The generator and pre-commit hook now retarget platform matrix output from README.md to `docs/get-started/prerequisites.mdx`, but the source metadata still says scripts generate README and docs tables. That stale source-of-truth comment can mislead future platform/provider status updates after README sentinels were removed.
    • Recommendation: Update the `$comment` in `ci/platform-matrix.json` to describe the current generated targets, or avoid naming README and state that docs tables are derived from the matrix.
    • Evidence: `scripts/generate-platform-docs.py` targets `docs/get-started/prerequisites.mdx` for `platform-matrix`, and `.pre-commit-config.yaml` stages `docs/get-started/prerequisites.mdx` plus `docs/inference/inference-options.mdx`. `ci/platform-matrix.json:2` still says: "Scripts read this to generate README and docs tables."

🌱 Nice ideas

  • None.
Since last review details

Current findings:

  • Source-of-truth review needed: Platform matrix generated documentation: The advisor marked localized patch analysis as needs_followup.
    • Recommendation: Identify the invalid state, source boundary, source-fix constraint, regression test, and removal condition before merging the localized behavior.
    • Evidence: `scripts/generate-platform-docs.py` targets `docs/get-started/prerequisites.mdx` and `docs/inference/inference-options.mdx`; `.pre-commit-config.yaml` stages those same files; `ci/platform-matrix.json:2` still names README generation.
  • Hermes warning removed without equivalent risk/status signal (docs/get-started/quickstart-hermes.mdx:13): The PR removes the top-level Hermes experimental warning while the same quickstart still documents security-sensitive operation: a forwarded OpenAI-compatible API on port 8642, optional dashboard forwarding on port 9119, bearer-token client authentication, remote CHAT_UI_URL exposure, and Hermes-specific policy allowances. That is not a code-level auth bypass, but it weakens operator awareness for an externally reachable agent API path unless Hermes maturity and production-readiness expectations are documented elsewhere with comparable prominence.
    • Recommendation: Keep a concise Hermes status/risk note in the quickstart, or link near the top to authoritative release/status guidance that covers Hermes support maturity, API exposure, dashboard exposure, credential handling, and production-readiness expectations.
    • Evidence: The diff deletes the `<Warning title="Experimental Feature">` block from `docs/get-started/quickstart-hermes.mdx`. The current page still documents `CHAT_UI_URL`, `http://127.0.0.1:8642/v1\`, optional dashboard forwarding on `9119`, bearer-token API auth, and an agent-specific baseline policy allowing Hermes runtime egress.
  • Platform matrix source comment still names README generation (ci/platform-matrix.json:2): The generator and pre-commit hook now retarget platform matrix output from README.md to `docs/get-started/prerequisites.mdx`, but the source metadata still says scripts generate README and docs tables. That stale source-of-truth comment can mislead future platform/provider status updates after README sentinels were removed.
    • Recommendation: Update the `$comment` in `ci/platform-matrix.json` to describe the current generated targets, or avoid naming README and state that docs tables are derived from the matrix.
    • Evidence: `scripts/generate-platform-docs.py` targets `docs/get-started/prerequisites.mdx` for `platform-matrix`, and `.pre-commit-config.yaml` stages `docs/get-started/prerequisites.mdx` plus `docs/inference/inference-options.mdx`. `ci/platform-matrix.json:2` still says: "Scripts read this to generate README and docs tables."

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

Bring back the Page | Description table with all doc links so the
simplified README still points readers to the full docs site map.
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
docs/about/overview.mdx (1)

8-8: ⚡ Quick win

Normalize branded term casing in keywords.

Use OpenClaw, NVIDIA OpenShell, and NVIDIA capitalization in keywords to match the project word list.

As per coding guidelines: “NVIDIA must be all caps” and “NemoClaw, OpenClaw, and OpenShell must use correct casing.”

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/about/overview.mdx` at line 8, Update the keywords array so branded
terms use the project's canonical casing: change "nemoclaw overview" to
"NemoClaw overview", "openclaw always-on assistants" to "OpenClaw always-on
assistants", and apply all-caps to NVIDIA where present (e.g., "nvidia
openshell" → "NVIDIA OpenShell", "nvidia nemotron" → "NVIDIA Nemotron"); ensure
the keywords array uses these exact corrected strings and leave unrelated
entries (like "hermes agent") unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/about/overview.mdx`:
- Line 8: Update the keywords array so branded terms use the project's canonical
casing: change "nemoclaw overview" to "NemoClaw overview", "openclaw always-on
assistants" to "OpenClaw always-on assistants", and apply all-caps to NVIDIA
where present (e.g., "nvidia openshell" → "NVIDIA OpenShell", "nvidia nemotron"
→ "NVIDIA Nemotron"); ensure the keywords array uses these exact corrected
strings and leave unrelated entries (like "hermes agent") unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 71318e8c-071b-493e-a8a6-0febc55773f8

📥 Commits

Reviewing files that changed from the base of the PR and between f81f4ac and fc1f879.

📒 Files selected for processing (9)
  • .pre-commit-config.yaml
  • README.md
  • docs/about/how-it-works.mdx
  • docs/about/overview.mdx
  • docs/get-started/prerequisites.mdx
  • docs/get-started/quickstart-hermes.mdx
  • docs/index.mdx
  • docs/inference/inference-options.mdx
  • scripts/generate-platform-docs.py
💤 Files with no reviewable changes (1)
  • docs/get-started/quickstart-hermes.mdx

@ericksoa ericksoa enabled auto-merge (squash) May 29, 2026 23:05
Copy link
Copy Markdown
Contributor

@ericksoa ericksoa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for the docs/README simplification. I reviewed the README/docs generator changes on c5f186f and locally verified the generated platform docs are in sync with python3 scripts/generate-platform-docs.py --check; diff whitespace checks are clean as well. CodeRabbit's metadata keyword-casing note is non-blocking.

Format the alpha notice as a GitHub blockquote alert and list supported
agents as bullets instead of inline prose.
@miyoungc miyoungc disabled auto-merge May 29, 2026 23:12
@miyoungc miyoungc enabled auto-merge (squash) May 29, 2026 23:12
@miyoungc miyoungc merged commit 843cf36 into main May 29, 2026
32 checks passed
@miyoungc miyoungc deleted the docs/agent-agnostic branch May 29, 2026 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants