← ClaudeAtlas

foxglovelisted

Foxglove for robotics visualization: foxglove_bridge setup for live ROS 2 robots, layouts, MCAP recording and playback, and remote/web visualization of robots running on servers. Use when: 'foxglove', 'mcap', visualizing a robot running on a remote server, sharing visualization with others, or recording sessions for later analysis. The remote-viz answer in the robium stack — key to the local-vs-remote workflow (cross-ref environments). Not for: ROS desktop debugging (rviz2) or ML logging (rerun).
robium-ai/robium-plugin · ★ 0 · AI & Automation · score 73
Install: claude install-skill robium-ai/robium-plugin
# foxglove The remote/web visualization tool for robium: `foxglove_bridge` exposes a live ROS 2 graph over a WebSocket, and the Foxglove app (desktop or `app.foxglove.dev` in a browser) connects to it or opens a recorded MCAP file — the answer `environments` and `gazebo` route to whenever a robot or sim runs headless/remote and RViz2's local-display requirement doesn't fit. Two things changed over time and matter for how this skill is used: the bridge itself (`foxglove_bridge`, MIT-licensed, open source) moved its active development from `foxglove/ros-foxglove-bridge` (now ROS 1-only, maintenance mode) to the `foxglove/foxglove-sdk` monorepo, and the *app* that used to be free/open-source "Foxglove Studio" was discontinued in February 2024 (last open-source release v1.87.0, MPL-2.0) in favor of the current closed-source, commercial "Foxglove" 2.x app — which does still ship a free tier the product page states is "free forever" for local/live visualization, separate from its paid Data Platform/cloud features. The bridge migration was confirmed via direct fetch of the `foxglove/ros-foxglove-bridge` and `foxglove/foxglove-sdk` GitHub repos this session; the free-tier claim was confirmed via direct fetch of `foxglove.dev`'s pricing page, while the Studio-to-2.x licensing history was reconstructed via search-synthesis after the source blog post 404'd on direct fetch (see References) — re-verify before repeating either claim, since licensing terms are exactly the kind of thing tha