| name | bag-replay-debugger |
| description | Check rosbag or recorded data replay issues involving topic names, clocks, remaps, timing, and consumer mismatch. Use when replayed data does not reproduce expected behavior. |
Bag Replay Debugger
Overview
Check rosbag or recorded data replay issues involving topic names, clocks, remaps, timing, and consumer mismatch.
Core Workflow
- Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
- Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
- Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
- Validate the explanation with the smallest reliable check the repo or environment supports.
Deliver
- A concise diagnosis with the most likely root cause or bounded uncertainty.
- The highest-signal evidence and suspect files, configs, or systems involved.
- The smallest safe fix path or next experiment to run.
Guardrails
- Do not claim a root cause without evidence that explains the observed behavior.
- Separate symptoms from likely causes and call out uncertainty explicitly.
- Prefer the smallest reproducible scope before escalating to broad changes.
- Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.
