A Chrome extension for GeoGuessr and OpenGuessr that adds:
- Copy — captures a full-resolution screenshot of the current panorama (via the DevTools Protocol, so it's sharper than a normal tab capture) and copies it to your clipboard. On OpenGuessr's Street View rounds it can sweep 360° and stitch the frames into one wide image.
- Locate (OpenGuessr only) — places the guess pin at the round's actual coordinates. A Safe mode toggle offsets the placed pin by a random 1–100 km instead of the exact spot.
- Autoplay (OpenGuessr only) — automatically guesses and continues each round on randomized delays, respecting Safe mode and any pin you've already placed with Locate.
Install from the Chrome Web Store listing. Chrome then keeps the extension up to date on its own. In OpenGuessr, Check for updates in the native Settings panel forces a check and installs a new version immediately.
Installing unpacked instead (development, or before the listing is live)
- Grab the latest zip from Releases.
- Unzip it.
- In Chrome, go to
chrome://extensions, enable Developer mode, click Load unpacked, and select the unzipped folder.
Chrome has no update channel for an unpacked copy, so Check for updates in OpenGuessr's Settings panel compares against the latest GitHub release and links to it — you replace the folder yourself.
background.js decides which of the two it can do by checking whether
chrome.runtime.getManifest() has an update_url, which Chrome only adds to
extensions it installed itself:
- Store install —
chrome.runtime.requestUpdateCheck()asks Chrome to fetch the new version, thenchrome.runtime.reload()restarts into it. That tears down every content script, so open game tabs need a refresh afterwards. - Unpacked — falls back to the GitHub Releases API and a download link.
There's deliberately no chrome.runtime.onUpdateAvailable listener: registering
one makes Chrome hold updates back until the extension calls reload() itself,
and restarting unprompted would kill an Autoplay run mid-round. Without a
listener Chrome installs new versions once the extension goes idle.
No build step — manifest.json, background.js, content.js, content.css, locate.js, and icons/ are loaded as-is. The icons are generated, not hand-drawn; replace them with anything you like at the same four sizes. After editing, hit the reload icon for the extension on chrome://extensions.
Releases go out only through a reviewed, merged PR — nobody hand-pushes a release tag:
- On a branch, bump
"version"inmanifest.jsonto the new version (Chrome extension versions are 1–4 dot-separated integers, e.g.1.2.0). - Open a PR and get it reviewed and merged to
main. - Once merged, the
Auto Tag Releaseworkflow checks whether this push actually changedmanifest.json's version and whether a tag for it already exists; if so, it pushesv1.2.0tomain. - Since a
GITHUB_TOKEN-authored tag push doesn't trigger other workflows,Auto Tag Releasethen calls theReleaseworkflow directly (as a reusable workflow, in-process) with that tag, which builds a zip withmanifest.json's version set to match the tag, publishes it as a GitHub Release, and uploads/publishes that same zip to the Chrome Web Store.
The Chrome Web Store publish step authenticates with a Google OAuth client (CWS_CLIENT_ID / CWS_CLIENT_SECRET) and a refresh token (CWS_REFRESH_TOKEN) stored as repo secrets, targeting the item ID in the CWS_EXTENSION_ID repo variable. A successful call either publishes immediately or puts the item into ITEM_PENDING_REVIEW, depending on the store's review requirements at the time.
Because the tag is only ever created from main, and main only moves via a reviewed PR (branch protection enforces this), every release traces back to a PR your other dev signed off on. A PR that doesn't bump manifest.json's version just merges normally with no release.
GeoHelper collects no data. See PRIVACY.md.