Choose where your checks run.
Start a setup in PageFluxer, the API or a connected assistant. Use PageFluxer Local when you want checks to run in your own Chrome profile, or Cloud when you want checks to continue while your computer is off.
Version availability
Browser setup requests and transfers require PageFluxer Chrome Extension v0.4.4 or later and the updated PageFluxer app. PageFluxer Chrome Extension v0.4.4 is an upcoming release. PageFluxer Chrome Extension v0.4.1 remains submitted for Store review; it creates PageFluxer Local monitors from the extension and uses selector-based prices with a required currency. See the version history for availability and future updates.
Start a PageFluxer Local monitor from the app
- Connect your Chrome profile to the correct workspace from the PageFluxer Chrome Extension.
- Open Add a PageFluxer Local monitor. Choose the connected browser, page address, monitoring goal and interval.
- Send the setup. A pending request is waiting for review; no Local checks have started.
- In the selected Chrome profile, open the PageFluxer Chrome Extension and choose Local monitors, then Review setup. Allow access to that website.
- Review the page, targets and any preparation actions. For a price, detect or select the current offer. For signed-in content, add a visible signed-in marker. Confirm selected-content sharing.
- Choose Test current capture or Test current price. Check the returned values and confirm to save. The starting capture does not send a change alert.
Requests expire after 24 hours. You can cancel them on the Local browsers page or decline them in the extension. A request belongs to one browser; opening another Chrome profile will not run it.
Move an existing monitor
Cloud to PageFluxer Local: open the monitor, choose Move to PageFluxer Local, and select a connected browser. Review, test and confirm in that browser. The Cloud monitor keeps its current schedule until confirmation succeeds.
PageFluxer Local to Cloud: choose Move to Cloud on the monitor’s PageFluxer page or in the extension. Load and confirm a fresh Cloud preview. Chrome’s website session is not copied; a signed-in Cloud monitor needs its own approved site connection.
Supported transfers keep the same monitor, retained history, labels, pause state and notification channels. Each destination starts a new quiet baseline, so differences between Cloud and your browser do not produce a transfer alert. Paused monitors stay paused. A failed capture leaves the source unchanged. The destination’s plan allowances and minimum interval apply, and a monitor at the same address in that destination must be resolved first.
If the source settings change while a request is waiting, cancel it and send a fresh request. This prevents an older setup from replacing newer settings.
What can move?
| Feature | Cloud and PageFluxer Local |
|---|---|
| Content, product prices, availability and new items | Supported, with fresh testing in the destination. |
| Up to three targets and supported All conditions rules | Supported. |
| Clicks, public text, filters, checkboxes, waits and scrolling | Supported actions can be reviewed and tested. |
| Retained history and notification channels | Shared in PageFluxer, subject to your plan. |
| Screenshots, PDFs and RSS/Atom/sitemap source monitors | Cloud features; these monitors cannot move to PageFluxer Local. |
| AI summaries, relevance filtering and no-change alerts | Cloud features. Turn them off before moving. PageFluxer Local captures remain protected from AI processing. |
| Native key presses | Cloud Browser only. Replace them with supported actions before moving. |
Capture limits differ: PageFluxer Local sends at most 32 KiB and 100 selected items per capture. Choose a narrower region when necessary. It never silently truncates a large item list. Existing monitors retain their capture behavior until you edit, test and confirm them.
Start from ChatGPT, MCP or the API
Ask a connected assistant: “Prepare a PageFluxer Local price monitor for this product in my desktop Chrome browser.” The assistant can use list_local_browsers, prepare_local_monitor and list_local_requests. It can prepare a Cloud transfer by supplying the monitor ID and current configuration version. You still review and confirm in Chrome.
The REST API provides GET /api/v1/local-browsers, POST /api/v1/local-requests, and list, status and cancellation endpoints. Read operations require monitors:read; preparation and cancellation require monitors:write. A 202 response means the setup is pending browser review.
POST /api/v1/local-requests
Authorization: Bearer YOUR_TOKEN
Idempotency-Key: local-product-setup-001
Content-Type: application/json
{
"device_id": "YOUR_CONNECTED_BROWSER_ID",
"url": "https://example.com/product",
"goal": "price",
"name": "My product",
"interval_minutes": 15
}To move a Cloud monitor, send device_id, monitor_id and expected_version to the same endpoint. To move a PageFluxer Local monitor to Cloud, update it with execution_mode: "cloud", a fresh preview_id, expected_version and the confirmed targets and interval. MCP’s update_monitor supports this explicit Cloud transfer too. See the API reference and MCP guide.
When checks repeatedly fail
First check the error, the next attempt and the last successful capture. Active Cloud monitors retry automatically with a delay, and temporary failures may recover without changing your setup. If repeated attempts do not recover, test the page in your browser. If it loads normally in your Chrome profile but Cloud requests are challenged, PageFluxer Local may be a useful alternative. It still depends on the website granting access and on Chrome being open, online and on an awake desktop. It does not bypass CAPTCHA, guarantee Amazon access or recover changes missed while your computer was off.
If Chrome is often unavailable, try a Cloud preview before transferring back. The monitor list offers a link to review the other method after repeated failures; it never moves a monitor automatically. Amazon price-monitoring guidance →