fix: support Cursor CLI hook config

[AjayThorve]

Overview

Fix Cursor CLI hook configuration so current cursor-agent builds can execute NeMo Flow hook commands, and document the remaining Cursor CLI hook coverage limits.

• 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

• Generate Cursor .cursor/hooks.json entries as direct command entries with top-level "version": 1.
• Preserve that Cursor-compatible shape when nemo-flow run -- cursor-agent temporarily patches project hooks.
• Update nemo-flow doctor cursor to reject nested Cursor hook groups and missing or non-1 top-level version fields.
• Trim nullable fields from Cursor permission responses.
• Update Cursor integration docs and packaged hooks to state the CLI limitation plainly: current Cursor CLI hook coverage is narrower than Cursor IDE hook coverage.

Where should the reviewer start?

Start with crates/cli/src/installer.rs for the hook-shape change, then crates/cli/src/doctor.rs for validation of user-managed Cursor hook files.

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

• Closes https://linear.app/nvidia/issue/NMF-122/fix-cursor-cli-hook-config-and-document-stream-json-limitation

Summary by CodeRabbit

• Refactor

  • Standardized Cursor hook JSON to require a top-level version (1) and direct command entries; merged/generated hook files now enforce this shape.

• New Features

  • Added stricter validation for Cursor hook files with clear, actionable status messages and test coverage.

• Bug Fixes

  • Cursor hook responses/endpoints no longer include legacy message fields.

• Documentation

  • Expanded Cursor integration and troubleshooting guidance, plus CLI verification steps.

[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: ca9197bf-9784-4d1b-8294-add0e0891d8e

📥 Commits

Reviewing files that changed from the base of the PR and between 3f86119 and 4d93bde.

📒 Files selected for processing (12)

• crates/cli/src/adapters/cursor.rs
• crates/cli/src/doctor.rs
• crates/cli/src/installer.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• integrations/coding-agents/cursor/.cursor/hooks.json
• integrations/coding-agents/cursor/README.md

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (29)

**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-ffi-surface/SKILL.md)

**/*.rs: Run cargo fmt --all for FFI work as it is Rust work
Run just test-rust for FFI validation
Run cargo clippy --workspace --all-targets -- -D warnings to enforce warnings-as-errors linting

**/*.rs: Run cargo fmt --all for Rust code formatting
Run cargo clippy --workspace --all-targets -- -D warnings to enforce Rust linting with no warnings
Run just test-rust as the shared-runtime build/test wrapper for Rust changes

Use Rust snake_case naming convention for Rust code

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for Rust code formatting when Node changes touch Rust files
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting when Rust files changed as part of Node work

**/*.rs: Always run just test-rust when any Rust code changes
Always run cargo fmt --all when any Rust code changes
Always run cargo clippy --workspace --all-targets -- -D warnings when any Rust code changes

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{rs,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in all Rust, Go, JavaScript, and TypeScript source files using C-style comment syntax

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use SONAR_IGNORE_START / SONAR_IGNORE_END markers only for documented false positives that cannot be resolved in code; keep ignored blocks small, add explanatory comments, and require reviewer sign-off

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{js,ts,tsx,jsx,py,rs,go,java,c,cpp,h,cc,cxx,cs,rb,php,swift,kt}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changed files must be formatted with the language-native formatter

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{py,js,ts,tsx,go,rs,md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

Format changed files with the language-native formatter before the final lint/test pass

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• integrations/coding-agents/cursor/README.md
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{rs,py,js,ts,tsx,go}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

During iteration, prefer uv run pre-commit run --files <changed files...> for targeted validation

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs
• crates/cli/tests/coverage/launcher_tests.rs

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs

**/*.{md,rst,html,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,html}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst,txt}: Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as 'here' or 'read more.'
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not add trademark symbols to NeMo Flow learning documentation by default.
Do not rewrite API names, package names, command flags, or code literals for style reasons.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.{md,markdown,rst}: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Use monospace formatting for code elements, commands, parameters, package names, and expressions
Use monospace formatting for directories, file names, and paths
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Use quotation marks for error messages and strings in documentation
Use bold formatting for UI buttons, menus, fields, and labels in documentation
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use in documentation
Use italics for publication titles in documentation
Use plain text formatting for keyboard shortcuts in documentation
Prefer [NVIDIA/NeMo](link) format for GitHub repository references over generic phrases like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text in documentation
Avoid generic link anchors such as 'here,' 'this page,' and 'read more' in documentation
Include the acronym in link text if a linked term includes an acronym
Do not link long sentences or multiple sentences in documentation
Avoid links that pull readers away from a procedure unles...

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{html,md}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in HTML and Markdown files using HTML comment syntax

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/README.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update relevant crate or package README when that surface changed

Relevant package or crate README.md files must be updated when examples or binding guidance changes

Files:

• integrations/coding-agents/cursor/README.md

**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run Markdown link checking via lychee for README.md, CONTRIBUTING.md, and docs/ through pre-commit hooks

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,java,cpp,go,rust}

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

Keep package names, repo references, and build commands current in documentation

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash}

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

Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,example}

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

Example commands must match current package names and paths

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/{integrations,integration,*-integration}/**

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

**/{integrations,integration,*-integration}/**: Keep NeMo Flow optional in framework integrations
Preserve the framework's original behavior when NeMo Flow is absent
Wrap tool and LLM paths at the correct framework boundary
Integration pattern must follow docs/integrate-frameworks/adding-scopes.md

Files:

• integrations/coding-agents/cursor/README.md

**/*.{md,txt,rst}

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

