Thanks a lot for sharing this. I looked into Transitive a while back and really liked the terminal module’s hole-punching approach. Clean solution.
My goal here is slightly different: instead of building a fleet platform or a full remote-ops framework, but a very minimal “pipe” layer that robotics teams can drop in when they just need:
• A low-latency, firewall-friendly data path
• Lightweight downsampled topic streaming for debugging
• Automatic recording for short sessions
Basically a “debug-mode transport” rather than a platform.
That’s why I am talking to teams– to validate whether a super small ROS-agnostic pipe solves 80% of the remote-debugging pain without the overhead.
That said, I love the direction you are taking with Remote RViz. There’s definitely room for future interoperability (e.g., an agent that speaks both APIs).
I’d be very interested in comparing notes on pain points we’re seeing across users. Feel free to DM me.