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.
gripuirecognizes 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
gripuiprobed it before releasing it. Frames are no longer probed. gripuiset 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.gripuiprofiles fork accepts a profile that uses the copied default profile.