**/*.{md,txt,rst}: Ensure commands, package names, file paths, and APIs in documentation are correct and not stale; flag incorrect or outdated information as blocking issues
Ensure examples and procedures in documentation will execute successfully with current APIs and commands
Use consistent user-facing terminology throughout documentation that matches current repo terminology
Capitalize NVIDIA correctly in all documentation and public-facing text
Format code, commands, paths, and filenames as inline code (monospace) in documentation
Use descriptive anchor text for links instead of bare URLs or weak labels like 'here' in documentation
Prefer active voice, present tense, short sentences, and plain English in documentation
Structure documentation procedures as imperative steps that are easy to scan and not too long for a single sequence
Prefer 'after' instead of 'once' for temporal references in documentation
Use 'can' instead of 'may' when describing possibility (rather than permission) in documentation
Avoid ambiguous numeric dates and ordinal dates in documentation body text

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/index.md,**/README.md}

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

Update entry-point documentation (README.md, docs/index.md, package READMEs, binding-level source READMEs) whenever public behavior changes

Files:

• integrations/coding-agents/cursor/README.md

docs/**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run ./scripts/build-docs.sh for documentation site changes

docs/**/*.md: Relevant getting-started or reference docs must be updated when examples change
Release-policy docs must point to GitHub Releases as the only release-history source of truth

docs/**/*.md: Use title case for headings in technical documentation
Introduce code blocks, tables, and lists with complete lead-in sentences in documentation

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{RELEASING.md,CHANGELOG.md,docs/**/*.md}

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

Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

docs/integrate-frameworks/**/*.md

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

Documentation must be updated if activation or usage of the integration changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{scripts/*.sh,docs/**/*.md}

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

Use root ./scripts/*.sh commands in docs and contributor guidance as documented, with implementations under scripts/third-party/

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,examples/**,crates/adaptive/**,python/nemo_flow/**,go/nemo_flow/**,**/{example,component}.{ts,tsx,js,rs,py,go}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Any new adaptive component kind must have documentation, examples, and binding coverage across all supported languages

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README*,CHANGELOG*,docs/**/*.{md,rst,txt},examples/**/*,*.md}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update documentation, examples, and getting-started guides with new package/module/crate names after rename operations

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/**/*.md,examples/**/*.{js,ts,py,go,rs}}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Keep documentation and examples synchronized with current install, import, and build commands

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,CONTRIBUTING.md,docs/**/*.md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For docs-only changes, run targeted checks only if commands, package names, or examples changed. Use just docs for docs-site builds and just docs-linkcheck when links changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

🔇 Additional comments (12)

crates/cli/src/adapters/cursor.rs (1)

36-39: LGTM!

crates/cli/tests/coverage/adapters_tests.rs (1)

260-261: LGTM!

crates/cli/tests/coverage/server_tests.rs (1)

467-468: LGTM!

crates/cli/tests/coverage/installer_tests.rs (1)

142-155: LGTM!

crates/cli/tests/coverage/doctor_tests.rs (1)

415-589: LGTM!

crates/cli/tests/coverage/launcher_tests.rs (1)

458-460: LGTM!

Also applies to: 501-505, 531-533

integrations/coding-agents/cursor/.cursor/hooks.json (1)

3-93: LGTM!

integrations/coding-agents/cursor/README.md (1)

18-29: LGTM!

Also applies to: 59-61, 135-137

docs/integrate-frameworks/coding-agent-cursor.md (1)

18-32: LGTM!

Also applies to: 51-53, 134-137, 149-151

crates/cli/src/installer.rs (1)

201-203: LGTM!

Also applies to: 231-232, 235-236, 252-253, 280-299, 302-307

crates/cli/src/launcher.rs (1)

826-837: LGTM!

crates/cli/src/doctor.rs (1)

409-411: LGTM!

Also applies to: 437-535

---

Walkthrough

Standardize Cursor CLI hooks to a top-level "version": 1 with direct per-event "command" entries; installer/launcher emit and normalize that shape; doctor validates and rejects nested/grouped hooks; adapter response omits unused message fields; tests and docs updated accordingly.

Changes

Cursor Hook Schema and Validation

