How it works › Rerun interop

Rerun interop

Lands with dashboard cards

Rerun is the backdoor for robotics data that wants a real 3D and time-series viewer. A dashboard names a recording written from its own datasets; its "Open in Rerun" menu hands it over.

Open in Rerun

Lands with dashboard cards

rerun: names a .rrd file written at build time from the same datasets by tools/rerun_export.py, with a blueprint that mirrors the layout. rerun-sdk is a uv run extra, never a runtime dependency of the kit. The menu offers three things: open the file in Rerun's hosted viewer, copy the native command, or download the file.

the menu's two links

https://app.rerun.io/version/0.40.0/index.html?url=<absolute rrd URL>
uvx --from rerun-sdk==0.40.0 rerun <rrd URL>

gallery/dashboard-cards/views.base · rerun: (planned syntax)

rerun:
  rrd: rerun/dashboard-cards.rrd
  sdk: 0.40.0

Planned syntax, from lane/dashboard-cards @ 4ceda4d (docs/peps/0005-dashboard-cards.md, gallery/examples/dashboard-cards). Not on main yet: this block becomes live when that lane lands.

The .rrd is generated, never hand-edited. Opening the hosted viewer loads Rerun's own page from app.rerun.io, the one place a dashboard reaches another site, and only when the reader asks.

Comes from docs/peps/0005-dashboard-cards.md §6 on lane/dashboard-cards (not on main yet) in docs/.