## Captured tables

No games yet
Open a Replay Poker table on `casino.org` and play a hand. Captured tables will appear here.

## Settings

### Capture

Capture casino.org traffic

When off, no new HTTP or WebSocket frames are recorded. Existing captures are preserved.

### Sync

Auto-flush on every finishHand

When auto-flush is on, the moment a hand finishes the extension uploads it to the endpoint below — no waiting on a timer. Failures don't retry automatically (they show up as retry in Status; Flush now will pick them up). Hands still in progress, or hands where recording started mid-hand, are excluded either way.

Auto-delete after flush

Once a hand has been successfully uploaded, drop its captured frames from local storage. The upload audit row stays in the sync index, but the round will no longer appear in History (and you can't re-export it). Off by default — turn it on to keep the local capture buffer small on long sessions.

Endpoint —
Status —
Admin flush token

Optional. When set, the token rides inside the encrypted flush body and unlocks ingest of generic rounds (no visible hole cards) under the [Generic] bucket on the website. Leave empty to flush anonymously — non-generic rounds still upload normally. The token is a server-side scoped credential; it is not the website login password.

### Storage

Captured messages —
Approximate size —
Browser quota —

To remove captured data, tick the checkboxes next to a player, table, or round on the History page and use the Delete selected button in the action bar. Empty (0-hand) tables can be ticked too — the row's residual frames will be dropped along with it.