Layer / File(s)	Summary
Cursor hook configuration format integrations/coding-agents/cursor/.cursor/hooks.json, integrations/coding-agents/cursor/README.md, docs/integrate-frameworks/coding-agent-cursor.md	Flattened hooks.json: top-level "version": 1 with per-event arrays of { command, timeout }; README/docs updated to require versioned direct-command entries and document CLI limitations.
Cursor hook generation and merging crates/cli/src/installer.rs, crates/cli/src/launcher.rs	Installer adds direct_command_hooks_for_events and narrows wildcard matcher logic to Claude/Codex tool spellings; launcher ensures merged hooks include top-level version: 1 before pretty-serializing.
Cursor hook JSON validation crates/cli/src/doctor.rs	Adds cursor_hook_file_status that checks for hook-forward cursor marker, parses JSON, enforces version == 1 and hooks object, rejects nested hook groups, and requires at least one direct hook-forward cursor command entry.
Cursor adapter response cleanup crates/cli/src/adapters/cursor.rs	ToolStarted response no longer includes user_message or agent_message; retains continue: true and permission: "allow".
Cursor hook and adapter test coverage crates/cli/tests/coverage/*	Added/updated tests: installer test verifies direct-command version: 1 output; doctor tests reject grouped/unversioned hooks and accept correct versioned direct entries; launcher tests assert patched .cursor/hooks.json has version: 1 before restore; adapter/server tests assert omitted message fields.

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title follows Conventional Commits format with type 'fix' and concise imperative summary under 72 characters.
Description check	✅ Passed	Description includes all required sections: Overview with confirmation checkboxes, Details explaining changes, Where to start, and Related Issues with action keyword.
Docstring Coverage	✅ Passed	Docstring coverage is 91.94% which is sufficient. The required threshold is 80.00%.
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

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 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.

Inline comments:
In `@crates/cli/src/doctor.rs`:
- Around line 488-496: The current check only fails when a nested group contains
a NeMo "hook-forward cursor" command; change the detection so
has_nested_nemo_hook (or the logic that inspects `parsed`) returns true for any
nested hook group regardless of its inner command names, and keep the existing
return path that uses `path` and the same failure message; update the
has_nested_nemo_hook implementation to traverse the parsed hook tree and flag
any nested group node (e.g., any entry with its own `hooks` array) rather than
matching specific command strings.

In `@docs/integrate-frameworks/coding-agent-cursor.md`:
- Around line 136-138: Summary: Replace the incorrect artifact name "ATOF" with
the correct "ATIF". Fix: edit the sentence that currently references "ATOF" and
change it to "ATIF" so the text reads that records absent from ATIF were not
emitted; ensure any other occurrences of the token "ATOF" in the same document
are updated to "ATIF" to keep terminology consistent with the documented export
artifact.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 4f0f7ba1-95f9-4e25-9457-c903a9538380

📥 Commits

Reviewing files that changed from the base of the PR and between 954d961 and e5acf8b.

📒 Files selected for processing (19)

• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/hermes.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/src/doctor.rs
• crates/cli/src/installer.rs
• crates/cli/src/launcher.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/tests/coverage/setup_tests.rs
• crates/core/src/observability/atif.rs
• crates/core/tests/unit/atif_tests.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• integrations/coding-agents/cursor/.cursor/hooks.json
• integrations/coding-agents/cursor/README.md

📜 Review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)

• GitHub Check: WebAssembly / Test (windows-arm64)
• GitHub Check: Node.js / Test (linux-amd64)
• GitHub Check: WebAssembly / Test (windows-amd64)
• GitHub Check: WebAssembly / Test (macos-arm64)
• GitHub Check: Node.js / Test (windows-arm64)
• GitHub Check: WebAssembly / Test (linux-amd64)
• GitHub Check: Node.js / Test (windows-amd64)
• GitHub Check: Node.js / Test (linux-arm64)
• GitHub Check: WebAssembly / Test (linux-arm64)
• GitHub Check: Rust / Test (linux-amd64)
• GitHub Check: Python / Test (linux-arm64)
• GitHub Check: Rust / Test (windows-amd64)
• GitHub Check: Go / Test (linux-arm64)
• GitHub Check: Python / Test (linux-amd64)
• GitHub Check: Rust / Test (linux-arm64)
• GitHub Check: Python / Test (windows-amd64)
• GitHub Check: Python / Test (windows-arm64)
• GitHub Check: Python / Test (macos-arm64)
• GitHub Check: Rust / Test (windows-arm64)
• GitHub Check: OpenClaw / Test
• GitHub Check: Go / Test (windows-arm64)
• GitHub Check: Go / Test (macos-arm64)
• GitHub Check: Node.js / Test (macos-arm64)
• GitHub Check: Rust / Test (macos-arm64)
• GitHub Check: Documentation / Build
• GitHub Check: Go / Test (windows-amd64)
• GitHub Check: Go / Test (linux-amd64)

🧰 Additional context used

📓 Path-based instructions (34)

**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-ffi-surface/SKILL.md)

**/*.rs: Run cargo fmt --all for FFI work as it is Rust work
Run just test-rust for FFI validation
Run cargo clippy --workspace --all-targets -- -D warnings to enforce warnings-as-errors linting

**/*.rs: Run cargo fmt --all for Rust code formatting
Run cargo clippy --workspace --all-targets -- -D warnings to enforce Rust linting with no warnings
Run just test-rust as the shared-runtime build/test wrapper for Rust changes

Use Rust snake_case naming convention for Rust code

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for Rust code formatting when Node changes touch Rust files
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting when Rust files changed as part of Node work

**/*.rs: Always run just test-rust when any Rust code changes
Always run cargo fmt --all when any Rust code changes
Always run cargo clippy --workspace --all-targets -- -D warnings when any Rust code changes

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

**/*.{rs,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in all Rust, Go, JavaScript, and TypeScript source files using C-style comment syntax

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use SONAR_IGNORE_START / SONAR_IGNORE_END markers only for documented false positives that cannot be resolved in code; keep ignored blocks small, add explanatory comments, and require reviewer sign-off

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

**/*.{js,ts,tsx,jsx,py,rs,go,java,c,cpp,h,cc,cxx,cs,rb,php,swift,kt}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changed files must be formatted with the language-native formatter

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

**/*.{py,js,ts,tsx,go,rs,md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

Format changed files with the language-native formatter before the final lint/test pass

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• integrations/coding-agents/cursor/README.md
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

**/*.{rs,py,js,ts,tsx,go}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

