Use cases

Inspect — Why did that run look wrong?

Look through recorded states, actions, and timing. Find a data problem before changing your model.

Follow a small example: an offline walkthrough using synthetic numeric data. It keeps the source timestamps, missing samples, and limitations visible. A cleaner display is not proof that a robot task succeeded.

Compare — What did my change do?

Put two recordings side by side. Compare the evidence and keep a note of what to try next.

Compare recordings in the private workspace. Sign in and select a namespace, import your records, and choose an explicit alignment. Inspect the evidence before interpreting a delta; incompatible alignment suppresses metric comparisons. Imported recordings are not attested tinyrobot executions.

Explore — How does this model work?

Try a small robotics demo. Inspect its behavior and the code behind it, without setting up a robot.

Explore experiments: browser demos and recorded runs, not robot control. Each experiment explains its own execution mode and limits. Illustrations are not screenshots, recordings, or proof of physical hardware performance.

Monitor — What is my printer reporting?

Read the printer setup guide for private, read-only Bambu LAN monitoring. A local connector reports supported status and temperature fields; missing values stay unknown. Hardware support is unverified. This does not add camera access, printer controls, or automatic intervention.

Keep your tools. Bring the recordings and results here. Read the docs for setup and the boundaries of each workflow.