Chrome background check
Run a built-in deterministic habit in a temporary background browser while Chrome session access is paused.
last updated
Chrome background check is available to selected beta testers on Apple Silicon Macs running macOS 14 or newer. It currently tests a temporary browser using built-in pages. General website habits are not available through it yet.
Test deterministic steps
- Open Settings → General → Chrome background check.
- Choose Test deterministic habit.
- Review the listed steps, then choose run or skip.
The test navigates and searches built-in pages using fixed steps, with no AI call. The live panel shows each step's result. Each run needs your approval; it does not grant ongoing Chrome access.
Test an anonymous session
Select the checkbox approving one check, then choose Test without Chrome session.
The check opens a separate background browser, tests the built-in page, and removes its temporary browser and data. Expect Signed in: no, Admin access: not confirmed, and Temporary browser and data: removed. These results refer to the test page, not your account on a website.
Neither test needs a local web server or a Chrome sign-in. They do not read Chrome cookies, contact your website, or request Chrome Safe Storage access. Temporary browser data is encrypted on disk and removed after each run.
Chrome access is paused
Chrome setup and session import are unavailable until Plainwork can verify the destination site before sending borrowed cookies. This restriction applies to signed builds too. An earlier Chrome grant does not enable an imported-session check, and there is no setting to bypass destination verification.
Habits can declare required browser storage, but localStorage, sessionStorage, and IndexedDB import are unsupported. Those requirements stop execution before a browser starts. Declaring cookies does not enable website access either.
If you previously set up access, Remove Chrome access removes Plainwork's local consent. It does not change Chrome's Keychain permissions or sign you out of Chrome.
Cancel or resolve a failure
Cancel stops a running test and cleans it up. A failed step never switches to controlling your desktop. Browser recovery requires a separate habit opt-in and approval for its actions. If cleanup fails, use Retry cleanup before another test. Blocked apps/sites and Plainwork's safe mode also prevent checks. The feature is off by default and appears only when enabled for your beta account.