During iteration, prefer uv run pre-commit run --files <changed files...> for targeted validation

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/doctor.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/adapters/mod.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/src/session.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/src/installer.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/observability/atif.rs
• crates/cli/src/adapters/hermes.rs

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/setup_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/core/tests/unit/atif_tests.rs
• crates/cli/tests/coverage/session_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs

**/*.{md,rst,html,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,html}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst,txt}: Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as 'here' or 'read more.'
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not add trademark symbols to NeMo Flow learning documentation by default.
Do not rewrite API names, package names, command flags, or code literals for style reasons.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.{md,markdown,rst}: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Use monospace formatting for code elements, commands, parameters, package names, and expressions
Use monospace formatting for directories, file names, and paths
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Use quotation marks for error messages and strings in documentation
Use bold formatting for UI buttons, menus, fields, and labels in documentation
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use in documentation
Use italics for publication titles in documentation
Use plain text formatting for keyboard shortcuts in documentation
Prefer [NVIDIA/NeMo](link) format for GitHub repository references over generic phrases like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text in documentation
Avoid generic link anchors such as 'here,' 'this page,' and 'read more' in documentation
Include the acronym in link text if a linked term includes an acronym
Do not link long sentences or multiple sentences in documentation
Avoid links that pull readers away from a procedure unles...

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{html,md}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in HTML and Markdown files using HTML comment syntax

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/README.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update relevant crate or package README when that surface changed

Relevant package or crate README.md files must be updated when examples or binding guidance changes

Files:

• integrations/coding-agents/cursor/README.md

**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run Markdown link checking via lychee for README.md, CONTRIBUTING.md, and docs/ through pre-commit hooks

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,java,cpp,go,rust}

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

Keep package names, repo references, and build commands current in documentation

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash}

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

Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,example}

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

Example commands must match current package names and paths

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/{integrations,integration,*-integration}/**

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

**/{integrations,integration,*-integration}/**: Keep NeMo Flow optional in framework integrations
Preserve the framework's original behavior when NeMo Flow is absent
Wrap tool and LLM paths at the correct framework boundary
Integration pattern must follow docs/integrate-frameworks/adding-scopes.md

Files:

• integrations/coding-agents/cursor/README.md

**/*.{md,txt,rst}

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

**/*.{md,txt,rst}: Ensure commands, package names, file paths, and APIs in documentation are correct and not stale; flag incorrect or outdated information as blocking issues
Ensure examples and procedures in documentation will execute successfully with current APIs and commands
Use consistent user-facing terminology throughout documentation that matches current repo terminology
Capitalize NVIDIA correctly in all documentation and public-facing text
Format code, commands, paths, and filenames as inline code (monospace) in documentation
Use descriptive anchor text for links instead of bare URLs or weak labels like 'here' in documentation
Prefer active voice, present tense, short sentences, and plain English in documentation
Structure documentation procedures as imperative steps that are easy to scan and not too long for a single sequence
Prefer 'after' instead of 'once' for temporal references in documentation
Use 'can' instead of 'may' when describing possibility (rather than permission) in documentation
Avoid ambiguous numeric dates and ordinal dates in documentation body text

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/index.md,**/README.md}

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

Update entry-point documentation (README.md, docs/index.md, package READMEs, binding-level source READMEs) whenever public behavior changes

Files:

• integrations/coding-agents/cursor/README.md

crates/{core,adaptive}/**

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/tests/unit/atif_tests.rs
• crates/core/src/observability/atif.rs

{crates/core,crates/adaptive}/**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-wasm-binding/SKILL.md)

If the change touched shared runtime semantics in crates/core or crates/adaptive, also use validate-change

Files:

• crates/core/tests/unit/atif_tests.rs
• crates/core/src/observability/atif.rs

crates/core/**/*.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

When crates/core changes, run the full validation matrix across Rust, Python, Go, Node.js, and WebAssembly

crates/core/**/*.rs: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths. Keep errors explicit and binding-appropriate at the wrapper layer.

Files:

• crates/core/tests/unit/atif_tests.rs
• crates/core/src/observability/atif.rs

crates/{core,adaptive}/**/*.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/tests/unit/atif_tests.rs
• crates/core/src/observability/atif.rs

docs/**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run ./scripts/build-docs.sh for documentation site changes

docs/**/*.md: Relevant getting-started or reference docs must be updated when examples change
Release-policy docs must point to GitHub Releases as the only release-history source of truth

docs/**/*.md: Use title case for headings in technical documentation
Introduce code blocks, tables, and lists with complete lead-in sentences in documentation

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{RELEASING.md,CHANGELOG.md,docs/**/*.md}

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

Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

docs/integrate-frameworks/**/*.md

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

Documentation must be updated if activation or usage of the integration changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{scripts/*.sh,docs/**/*.md}

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

Use root ./scripts/*.sh commands in docs and contributor guidance as documented, with implementations under scripts/third-party/

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,examples/**,crates/adaptive/**,python/nemo_flow/**,go/nemo_flow/**,**/{example,component}.{ts,tsx,js,rs,py,go}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Any new adaptive component kind must have documentation, examples, and binding coverage across all supported languages

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README*,CHANGELOG*,docs/**/*.{md,rst,txt},examples/**/*,*.md}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update documentation, examples, and getting-started guides with new package/module/crate names after rename operations

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/**/*.md,examples/**/*.{js,ts,py,go,rs}}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Keep documentation and examples synchronized with current install, import, and build commands

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,CONTRIBUTING.md,docs/**/*.md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For docs-only changes, run targeted checks only if commands, package names, or examples changed. Use just docs for docs-site builds and just docs-linkcheck when links changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

