Best-move arrows
Top 1–3 lines with distinct colours: amber for the engine pick, green and grey for the alternates. Alt+F2 cycles depth of the stack.
A dark overlay that reads the position, draws the best line and plays it with a human hand. Stockfish 19 runs inside the browser — no cloud, no queue, no tell in the network tab.
The panel sits in the corner of chess.com. Arrows draw over the board, the engine streams UCI locally, and autoplay only fires after the line settles.
Top 1–3 lines with distinct colours: amber for the engine pick, green and grey for the alternates. Alt+F2 cycles depth of the stack.
Live evaluation with correct mate handling. The bar tracks the current position, not the last one, and does not drift while you drag.
Every gesture is checked against the expected board placement instead of a timer. The ladder runs drag → click-click → trusted input, then retries once.
A random 300–1200 ms pause before each move, plus a speed preset that scales with the clock. Own side or both sides — your call in the popup.
After game over: rematch against bots, new game after a human win, or an offer after a loss. The queue retries if a modal ignores the first click.
Stockfish boots in an offscreen document, streams UCI and keeps the latest position. Threads = cores − 1, hash 256 MB, single-thread build as fallback.
Boot output from a clean run. Engine lines, timing, gesture result and replay state are printed in the panel — no hidden phase, no mystery delay.
Single-purpose build. It loads on chess.com, draws over the board and hosts the engine locally. No remote configuration, no analytics endpoint.
Unpacked build, desktop Chrome. The engine downloader is a local PowerShell script; it pulls the NNUE files once.
Extract the delivered zip to a folder you keep. Do not run it from inside the archive; Chrome needs a real directory with the manifest at the root.
Open chrome://extensions, enable Developer mode, choose Load unpacked and select the folder. Pin the extension to the toolbar.
The build ships with a downloader. Run it once from the extension folder, then reload the extension.
powershell -ExecutionPolicy Bypass -File .\get-engine.ps1 -Flavor fullStart a chess.com game. The panel boots the engine, draws the line and waits. F2 hides or shows the overlay; Alt+F2 changes how many lines are drawn.
Current build is 2.1.0. The manifest version is the source of truth.
No. The build ships with a loader that pulls the Stockfish 19 JavaScript and WASM files into engine/. If that folder is empty after unpacking, run the PowerShell command once.
Only the last rung of the autoplay ladder: real mouse events through chrome.debugger when synthetic gestures fail. Chrome shows its debug infobar while attached; the extension detaches as soon as the move fires.
Yes. Auto side: own follows board orientation; both makes the engine answer every move. Both modes still run the same verification and humanizer.
Anything Chromium-based at 116+ can load an unpacked MV3 build. The shipped target is desktop Chrome; other Chromium builds are not part of the support matrix.
In chrome.storage.local on your machine. Removing the extension clears them; the build has no server-side profile.
Replace the folder contents with the new build and press reload on chrome://extensions. The desk posts a notice when chess.com changes something the scraper depends on.
Crash Farm handles the 0x21cracks settlement window, bet engine and market buyer.