agentleFS
NVIDIAKnown publisherNVIDIA/IsaacTeleop/deps/cloudxr/webxr_client/AGENTS.md

IsaacTeleop / webxr_client

AGENTS.md438 starsChanged 31 days agoApache-2.0View on GitHub

Validate IWER/DevUI upgrades with stationary controller-gizmo taps and drags in an active, visible XR session. Successful connection and loader tests do not verify controller manipulation. Keep react and react-dom on the same minor release supported by @react-three/fiber. Validate dependency-range changes with a clean npm install; do not bypass peer checks with --force or --legacy-peer-deps. Synthetic XR browser checks use the dev server's hot reload. Do not edit or format client files while those checks run: remounting the app invalidates the…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep react and react-dom on the same minor release supported by @react-three/fiber.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

WebXR client dependencies

Validate IWER/DevUI upgrades with stationary controller-gizmo taps and drags in an active, visible XR session. Successful connection and loader tests do not verify controller manipulation.

Keep react and react-dom on the same minor release supported by @react-three/fiber. Validate dependency-range changes with a clean npm install; do not bypass peer checks with --force or --legacy-peer-deps.

Synthetic XR browser checks use the dev server's hot reload. Do not edit or format client files while those checks run: remounting the app invalidates the session and input ownership observations.

Synthetic examples must start teleoperation through the existing client handler. Do not hard-code a controller ray to an assumed 3D panel position.

Long-running synthetic-input tests against MockCloudXR must supply decoded mock frames. Preserve the production decoder startup watchdog and input release on disconnect.

Complete client formatting before staging and running pre-commit; do not run formatters concurrently with hooks, which detect any file changes during a run.

Session errors restored after reload must retain banner priority over asynchronous startup notices and status cleanup until a stream connects successfully.

Selecting Custom preserves current profile-driven settings; named profiles apply their defaults.

Connect readiness must remain blocked during emulator loading and capability checks, even when form validation or XR-store notifications update the button. Cover startup with a delayed emulator bundle and click as soon as Connect becomes available.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.