crates/core/src/observability/{atif,otel,openinference}.rs

📄 CodeRabbit inference engine (.agents/skills/maintain-observability/SKILL.md)

crates/core/src/observability/{atif,otel,openinference}.rs: When changing event fields, exporter behavior, subscriber config, or binding parity for ATIF, OpenTelemetry, or OpenInference, ensure the core event model and emitted fields remain in sync across ATIF (crates/core/src/observability/atif.rs), OpenTelemetry (crates/core/src/observability/otel.rs), and OpenInference (crates/core/src/observability/openinference.rs)
When event fields in observability exporters change, run the affected Rust crate tests plus just test-rust

Files:

• crates/core/src/observability/atif.rs

🔇 Additional comments (20)

crates/cli/src/session.rs (1)

731-734: LGTM!

crates/cli/src/adapters/cursor.rs (1)

36-39: LGTM!

integrations/coding-agents/cursor/.cursor/hooks.json (1)

1-96: LGTM!

crates/cli/src/installer.rs (4)

63-65: LGTM!

---

202-237: LGTM!

---

281-300: LGTM!

---

302-308: LGTM!

crates/cli/tests/coverage/server_tests.rs (1)

464-465: LGTM!

crates/cli/src/launcher.rs (1)

726-738: LGTM!

crates/cli/tests/coverage/launcher_tests.rs (1)

413-415: LGTM!

Also applies to: 456-460, 486-488

crates/cli/tests/coverage/installer_tests.rs (1)

145-158: LGTM!

crates/cli/tests/coverage/adapters_tests.rs (1)

260-261: LGTM!

Also applies to: 322-325, 341-362, 399-399, 435-566

integrations/coding-agents/cursor/README.md (1)

18-27: LGTM!

Also applies to: 57-59, 123-125, 127-133

crates/cli/tests/coverage/doctor_tests.rs (1)

239-337: LGTM!

crates/core/src/observability/atif.rs (1)

943-978: LGTM!

Also applies to: 1053-1053, 1061-1086

crates/cli/src/adapters/mod.rs (1)

72-77: LGTM!

Also applies to: 315-319

crates/core/tests/unit/atif_tests.rs (1)

54-57: LGTM!

Also applies to: 626-701

crates/cli/src/adapters/hermes.rs (1)

41-64: LGTM!

Also applies to: 66-66, 93-105, 121-126, 133-138, 170-175, 193-198, 207-289

crates/cli/tests/coverage/setup_tests.rs (1)

335-335: LGTM!

crates/cli/tests/coverage/session_tests.rs (1)

361-540: LGTM!

[coderabbitai]

Actionable comments posted: 4

🤖 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.

Inline comments:
In `@crates/cli/src/launcher.rs`:
- Around line 832-834: The current logic only inserts "version" if missing,
allowing non-1 values to persist; change the merged JSON handling so that when
merged.as_object_mut() returns Some(root) you unconditionally set/overwrite the
"version" field to json!(1) (replace the use of
root.entry("version").or_insert_with(...) with an assignment/insertion that
always writes json!(1)) so patched Cursor hooks are normalized to version 1.

In `@crates/cli/tests/coverage/doctor_tests.rs`:
- Around line 321-349: Add a negative test that asserts a non-1 "version" fails:
create a temp hooks.json like in cursor_hook_status_requires_version_one but
include "\"version\": 2" at top-level, call hook_file_status(Ok(hooks_path),
CodingAgent::Cursor, true, "hooks: user-managed"), and assert status ==
Status::Fail and that details contains "version" and "1" (to lock the “must be
exactly 1” contract); reuse the same tempfile setup and assertions pattern used
in cursor_hook_status_requires_version_one and reference the existing
hook_file_status, CodingAgent::Cursor, and Status::Fail symbols.

In `@docs/integrate-frameworks/coding-agent-cursor.md`:
- Around line 27-30: Update the wording in the sentence currently reading "may
only appear" to "can only appear" in
docs/integrate-frameworks/coding-agent-cursor.md so it follows the style rule
for possibility; locate the phrase in the paragraph that starts "Cursor CLI hook
coverage is not the same as Cursor IDE hook coverage" and replace that exact
substring to ensure consistency with the guideline.

In `@integrations/coding-agents/cursor/README.md`:
- Around line 24-26: The sentence uses "may" for possibility; update the phrase
"may only appear" to "can only appear" in the README sentence that starts
"Cursor CLI hook coverage is still narrower than Cursor IDE hook coverage. In
headless `--print` runs, assistant messages and tools such as WebSearch may only
appear in `--output-format stream-json` output rather than hook payloads." so
the wording becomes "can only appear" to match the docs style guide.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 3319b5e1-ab6c-4253-89b1-ab9f1cf2fed2

📥 Commits

Reviewing files that changed from the base of the PR and between e5acf8b and d5a5055.

📒 Files selected for processing (12)

• crates/cli/src/adapters/cursor.rs
• crates/cli/src/doctor.rs
• crates/cli/src/installer.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• integrations/coding-agents/cursor/.cursor/hooks.json
• integrations/coding-agents/cursor/README.md

📜 Review details

🧰 Additional context used

