UI Guide

foldback-ui is a Tauri desktop app for inspecting a .foldback session — a recorded file, or a running game connected live.

Run it from a checkout with:

cargo run -p foldback-ui

Opening a session

Three ways:

Drag a .foldback file onto the window — no dialog, no setup.
Click Open session… and pick a file.
Click Connect live… and give it a game’s live-mode URL (defaults to ws://127.0.0.1:9871) — see Cookbook recipe 7 for embedding the server side in your game. The same timeline/peer-comparison/drill-down views below fill in as frames arrive; the timeline auto-follows the latest tick until you scrub manually. A disconnect (the game exits, or the connection drops) is shown in the status pill with the real reason — whatever streamed in stays inspectable, nothing is discarded.

Tick timeline: the full recorded tick range, green where every reporting peer agreed, red from the first divergence onward. Click anywhere to scrub; the accent line marks your current tick. Accent tick marks are recorded snapshots.
Peers at tick N: each peer’s hash for the selected tick, with the odd-one-out highlighted red when they disagree. Below it, the last tick peers agreed on and the nearest snapshot at or before the divergence, when one exists.
Session: which hashing levels this file actually has data for (tick, and entity/field if recorded), whether the recording ended cleanly, and counts of metadata entries and snapshots.
Bisection result: entity/field-level drill-down, when the file has EntityHash/FieldHash frames for the selected tick (Session::hash_entity/hash_field, cookbook recipes 4/5 — see examples/ggrs-demo for a real recording that includes them). A session with only Level 1 (tick) data shows a plain note here instead of fabricated detail. When field data does exist, the UI shows the raw diverging values side by side and does not guess a root cause — check them against your own simulation code.

See the Foldback UI mockup for the original visual spec this was built against.