agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/IsaacTeleop/src/core/replay_trackers/AGENTS.md

IsaacTeleop / replay_trackers

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

CRITICAL (non-optional): Before editing this package, complete the mandatory AGENTS.md preflight in ../../../AGENTS.md (read every applicable AGENTS.md on your paths, not just this file). Replay impls for trackers declared in ../deviceio_trackers/trackers.toml are emitted into ${CMAKE_BINARY_DIR}/generated/trackers/replay_trackers/. Only the hand-written trackers (head, hand, controller, full_body, message_channel, haptic_command_reader, TensorPushTracker, keyboard) have .cpp files in this directory. - replay_deviceio_factory.{hpp,cpp} stays hand-written but #includes generated .inc fragments for the manifest trackers' forward decls, try-create thunks, dispatch rows, and factory methods. Do not add rows for…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    CRITICAL (non-optional): Before editing this package, complete the mandatory AGENTS.md preflight in ../../../AGENTS.md (read every …

    line 8
  2. Distinctive:

    Do not: add rows for a manifest tracker by hand.

    line 20

≈ “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 -->

Agent notes — replay_trackers

CRITICAL (non-optional): Before editing this package, complete the mandatory AGENTS.md preflight in ../../../AGENTS.md (read every applicable AGENTS.md on your paths, not just this file).

Half this package is generated

Replay impls for trackers declared in ../deviceio_trackers/trackers.toml are emitted into ${CMAKE_BINARY_DIR}/generated/trackers/replay_trackers/. Only the hand-written trackers (head, hand, controller, full_body, message_channel, haptic_command_reader, TensorPushTracker, keyboard) have .cpp files in this directory.

  • replay_deviceio_factory.{hpp,cpp} stays hand-written but #includes generated .inc fragments for the manifest trackers' forward decls, try-create thunks, dispatch rows, and factory methods. Do not add rows for a manifest tracker by hand.
  • The forward-decl fragment is shared with the live factory header — it is generated_tracker_forward_decls.inc, not a replay-specific one. Keep it direction-agnostic.

Missing-data logging is warn-once, by design

A replay impl reaching EOF or a gap is called every frame. Log the "no data" message once per gap behind a warned_no_data_ flag and reset the flag when a record arrives — never write to std::cerr unconditionally in update(). The generated impls do this; hand-written ones must too. This unification is why the generated replay stack is not a byte-for-byte port of the older per-tracker files.

Related docs

  • Manifest and generator rules: ../codegen/AGENTS.md
  • Replay session lifecycle: ../deviceio_session/AGENTS.md
  • Live counterpart: ../live_trackers/AGENTS.md

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.

Check your setup, free