📓 Path-based instructions (29)

**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-ffi-surface/SKILL.md)

**/*.rs: Run cargo fmt --all for FFI work as it is Rust work
Run just test-rust for FFI validation
Run cargo clippy --workspace --all-targets -- -D warnings to enforce warnings-as-errors linting

**/*.rs: Run cargo fmt --all for Rust code formatting
Run cargo clippy --workspace --all-targets -- -D warnings to enforce Rust linting with no warnings
Run just test-rust as the shared-runtime build/test wrapper for Rust changes

Use Rust snake_case naming convention for Rust code

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for Rust code formatting when Node changes touch Rust files
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting when Rust files changed as part of Node work

**/*.rs: Always run just test-rust when any Rust code changes
Always run cargo fmt --all when any Rust code changes
Always run cargo clippy --workspace --all-targets -- -D warnings when any Rust code changes

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{rs,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in all Rust, Go, JavaScript, and TypeScript source files using C-style comment syntax

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use SONAR_IGNORE_START / SONAR_IGNORE_END markers only for documented false positives that cannot be resolved in code; keep ignored blocks small, add explanatory comments, and require reviewer sign-off

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{js,ts,tsx,jsx,py,rs,go,java,c,cpp,h,cc,cxx,cs,rb,php,swift,kt}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changed files must be formatted with the language-native formatter

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{py,js,ts,tsx,go,rs,md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

Format changed files with the language-native formatter before the final lint/test pass

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• integrations/coding-agents/cursor/README.md
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• crates/cli/src/doctor.rs

**/*.{rs,py,js,ts,tsx,go}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

During iteration, prefer uv run pre-commit run --files <changed files...> for targeted validation

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs

**/*.{md,rst,html,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,html}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst,txt}: Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as 'here' or 'read more.'
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not add trademark symbols to NeMo Flow learning documentation by default.
Do not rewrite API names, package names, command flags, or code literals for style reasons.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.{md,markdown,rst}: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Use monospace formatting for code elements, commands, parameters, package names, and expressions
Use monospace formatting for directories, file names, and paths
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Use quotation marks for error messages and strings in documentation
Use bold formatting for UI buttons, menus, fields, and labels in documentation
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use in documentation
Use italics for publication titles in documentation
Use plain text formatting for keyboard shortcuts in documentation
Prefer [NVIDIA/NeMo](link) format for GitHub repository references over generic phrases like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text in documentation
Avoid generic link anchors such as 'here,' 'this page,' and 'read more' in documentation
Include the acronym in link text if a linked term includes an acronym
Do not link long sentences or multiple sentences in documentation
Avoid links that pull readers away from a procedure unles...

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{html,md}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in HTML and Markdown files using HTML comment syntax

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/README.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update relevant crate or package README when that surface changed

Relevant package or crate README.md files must be updated when examples or binding guidance changes

Files:

• integrations/coding-agents/cursor/README.md

**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run Markdown link checking via lychee for README.md, CONTRIBUTING.md, and docs/ through pre-commit hooks

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,java,cpp,go,rust}

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

Keep package names, repo references, and build commands current in documentation

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash}

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

Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,example}

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

Example commands must match current package names and paths

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/{integrations,integration,*-integration}/**

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

**/{integrations,integration,*-integration}/**: Keep NeMo Flow optional in framework integrations
Preserve the framework's original behavior when NeMo Flow is absent
Wrap tool and LLM paths at the correct framework boundary
Integration pattern must follow docs/integrate-frameworks/adding-scopes.md

Files:

• integrations/coding-agents/cursor/README.md

**/*.{md,txt,rst}

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

**/*.{md,txt,rst}: Ensure commands, package names, file paths, and APIs in documentation are correct and not stale; flag incorrect or outdated information as blocking issues
Ensure examples and procedures in documentation will execute successfully with current APIs and commands
Use consistent user-facing terminology throughout documentation that matches current repo terminology
Capitalize NVIDIA correctly in all documentation and public-facing text
Format code, commands, paths, and filenames as inline code (monospace) in documentation
Use descriptive anchor text for links instead of bare URLs or weak labels like 'here' in documentation
Prefer active voice, present tense, short sentences, and plain English in documentation
Structure documentation procedures as imperative steps that are easy to scan and not too long for a single sequence
Prefer 'after' instead of 'once' for temporal references in documentation
Use 'can' instead of 'may' when describing possibility (rather than permission) in documentation
Avoid ambiguous numeric dates and ordinal dates in documentation body text

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/index.md,**/README.md}

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

Update entry-point documentation (README.md, docs/index.md, package READMEs, binding-level source READMEs) whenever public behavior changes

Files:

• integrations/coding-agents/cursor/README.md

docs/**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run ./scripts/build-docs.sh for documentation site changes

docs/**/*.md: Relevant getting-started or reference docs must be updated when examples change
Release-policy docs must point to GitHub Releases as the only release-history source of truth

docs/**/*.md: Use title case for headings in technical documentation
Introduce code blocks, tables, and lists with complete lead-in sentences in documentation

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{RELEASING.md,CHANGELOG.md,docs/**/*.md}

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

Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

docs/integrate-frameworks/**/*.md

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

Documentation must be updated if activation or usage of the integration changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{scripts/*.sh,docs/**/*.md}

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

