These packages are copy-ready CronPlus browser automation examples. Each directory
contains one .cronplus.yaml manifest, a script, and any local files needed for
cronplus validate.
Use them as starting points:
cronplus validate examples/browser/one-shot-browser
cronplus import examples/browser/one-shot-browserThe examples use CronPlus-managed browser paths instead of hard-coded temporary directories:
CRONPLUS_BROWSER_USER_DATA_DIRCRONPLUS_BROWSER_DOWNLOADS_DIRCRONPLUS_BROWSER_CACHE_DIRCRONPLUS_BROWSER_PROFILE_MODECRONPLUS_BROWSER_PROFILE_SOURCE
one-shot-browser: opens visible Chromium with an isolated per-run profile, visits one or more URLs, and lets CronPlus clean up successful runs.profile-copy-browser: copies a durable profile into an isolated per-run profile before opening visible Chromium. This is useful when a site needs cookies, localStorage, or extension state, but the task should not mutate the durable source profile.
The scripts default to public example URLs. Override them with environment
variables in the task manifest or task package .env file.