Baseline History
Scan Setup
Per-user game conditions (optional)
Put a condition in parentheses immediately after a username. Only matching games and their opponents are retained; archive verification still covers the requested date scope. Conditions supplement, not override, the global game-history range.
lichess:mjkstorm(goose_on_the_moose)chesscom:player(vs:goose_* AND (type:rapid OR type:blitz))lichess:player(finished:2026-01-01..2026-10-28 AND rated:true AND color:white)Fields: vs / opponent, type / speed, variant, tc / timecontrol, result (win/loss/draw), color, rated (true/false), started, finished / date, duration (s/m/h/d), ownrating, opprating, termination (Lichess). Boolean: AND, OR, NOT, parentheses; &, |, !. Wildcards: * (any characters), ? (one character). Numeric: > >= < <= =; e.g. duration>5m, opprating>=1800. Date values use UTC calendar dates (YYYY-MM-DD) or timezone-qualified ISO timestamps (Z or offset); ranges use .. . Missing source fields never count as matching an explicit positive condition.
New scans save available results in this browser automatically.
Progress
Results
SQL-edited working data: changes are not provider-verified scan evidence and cannot be saved as a verified baseline. Saved CASS history remains untouched.
Simple Results
Closed opponents and Lichess ToS flags from saved observations.
An account closure does not necessarily mean cheating. Statuses can change.
SQL Results Workspace
No blocking scan runningSQL queries use current results, not saved history. Changes here stay in the working copy unless you separately authorize re-importing them into saved history.
How SQL handles data and history
SQL queries use ten related tables and five views projected from current in-session scan data. The opponents view preserves existing queries, while game_history exposes retained game details (not all counted games). Historical IndexedDB baselines are not loaded into SQL. With rebuild checked, each execution starts from the original snapshot. Uncheck it to keep temporary SQLite edits, custom tables, and indexes between executions. SQL editing does not directly write saved history; only supported opponent-view edits can be mapped to CASS working results. The Advanced text search is separate from the full SQLite workspace. Saved scan history can change only through the separate permission-gated Re-import control below.
Filename fields record requested downloads only. Files probably go to Downloads; verify in your browser.
Back Up Current SQL Data saves the SQL working dataset as of the last completed query (including its preview if one ran). Back Up Original SQL Data saves the pre-edit SQL dataset. Both are versioned JSON recovery files. After SQLite has run, backups include a complete embedded SQLite database image (including custom tables). Before the first run, backups contain report data for reconstruction. Neither is a DBHistory backup. The filename fields show the last original and current SQL JSON backup filenames requested from the browser. Click a filename to copy its name. Your browser probably saves downloaded files in Downloads, but the destination depends on its download settings. Check your browser downloads to confirm the file exists. The browser retains its existing backup metadata, but restoration is performed only through Restore Backup SQL Data by choosing a JSON file; baselines and scan history are not restored.
Schema: Query opponents, game_history, opponent_history, latest_status, account_summary, or join the ten related tables. NULL means unavailable data. Keywords: SELECT, WHERE, GROUP BY, ORDER BY, LIMIT; SQLite write statements affect only the disposable workspace; re-importing supported changes into saved DBHistory is separately permission-gated, validated, and irreversible without recovery. SQL runs locally using same-origin, bundled SQL.js and SQLite WebAssembly.
Advanced Results
Results for scan
Search within the selected category and websites. Examples: user:opponent1 AND type:blitz, games:>1, tc:2+0, inc>0, is:any-tos. Game-detail searches can be incomplete for older games. Use the selected display timezone for game dates.
Game date filter uses your selected display timezone. Older history may lack complete date indexes; new scans retain up to your selected game-detail limit per opponent.
| Time control / duration | Game Result | Actions |
|---|