Use root ./scripts/*.sh commands in docs and contributor guidance as documented, with implementations under scripts/third-party/

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,examples/**,crates/adaptive/**,python/nemo_flow/**,go/nemo_flow/**,**/{example,component}.{ts,tsx,js,rs,py,go}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Any new adaptive component kind must have documentation, examples, and binding coverage across all supported languages

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README*,CHANGELOG*,docs/**/*.{md,rst,txt},examples/**/*,*.md}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update documentation, examples, and getting-started guides with new package/module/crate names after rename operations

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/**/*.md,examples/**/*.{js,ts,py,go,rs}}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Keep documentation and examples synchronized with current install, import, and build commands

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,CONTRIBUTING.md,docs/**/*.md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For docs-only changes, run targeted checks only if commands, package names, or examples changed. Use just docs for docs-site builds and just docs-linkcheck when links changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

🔇 Additional comments (9)

integrations/coding-agents/cursor/.cursor/hooks.json (1)

3-93: LGTM!

crates/cli/src/installer.rs (1)

200-201: LGTM!

Also applies to: 230-231, 234-235, 251-252, 279-306

crates/cli/src/doctor.rs (1)

409-535: LGTM!

crates/cli/src/adapters/cursor.rs (1)

36-39: LGTM!

crates/cli/tests/coverage/adapters_tests.rs (1)

259-261: LGTM!

crates/cli/tests/coverage/server_tests.rs (1)

462-463: LGTM!

crates/cli/tests/coverage/installer_tests.rs (1)

142-155: LGTM!

crates/cli/tests/coverage/doctor_tests.rs (1)

238-319: LGTM!

Also applies to: 351-381

crates/cli/tests/coverage/launcher_tests.rs (1)

458-460: LGTM!

Also applies to: 501-505, 531-533

