Develop

[Aniket-Manus]

Manus Documentation update for isaaclab

[greptile-apps]

Plugin path uses wrong root

When a user follows this workflow from the IsaacLab checkout, ./install/plugins/manus/manus_hand_plugin resolves relative to IsaacLab instead of the separate IsaacTeleop repository where the executable is installed, causing the command to fail with “No such file or directory” and leaving glove tracking unavailable.

[greptile-apps]

Greptile Summary

The PR updates the Manus teleoperation documentation.

• Runs environment-profile discovery through the selected Isaac Lab Python environment.
• Documents launching the native Manus plugin after starting CloudXR.

Confidence Score: 4/5

The documentation should not merge until the Manus launch command establishes the IsaacTeleop build directory or uses an unambiguous executable path.

The documented relative plugin path is resolved from the user's current directory, while the executable is installed under a separate IsaacTeleop checkout, causing the recommended workflow to fail from the IsaacLab workspace.

Files Needing Attention: docs/source/how-to/cloudxr_teleoperation.rst

Important Files Changed

Filename	Overview
docs/source/how-to/cloudxr_teleoperation.rst	Updates Manus setup commands, but the new plugin launch command assumes an unstated IsaacTeleop working directory.

_{Reviews (1): Last reviewed commit: "Updated setup documentation to use Manus..." | Re-trigger Greptile}

[isaaclab-review-bot]

Isaac Lab Review Bot

Documentation-only update to the CloudXR/Manus guide. The newly added manual plugin-launch workflow is unclear about its relationship to automatic activation and uses a relative executable path without establishing the required working directory.

• Design and architecture: No source, package, or module architecture is affected.
• API: No public API symbols, CLI arguments, or configuration contracts are changed.
• Implementation: The manual Manus plugin step needs clarification and an unambiguous invocation path so users can reliably follow the documented workflow.

Minor fixes needed. Posted 1 actionable finding inline.

Conservative automated review; human maintainers own approval decisions.

[isaaclab-review-bot]

🔵 Suggestion · Implementation — New step contradicts automatic activation text

The unchanged paragraph just above states the Manus plugin ships in isaacteleop and is "activated automatically when configured in the environment's retargeting pipeline", while the added step requires manually building and launching manus_hand_plugin from a relative ./install/... path in an unspecified working directory. Reconcile the two passages and give an unambiguous path or cd step for the binary.