Your browser checks. PageFluxer keeps you informed.

Start a Local monitor

1. Install or update the PageFluxer Chrome extension, open your page and click the toolbar icon.
2. Choose Local. Connect the browser, approve the correct workspace in PageFluxer, then choose Finish connecting in the extension. An owner or admin must approve.
3. Select up to three targets and choose text, price, stock or new-link rules. Supported All conditions use the same shared rule model as Cloud. Record only safe, non-sensitive page preparation.
4. For a signed-in page, add a unique visible CSS selector that confirms you are signed in. Sign in normally on the website; never record a password or login form.
5. Set an interval, confirm selected-content sharing and grant access to this site. Choose Test & start Local monitor. The test runs in a fresh inactive tab and creates a quiet baseline.
6. Open Local monitors to pause, resume, check, edit or delete. Follow History & notifications to configure available delivery channels in PageFluxer.

What stays on your desktop, and what is shared?

Chrome supplies your ordinary website session to its own tabs. The extension does not read or upload website cookies, authorization headers, browser storage or password fields. It requests access to monitoring sites individually and uses a separate scoped PageFluxer device token for uploads.

Selected text, selected link addresses and labels, the page title and URL, monitor settings and explicitly recorded non-sensitive values are uploaded to PageFluxer. Selected content may contain private information. Hidden fields, form-control values and raw page HTML are excluded from captures. Normal authorized history, API, assistant and notification access still applies to the captured data.

Local captures are excluded from PageFluxer AI summaries and relevance processing in this release. Notification providers receive the content needed to deliver your enabled alerts. Local is an execution location, not a promise that every captured value remains on your device.

Background tabs and reliability

The extension stores its monitor list and schedule, then uses Chrome alarms to check due pages serially in temporary inactive tabs. You may briefly see those tabs. It does not refresh your existing tabs or require them to stay open. Chrome must remain running, the extension enabled, and your desktop awake and online for timely delivery.

Chrome alarms are best effort. Sleeping, quitting Chrome, losing connectivity, background throttling or slow websites can delay a check. There is no guarantee that a large monitor list completes at every selected interval. Missed checks are not replayed in a burst. Intermediate changes can be missed.

Changed captures upload promptly when connected. Unchanged statuses batch periodically. If connectivity fails during an upload, a bounded queue retains the latest result per monitor. Before starting more checks, the extension must successfully sync with PageFluxer. This keeps web pause and delete controls authoritative; no new pages are checked while a sync is failing.

Local allowances

Paused Local monitors still occupy saved slots. Local does not consume HTML or Cloud Browser check credits. Full captures are limited to 32 KiB; unchanged status messages do not consume capture-upload allowance. Upload totals reset at midnight UTC. The existing workspace history, email, webhook and channel allowances remain shared. Local is not unlimited server processing.

Supported actions and limits

Local supports safe DOM clicks, non-sensitive fill, select, check, wait and scroll steps, bounded extra waits and CSS readiness selectors. These synthetic actions can behave differently from Cloud Browser input. Native key presses, sensitive fields, cross-origin navigation, new tabs and downloads are rejected. Only record actions you are authorized to perform; opening a page can still have website side effects.

This first Local release does not support screenshots, PDFs, RSS/sitemap source watches, AI processing or no-change alerts. Frames, closed shadow roots, canvas-only content, protected Chrome pages, CAPTCHA and foreground-dependent pages are unsupported. Some signed-in websites rely on tab-specific session storage that a fresh tab cannot reuse. A failed login marker, ambiguous selector or failed capture preserves the last successful baseline.

Connections, changes and deletion

Edit and test capture settings in the connected extension. Pause, resume or delete from either the dashboard or the extension. The scheduler syncs about once a minute while Chrome is running; opening Local monitors or choosing Refresh requests an immediate sync. An in-progress page check may finish, but the server rejects new results for paused or deleted monitors. Pausing keeps retained history. Deleting removes the monitor and its history, and clears the extension copy and queued results on the next successful sync. An already-deleted monitor can be safely removed from the extension again. Browser connections expire after 90 days; reconnect with a fresh web approval to renew the same identity when the original device token is still present.

Revoke a browser from Local browsers to reject uploads immediately and pause its server monitors. New checks require a successful sync; revocation also rejects uploads immediately. An in-progress tab may finish before the next sync. Close Chrome or disable the extension for an immediate local stop. Uninstalling the extension does not delete server history; delete monitors in PageFluxer when that is your intent. A new Chrome profile must recreate and test Local monitors.