Changelog

The browser loop
keeps getting better.

Release notes and public builds. Check the release feed for the latest binaries and checksums.

Featured release

gripui v6.2.0 — challenges named, reloads stopped, headless frames run

gripui reports a site's browser check wherever it shows, refuses the reload that would restart it, no longer freezes cross-site frames in headless mode, and copies your default profile while your browser is open.

  • A browser check is reported whether it covers the page, runs in a frame, or is issued only to the page's scripts. Scripts refused with HTTP 429 or 503 are counted as network.throttled, so a blank page is no longer mistaken for an outage.
  • Challenge and rate-limit states no longer offer Reload. They say what to do next, and go, back, forward and reload include a challenge met on arrival in their own result.
  • reload, and go to the same site, are refused while a challenge or rate limit is active on the tab. --force overrides. gripui recognizes a check and stops repeating the request; it does not try to pass one.
  • Headless: a new cross-site frame could freeze for about ten seconds while gripui probed it before releasing it. Frames are no longer probed.
  • gripui set default-profile copies your profile while your browser is open. The real profile is only read and its lock files are never touched; databases are copied with their journals and re-copied if they changed.
  • gripui profiles fork accepts a profile that uses the copied default profile.
Open the release feed ↗

Demo recording

Player unavailable? Watch on YouTube ↗