[coderabbitai]

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@integrations/coding-agents/cursor/README.md`:
- Around line 18-21: The README's hook command example is out of sync with the
shipped .cursor/hooks.json bundle; update the documented command string to match
the packaged hook entry by replacing the example `nemo-flow hook-forward cursor`
with `nemo-flow-sidecar hook-forward cursor` (or vice versa if you intend to
change the bundle), and ensure the README still describes the top-level
`"version": 1` and the direct command entry shape `{"command": "...", "timeout":
30}` to reflect the actual .cursor/hooks.json used by this integration.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: d636b5e0-9577-4496-9fb9-525208d835ad

📥 Commits

Reviewing files that changed from the base of the PR and between d5a5055 and 3f86119.

📒 Files selected for processing (12)

• crates/cli/src/adapters/cursor.rs
• crates/cli/src/doctor.rs
• crates/cli/src/installer.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• integrations/coding-agents/cursor/.cursor/hooks.json
• integrations/coding-agents/cursor/README.md

📜 Review details

🧰 Additional context used

📓 Path-based instructions (29)

**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-ffi-surface/SKILL.md)

**/*.rs: Run cargo fmt --all for FFI work as it is Rust work
Run just test-rust for FFI validation
Run cargo clippy --workspace --all-targets -- -D warnings to enforce warnings-as-errors linting

**/*.rs: Run cargo fmt --all for Rust code formatting
Run cargo clippy --workspace --all-targets -- -D warnings to enforce Rust linting with no warnings
Run just test-rust as the shared-runtime build/test wrapper for Rust changes

Use Rust snake_case naming convention for Rust code

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for Rust code formatting when Node changes touch Rust files
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting when Rust files changed as part of Node work

**/*.rs: Always run just test-rust when any Rust code changes
Always run cargo fmt --all when any Rust code changes
Always run cargo clippy --workspace --all-targets -- -D warnings when any Rust code changes

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{rs,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in all Rust, Go, JavaScript, and TypeScript source files using C-style comment syntax

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use SONAR_IGNORE_START / SONAR_IGNORE_END markers only for documented false positives that cannot be resolved in code; keep ignored blocks small, add explanatory comments, and require reviewer sign-off

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{js,ts,tsx,jsx,py,rs,go,java,c,cpp,h,cc,cxx,cs,rb,php,swift,kt}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changed files must be formatted with the language-native formatter

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

**/*.{py,js,ts,tsx,go,rs,md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

Format changed files with the language-native formatter before the final lint/test pass

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• integrations/coding-agents/cursor/README.md
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• docs/integrate-frameworks/coding-agent-cursor.md
• crates/cli/src/doctor.rs

**/*.{rs,py,js,ts,tsx,go}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

During iteration, prefer uv run pre-commit run --files <changed files...> for targeted validation

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/src/launcher.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/src/adapters/cursor.rs
• crates/cli/tests/coverage/doctor_tests.rs
• crates/cli/src/installer.rs
• crates/cli/src/doctor.rs

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/tests/coverage/launcher_tests.rs
• crates/cli/tests/coverage/installer_tests.rs
• crates/cli/tests/coverage/server_tests.rs
• crates/cli/tests/coverage/doctor_tests.rs

**/*.{md,rst,html,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,html}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,rst,txt}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst,txt}: Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as 'here' or 'read more.'
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not add trademark symbols to NeMo Flow learning documentation by default.
Do not rewrite API names, package names, command flags, or code literals for style reasons.

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.{md,markdown,rst}: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Use monospace formatting for code elements, commands, parameters, package names, and expressions
Use monospace formatting for directories, file names, and paths
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Use quotation marks for error messages and strings in documentation
Use bold formatting for UI buttons, menus, fields, and labels in documentation
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use in documentation
Use italics for publication titles in documentation
Use plain text formatting for keyboard shortcuts in documentation
Prefer [NVIDIA/NeMo](link) format for GitHub repository references over generic phrases like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text in documentation
Avoid generic link anchors such as 'here,' 'this page,' and 'read more' in documentation
Include the acronym in link text if a linked term includes an acronym
Do not link long sentences or multiple sentences in documentation
Avoid links that pull readers away from a procedure unles...

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{html,md}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in HTML and Markdown files using HTML comment syntax

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/README.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update relevant crate or package README when that surface changed

Relevant package or crate README.md files must be updated when examples or binding guidance changes

Files:

• integrations/coding-agents/cursor/README.md

**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run Markdown link checking via lychee for README.md, CONTRIBUTING.md, and docs/ through pre-commit hooks

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,java,cpp,go,rust}

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

Keep package names, repo references, and build commands current in documentation

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash}

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

Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/*.{md,markdown,py,sh,bash,js,ts,example}

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

Example commands must match current package names and paths

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

**/{integrations,integration,*-integration}/**

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

**/{integrations,integration,*-integration}/**: Keep NeMo Flow optional in framework integrations
Preserve the framework's original behavior when NeMo Flow is absent
Wrap tool and LLM paths at the correct framework boundary
Integration pattern must follow docs/integrate-frameworks/adding-scopes.md

Files:

• integrations/coding-agents/cursor/README.md

**/*.{md,txt,rst}

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

**/*.{md,txt,rst}: Ensure commands, package names, file paths, and APIs in documentation are correct and not stale; flag incorrect or outdated information as blocking issues
Ensure examples and procedures in documentation will execute successfully with current APIs and commands
Use consistent user-facing terminology throughout documentation that matches current repo terminology
Capitalize NVIDIA correctly in all documentation and public-facing text
Format code, commands, paths, and filenames as inline code (monospace) in documentation
Use descriptive anchor text for links instead of bare URLs or weak labels like 'here' in documentation
Prefer active voice, present tense, short sentences, and plain English in documentation
Structure documentation procedures as imperative steps that are easy to scan and not too long for a single sequence
Prefer 'after' instead of 'once' for temporal references in documentation
Use 'can' instead of 'may' when describing possibility (rather than permission) in documentation
Avoid ambiguous numeric dates and ordinal dates in documentation body text

Files:

• integrations/coding-agents/cursor/README.md
• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/index.md,**/README.md}

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

Update entry-point documentation (README.md, docs/index.md, package READMEs, binding-level source READMEs) whenever public behavior changes

Files:

• integrations/coding-agents/cursor/README.md

docs/**/*.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Run ./scripts/build-docs.sh for documentation site changes

docs/**/*.md: Relevant getting-started or reference docs must be updated when examples change
Release-policy docs must point to GitHub Releases as the only release-history source of truth

docs/**/*.md: Use title case for headings in technical documentation
Introduce code blocks, tables, and lists with complete lead-in sentences in documentation

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{RELEASING.md,CHANGELOG.md,docs/**/*.md}

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

Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

docs/integrate-frameworks/**/*.md

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

Documentation must be updated if activation or usage of the integration changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{scripts/*.sh,docs/**/*.md}

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

Use root ./scripts/*.sh commands in docs and contributor guidance as documented, with implementations under scripts/third-party/

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,examples/**,crates/adaptive/**,python/nemo_flow/**,go/nemo_flow/**,**/{example,component}.{ts,tsx,js,rs,py,go}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Any new adaptive component kind must have documentation, examples, and binding coverage across all supported languages

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README*,CHANGELOG*,docs/**/*.{md,rst,txt},examples/**/*,*.md}

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update documentation, examples, and getting-started guides with new package/module/crate names after rename operations

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,docs/**/*.md,examples/**/*.{js,ts,py,go,rs}}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Keep documentation and examples synchronized with current install, import, and build commands

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{README.md,CONTRIBUTING.md,docs/**/*.md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For docs-only changes, run targeted checks only if commands, package names, or examples changed. Use just docs for docs-site builds and just docs-linkcheck when links changed

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/integrate-frameworks/coding-agent-cursor.md

🔇 Additional comments (12)

integrations/coding-agents/cursor/.cursor/hooks.json (1)

3-93: LGTM!

integrations/coding-agents/cursor/README.md (1)

24-29: LGTM!

Also applies to: 59-61, 135-137

docs/integrate-frameworks/coding-agent-cursor.md (1)

18-32: LGTM!

Also applies to: 51-53, 134-137, 149-151

crates/cli/src/installer.rs (1)

201-203: LGTM!

Also applies to: 231-232, 252-253, 280-299, 302-307

crates/cli/src/launcher.rs (1)

826-837: LGTM!

crates/cli/src/doctor.rs (1)

409-411: LGTM!

Also applies to: 437-535

crates/cli/src/adapters/cursor.rs (1)

36-39: LGTM!

crates/cli/tests/coverage/adapters_tests.rs (1)

260-261: LGTM!

crates/cli/tests/coverage/server_tests.rs (1)

467-468: LGTM!

crates/cli/tests/coverage/installer_tests.rs (1)

142-155: LGTM!

crates/cli/tests/coverage/doctor_tests.rs (1)

415-589: LGTM!

crates/cli/tests/coverage/launcher_tests.rs (1)

458-460: LGTM!

Also applies to: 501-505, 531-533

[willkill07]

/merge